On Tue, Mar 4, 2014 at 2:41 AM, Gavin Wilby <[email protected]> wrote: > Good Morning All, > > I have a single Exchange 2010 server, it holds all rolls, and is running > currently with a self signed certification. > > I have a wild card ssl cert *.domain.com, from Go Daddy, that I have been > asked to use for the Exchange server. > > I understand that there is a thought that a wildcard is less secure than a > SAN, but that's what I have and it is supported. > > My question really is, is there any likely disruption of service when > applying the new certificate. > > I understand the process will be running the wizard to generate a new request > key, then importing the cer file into Exchange, I then can assign services to > use it, to start with it will be the OWA, which runs on > https://mail.domain.com/owa, a wildcard will cover this. > > Anything I need to watch for, or any possible disruption from anyone's > experience? > > Gavin.
We've just migrated our US office from 2003 to 2010, and continued implementation of our wildcard cert. Just make sure you follow this after installing your cert: http://technet.microsoft.com/en-us/library/cc535023%28EXCHG.80%29.aspx by doing this: Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.example.org Kurt
