We are running Exchange 2010 on SBS 2011. About a year ago, I renewed the certificate for the mail server, however, ever since that time, we receive certificate errors on OWA, and internally, we cannot create out of office messages (says the server is unavailable). I also now have a client running Outlook 2016 who cannot connect at all to the server. After much research, I think I have resolved that the certificate name doesn't match the exchange mail server name. I thought I renewed exactly what we had before, but apparently not. As an example, our mail server is actually: mail.mydomain.com, but the CN on the certificate is: remote.mydomain.com. Note that to connect to OWA, we use: https://remote.mydomain.com. The cert was done through godaddy. Our DNS is through Wordpress. Any advice for how to fix this....or am I stuck purchasing a new cert for mail.mydomain.com?
SBS wants to use remote.example.com for everything - and I would suggest that is what you use. If you have configured the server to use mail.example.com then you have two options.
- Run the configuration wizards in the SBS console to change the name to mail.example.com and get the SSL certificate reissued.
- Run the configuration wizards in the SBS console which will set Exchange etc to use remote.example.com. The Outlook clients will then be updated via Autodiscover internally. Mobile clients will need to be corrected. Externally if you have Autodiscover DNS records in place then that allow external machines to update.
It is key that you use the wizards to configure the server rather than the manual way for all functionality to work within SBS.