I have SBS 2011 standard setup and working except for Remote Web access. I configured the domain and added an existing SSL Certificate manually (am not a GoDaddy or eNom customer). I can access Remote Web from inside and outside the LAN using mail.domainname.com and it gets redirected to the HTTPS logon page just fine. The problem is that the client picks up the wrong SSL certificate. Why?
When I look at the server certificates in IIS Manager on the server it shows the self signed certificates the installation of SBS automatically creates along with the Class 2 Certificate that I got from GlobalSign CA
When I logon to Remote Web from a client PC I get the dreaded "There is a problem with this website's security certificate." If I continue on and look at the certificate it shows that the client has picked up one of the self signed certificates instead of the GlobalSign CA certificate. Interestingly enough, the certificate that it picks up is the self signed certificate with the internal host name, not the one with the host name "remote" as was used in the URL to get to Remote Web. Yes, the GlobalSign CA certificate is assigned with the FQDN of the external name of the server - mail.domainname.com.
Where did I go wrong?
Yes I saw this before referring to sbs essentials but as instructions supplied were for sbs essentials not standard they were no use to me :-)