After updating exchange 2010 using the commands for Set-ActiveSyncVirtualDirectory, Set-ClientAccessServer, Set-ECPVirtualDirectory, Set-OABVirtualDirectory, Set-OWAVirtualDirectory, & Set-WebservicesVirtualDirectory to point to the same address as our external address with appropriate DNS entries to forward this address to our mail server, all new Outlook accounts that are setup function perfectly however old accounts are still throwing up certificate errors about 20-25 seconds after Outlook starts. I'm guessing that the existing accounts are using some cached data to connect that the new accounts are not.

Does this guess make sense?

What can I do to force these clients to update their cached data?

If not, is there a way to recreate these accounts while preserving the user address books, etc... (preferably in a scripted fashion)?


We have users on domain-connected PC on our internal network and external users accessing the exchange server through OWA on non-domain connected computers. For our internal users, everything was good (except for the fact we were using outdated security) but for external users they were constantly getting errors regarding our SSL certificate. So, we acquired a certificate from a trusted CA and we installed it on the IIS Server. As expected, all of the errors disappeared from our external users, but we ended up having errors for people accessing the exchange server on the domain PCs through outlook. The errors made perfect sense, the IIS server was presenting a certificate for a different domain than those computers were connecting to. A little searching around found this question on server fault, which got me to the point where new outlook accounts are setup fine, but old outlook clients are still throwing up errors.

  • A homemade certificate or a paid'one ? Valid it by accesssing the owa webpage from a computer that does not work. Some certificate authority are new, thus the windows update is critic to be sure its listed secure – yagmoth555 Apr 23 '15 at 17:12
  • The certificate is good. None of the browsers on any computers complain while accessing OWA. New outlook accounts also don't complain, but old outlook accounts are still connecting via outdated server addresses which don't match the new certificate. – Darinth Apr 23 '15 at 19:31

I'm battling a similar issue. I don't have enough points to just comment.

But I'm curious, is this a wildcard certificate? And do you have the EXCH outlook provider CertPrincipal name set?


It is typical with wildcard certs to set the EXPR provider. But I'm finding I may also need to set the EXCH provider.

Set-OutlookProvider EXCH -CertPrincipalName msstd:*.domain.com

  • I did not have a wildcart certificate, single domain certificate only nor did I set the EXPR provider. In the end, the problem does appear to have been a caching issue. Over time the certificate errors all disappeared on their own as cached data expired and was refreshed. – Darinth May 26 '15 at 16:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.