How to change an exchange hostname to a new one with new FQDN SSL

Please make sure that you make a note of all the changes. There might be other configuration changes which are not included in the scope of this article.

This should not be treated as a guide/tutorial and it should only be used for informational only or training purposes.

There might an alert being displayed up to 24h from when it has been changed.

  1. Replace you SSL under IIS -> Default Site-> Security with a new one.
  2. Then correct Outlook Anywhere in Exchange Management Console under Client Server.
  3. Then issue the following powershell commands to  check your current configuration.

Get-ClientAccessServer | Select Name, *Internal* | fl

Get-UMVirtualDirectory | select identity,Name, *url* | fl

Get-ActiveSyncVirtualDirectory | select identity,Name, *url* | fl

Get-WebServicesVirtualDirectory | select identity,name,*url* | fl

Get-OABVirtualDirectory | select identity,name,*url* | fl

then you can amend the site using the new hostname/FQDN

Set-ClientAccessServer –Identity SERVER_NAME -AutoDiscoverServiceInternalUri:

Set-UMVirtualDirectory –Identity: “SERVER_NAME\UnifiedMessaging (Default Web Site)” –InternalURL:

Set-UMVirtualDirectory –Identity: “SERVER_NAME\UnifiedMessaging (Default Web Site)” –ExternalURL:

Set-ActiveSyncVirtualDirectory –Identity: “SERVER_NAME\Microsoft-Server-ActiveSync (Default Web Site)” -InternalURL:

Set-ActiveSyncVirtualDirectory –Identity: “SERVER_NAME\Microsoft-Server-ActiveSync (Default Web Site)” -ExternalURL:

Set-WebServicesVirtualDirectory –Identity “SERVER_NAME\EWS (Default Web Site)” –InternalUrl:
Set-WebServicesVirtualDirectory –Identity “SERVER_NAME\EWS (Default Web Site)” –ExternalUrl:

Sometimes it may take up 24h for the Outlook client reshresh settings.

You can also try to recycle app pool in IIS for

MSExchangeAutodiscoverAppPool or you may want to run iisreset /noforce on the server. To restart IIS Services.

Some more useful info: