Multi-Domain Configuration

Last Updated : Oct 16, 2020 |

In a multi-domain setup (where Exchange and AD are part of a sub-domain) or where Exchange has a different default accepted domain (the Exchange email domain name is different from the AD domain), the following additional configuration is required.

Exchange Configuration

Ensure that the Autodiscovery URL is pointing to the host on which Exchange is installed. That is, use the FQDN of the host in the autodiscovery URL. This is the attribute retrieved from the Get-ClientAccessServer | fl command executed on exchange management shell command.

  1. Verify the FQDN using the following command:

    [PS] C:\Windows\system32>Get-ClientAccessServer | fl Fqdn
Fqdn : <FQDN>
[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory | fl ExternalUrl
ExternalUrl : https://<FQDN>/EWS/Exchange.asmx
[PS] C:\Windows\system32>Get-ClientAccessServer | fl AutoDiscoverServiceInternalUri
AutoDiscoverServiceInternalUri : https://<FQDN>/autodiscover/autodiscover.svc

  2. If the FQDN shown in any of the parameters above is incorrect, rectify it to the correct FQDN using the corresponding Set-WebServicesVirtualDirectory or Set-ClientAccessServer commands.

Note:

  • TLD= Top level domain.

    EAD = Exchange Accepted domain.

  • Setting the URL to any name (for example mail.TLD.com or mail.EAD.com) other than the FQDN may not work.

  • It is also recommended to NOT have the AD TLD names as ‘.local’.

Related information
Exchange server integration
IIS Configuration
Web Manager Configuration