Scenario. We have a customer who is going through the process of migrating from SBS 2003. At the moment, we have Exchange 2003 (SBS) and Exchange 2010 co-existing on the same network.
We have purchased a wildcard SSL cert for *.ourdomain.net and this has been installed onto the Exchange 2010 server.
I have migrated just one test email account onto Exchange 2010 to iron out any issues.
This particular user has Outlook 2010, and since installing the new SSL certificate, when he opens Outlook he gets a warning about the certificate.
Outlook 2010 is connecting to the internal server name of srv-exch2010.ourdomain.loc
What I have done so far is:-
1) We already have a DNS zone for ourdomain.net, so I have added exchange.ourdomain.net as a CNAME entry pointing to srv-exch2010.ourdomain.loc
al. I can ping exchange.ourdomain.net and get the desired result back from the internal server IP.
2) After taking note of the existing settings, I have run the following PowerShell commands on the Exchange 2010 server:-
Set-ClientAccessServer -Identity SRV-EXCH2010 -AutodiscoverServiceInternalUri https://exchange.ourdomain.net/autodiscover/autodiscover.xml
Set-WebServicesVirtualDirectory -Identity "SRV-EXCH2010\EWS (Default Web Site)" -InternalUrl https://exchange.ourdomain.net/ews/exchange.asmx
Set-OABVirtualDirectory -Identity "SRV-EXCH2010\oab (Default Web Site)" -InternalUrl https://exchange.ourdomain.net/oab
Set-ActiveSyncVirtualDirectory -Identity "SRV-EXCH2010\Microsoft-Server-ActiveSync (Default Web Site)" -InternalUrl https://exchange.ourdomain.net/Microsoft-Server-ActiveSync
I have restarted the server, and yet still when I go into Outlook 2010 and try and enter the server name of exchange.ourdomain.net, it changes back to SRV-EXCH2010.ourdomain.loc
OWA is working fine both internally and externally.