So is there a workaround, until the possible "allow unsecure SSL version" configuration UI option is added or the offending exchange servers IIS is updated from it's out-dated defaults?
↧