I know this is a common question or issue when trying to attach a root trusted (starfield) ssl certificate to the exchange iis service but I have seen contradictory answers. I have a simple cert for my owa and activesync clients public address mail.domain.com I set it for the IIS service ONLY on Exchange 2010 so now I get an error from all outlooks clients. The name of the security certificate is invalid or does not match the name of the site: exchange.mydomain.local Is there a way to fix this?GB

I know this is a common question or issue when trying to attach a root trusted (starfield) ssl certificate to the exchange iis service but I have seen contradictory answers. I have a simple cert for my owa and activesync clients public address mail.domain.com I set it for the IIS service ONLY on Exchange 2010 so now I get an error from all outlooks clients. The name of the security certificate is invalid or does not match the name of the site: exchange.mydomain.local Is there a way to fix this? I don't use autodiscovery and I have very few clients. I already have single domain cert paid for for 5 years and a UC is about $500 for the same 5 years. thanks glennGB

You can try this link: http://www.amset.info/exchange/singlenamessl.asp Written for Exch 2007, but still applies. Add the ECP virtual directory to the list of URLs to configure.Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com

double post: http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/5aacdeb9-77b9-4f89-9d80-f8fc3c2f929eTim Harrington - Catapult Systems - http://HowDoUC.blogspot.com

Hi Glenn, Some other information for you: http://technet.microsoft.com/en-us/library/bb851505(EXCHG.80).aspx Regards! Gavin