Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

CertPrincipalName forced to wrong setting on server with wildcard SSL cert

$
0
0

Dears

After testing Exchange 2013 for a couple of weeks with a limited amount of IT personnel, we have migrated the first batch of users from 2010 to 2013.

That was the biggest mistake we've done this.. week..

The error is identified as an autodiscover/ssl problem. No matter what I specify in CertPrincipalName on CAS, Outlook resets itself to msstd:server.domain.com

I have tried with "none" and "msstd:*.domain.com" but it always resets to msstd:server.domain.com

Outlook Autoconfigure test returns the correct value. Any ideas?

All our clients are not domain members, so setting this with GPO is not an option.


Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>