jmair Posted March 10, 2011 Posted March 10, 2011 I've just purchased a new cert for our exchange server (our old one was Self Signed). All internal clients connect to the exchange server at server.domain.int. The new cert was made for domain.org. Now every client machine is getting a cert error when they open up Outlook. "The name on the security certificate is invalid or does not match the name of the site." Oops. What's the fastest way to fix this issue?
EduTech Posted March 10, 2011 Posted March 10, 2011 This should help you out, it has appeared on here a couple of times so it might be worth doing a search on the forum also. Security warning when you start Outlook 2007 and then connect to a mailbox that is hosted on a server that is running Exchange Server 2007 or Exchange Server 2010: "The name of the security certificate is invalid or does not match the name of You basically just need to run a script in powershell to update some settings, like autodiscover etc. James.
sukh Posted March 10, 2011 Posted March 10, 2011 Hi That KB seems helpful. Have you tested external access. It's nice to have a SAN certificate for Exchange, helps out. Sukh
chrisbrown Posted March 10, 2011 Posted March 10, 2011 Obtaining a SAN cert is really the way to go. It's a little more expensive but will save you lots of hassle in the long run. Put all names in that any user is likely to access your servers via. It's important that you put your external OWA URL as the primary subject name in this cert too.
mb2k01 Posted March 11, 2011 Posted March 11, 2011 I'd recommend getting a UC cert. You can put multi domains within the cert to cover for server.internal, server.exernal.com plus autodiscover. and owa. etc I've used Comodo for the last could of years, really good pre and post sale support. Fairly sure they sell to the US too.
techieshelp Posted March 22, 2011 Posted March 22, 2011 this is almost certainly an SAN ( subject alternative name ) issue. Make sure that you have SAN`s for all possible references to the server in your cert. For instance mail.yourdomain.com for external the servername.FQDN.com for internal referencing. Additional you will need autodiscover.fqdn As the post above mentions you will need to run the ps1 script for setting the autodiscover service url.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now