Exchange 2013 Configure internal URLs

Configure internal URL (client accesses mail.contoso.com via intranet)

Estimated time to complete: 10-15 minutes

Before the client can connect to the new server from the Intranet, you need to configure the internal domain or URL on the virtual directory of the client Access server, and then configure your private domain Name Service (DNS) records.

You can choose whether users use the same URL or a different URL to access your Exchange server on the Intranet and the Internet. Your choices depend on the addressing scheme that you are ready to implement or that you are implementing. If you are implementing a new addressing scheme, we recommend that you use the same internal and external URLs. Using the same URL makes it easier for users to access your Exchange servers, because they only need to remember one address . Regardless of what you choose, you must ensure that you configure a dedicated DNS zone for the address space that you configure. For more information about administering DNS zones, see Managing DNS servers.

For more information about the internal and external URLs of virtual directories, see Virtual directory Management.

What do you want to do?

Configure the internal and external URLs to be the same

2. Open the Exchange Management Shell on the Client Access server .

4. Store the host name of the client Access server in a variable for use in the next step. For example, Ex13.

   $HostName " Ex13 "

5. Run the following command in the shell to configure each internal URL to match the external URL of the virtual directory . (can also be configured via graphical interface, server-virtual directory)

   Set-ecpvirtualdirectory"$HostName \ECP (Default Web Site)"-internalurl ((get-ecpvirtualdirectory"$HostName \ECP (Default Web Site)"). Externalurl) Set-webservicesvirtualdirectory"$HostName \ews (Default Web Site)"-internalurl ((get-webservicesvirtualdirectory"$HostName \ews (Default Web Site)"). Externalurl) Set-activesyncvirtualdirectory"$HostName \Microsoft-Server-ActiveSync (Default Web Site)"-internalurl ((get-activesyncvirtualdirectory"$HostName \Microsoft-Server-ActiveSync (Default Web Site)"). Externalurl) Set-oabvirtualdirectory"$HostName \oab (Default Web Site)"-internalurl ((get-oabvirtualdirectory"$HostName \oab (Default Web Site)"). Externalurl) Set-owavirtualdirectory"$HostName \owa (Default Web Site)"-internalurl ((get-owavirtualdirectory"$HostName \owa (Default Web Site)"). Externalurl) Set-powershellvirtualdirectory"$HostName \powershell (Default Web Site)"-internalurl ((get-powershellvirtualdirectory"$HostName \powershell (Default Web Site)"). Externalurl)

7. 650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; margin:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M02/8C/7D/ Wkiol1hum9gj9xjbaaep6ovi8vo657.png "" 644 "height=" 213 "/>

9. Run the following command to configure the URL of the internal Autodiscover service. This command uses the internal Outlook everywhere host name that you previously configured in the manifest.

   $HostName $HostName $HostName). Fqdn.tolower ()), ((Get-outlookanywhere). internalhostname.hostnamestring))

11. Although we are in the Shell, we can also configure the offline Address Book (OAB) so that Autodiscover can select the correct virtual directory for OAB distribution. Run the following command to perform this operation.

    $True $Null

After you configure the internal URL for the Client Access server virtual directory, you need to configure private DNS records for Outlook Web App and other connections. Depending on your configuration, you need to configure the private DNS record to point to an internal or external IP address, or to a fully qualified domain name (FQDN) of the client Access server. The following is an example of a DNS record that is recommended to be created to enable internal client connections.

650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; margin:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/8C/7D/ Wkiol1hum9hyldgiaabt6h8yxse035.png "" 430 "height=" 153 "/>

How do you know this step works?

To verify that you have successfully configured the internal URL of the Client Access server virtual directory, do the following:

1. In the EAC, go to Servers > virtual directories.

2. In the Select Server field, select the Internet-facing client Access server.

3. Select the virtual directory and click Edit 650) this.width=650; title= Edit icon alt= Edit icon src= https://i-technet.sec.s-msft.com/zh-CN/ EXDEPLOY2013/JJ933448.6F53CCB2-1F13-4C02-BEA0-30690E6EA71D (v=exchg.150). gif?state=3215- w-cabeigaaqaagaaeaaqaaaaeaaaaawamaaaa%7e "/>.

4. Make sure the internal URL field is populated with the correct FQDN and service as shown below:

   650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; margin:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/8C/7D/ Wkiol1hum9kha82haae1rzitxuw558.png "" 602 "height=" 397 "/>

To verify that the internal URL of the Autodiscover service was successfully configured, do the following:

1. Open the Management Shell on the Client Access server.

2. Run the following command, and specify the host name of your client Access server. For example, Ex13.

   Get-clientaccessserver Ex13 | Format-list AutodiscoverServiceInternalUri

3. Verify that the values stored in the attribute are filled in with the AutoDiscoverServiceInternalUri correct FQDN. For example, https://mail.contoso.com/Autodiscover/Autodiscover.xml .

650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; margin:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M02/8C/7D/ Wkiol1hum9pbuha8aaa1rym-wyo214.png "" 644 "height="/>

650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; margin:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M02/8C/7D/ Wkiol1hum9tr1u6caaeptlaii-s251.png "" 644 "height=" 425 "/>

To verify that you have successfully configured a private DNS record, do the following:

1. Open a command prompt and run nslookup.exe .

2. Change to a DNS server that can query a private DNS zone.

3. Look in the nslookup records for each FQDN that you created. Verify that the value returned for each FQDN is correct.

Do you have any questions? Please ask for help in the Exchange forum. Please visit the following forums: Exchange Server, Exchange online, or Exchange online Protection.

https://technet.microsoft.com/zh-cn/exdeploy2013/PrintChecklist?state=3215-W-CABEIgAAQAAgAAEAAQAAAAEAAAAAwAMAAAA%7e

Exchange 2013 Configure internal URLs