A little history. We had a single exchange 2010 (exch1)server which was under spec'd for our needs. The server had a 3rd part ssl cert installed. I have recently installed another exchange 2010 server (exch2) on to a new server and have moved all the mailboxes to this server, and replicated all the connectors we need/use. I moved the ssl cert to the new server and assigned exchange roles to it, and went through the process of getting it reissued from the 3rd party. This seems to be working from the OWA side, but internally we now get a prompt on outlook to accept the certifcate from exch2, because the server name and cert name don't match. The cert was issued to webmail.mydomain.com but error states there is a problem because it is coming from exch2.domain.local. I'm sure this is going to be a simple answer but I'm at a bit of a loss on this one.

Hi, If this is a UCC certificate then get it reissued one more time and add exch2.domain.local and exch2 to it, also have autodiscover.domain.com. /Martin Exchange is a passion not just a collaboration software.

It is a UCC certificate so I guess I could get it re-issued but I'm curious as to why those weren't need before and are now. This might be a silly question but as the cert includes say webmail.mydomain.com can I not get the server to be webmail.mydomain.com. externally that is exactly what it is, and internally webmail.mydomain.com resolves to the internal ip of exch2

Hi, You can use a single name cert. Simon has written an article about it which you can find here: http://www.amset.info/exchange/singlenamessl.asp I also used this guide from Elan Shudnow earliere: http://www.shudnow.net/2007/08/10/outlook-2007-certificate-error/ As to why it worked before I can say, but maybe reading the articles listed can give you a hint. /MartinExchange is a passion not just a collaboration software.