How to Move a Client Access or Hub Transport Server to a Different Site: Exchange 2007 Help

How to Move a Client Access or Hub ...

Collapse All

How to Move a Client Access or Hub Transport Server to a Different Site

Applies to: Exchange Server 2007 SP2, Exchange Server 2007 SP1 Topic Last Modified: 2009-01-14

This topic explains how to move a Client Access server or a Hub Transport server from one Active Directory site to another Active Directory site.

Before You Begin

To perform this procedure, the account you use must be delegated the following:

Exchange Server administrator role and membership in the local administrators group on the Hub Transport server and the Client Access server
Membership in the Domain Admins group and in the local administrators group to change site membership

For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.

If you have network load balancing (NLB) enabled for your Client Access server, you must remove the Client Access server from the NLB array before you begin the procedure. If you will have NLB enabled in the new site, you must add the Client Access server to the array after you move it to the new site.

If you are using a reverse proxy server, such as Microsoft Internet Security and Acceleration (ISA) Server 2006, you must stop traffic from the reverse proxy server to the Client Access server before you begin the procedure, and then restart traffic after you move the Client Access server to the new site.

In any site with the Mailbox server role, you must have at least one Hub Transport server role installed. Confirm that if you move a Hub Transport server to a different site, the original site will still have the Hub Transport role installed on at least one computer.

In the target site, you must have at least one domain controller that is also a global catalog server and is running Windows Server 2003 with Service Pack 1 (SP1) or a later version.

Procedure

To move a Hub Transport server to a different Active Directory site

On the Exchange 2007 Hub Transport server, click Start, click Run, type Services.msc, and then click OK.
In the list of services, right-click Microsoft Exchange Transport, and then click Pause.
Wait five minutes.
In the Exchange Management Shell, type the following command:
```
Get-Queue
```
Verify that MessageCount is at zero for all queues except Poison. Make a note of any queue that has a status of Retry. You will resubmit the messages in these queues later in this procedure. For more information about queues, see Managing Queues.
In the Microsoft Management Console (MMC), right-click Microsoft Exchange Transport, and then click Stop.
In the MMC, right-click Microsoft Exchange Transport, and then click Properties.
On the General tab, under Startup type, select Disabled from the drop-down list, and then click OK.
Verify that for each Send connector that has the Hub Transport server that you plan to move listed as a source server, the send connector also has another Hub Transport server listed as a source server. To view, add, or remove source servers, in the Exchange Management Console expand Organization, select Hub Transport, and then select the Send Connectors tab. Right-click each connector and then select Properties. In the Properties dialog box, select the Source Server tab.

Note:
We recommend that you also remove the Hub Transport server that you plan to move from the list of source servers for the connector.
Verify that for each Receive connector on the server that you plan to move, you have a receive connector on another Hub Transport server that will receive messages after you move the first Hub Transport server.
Verify that for each Receive connector on the server that you plan to move, if the connector is scoped to a specific IP address or IP range, that address or range will still be valid after you move the server.
In the Exchange Management Console, to determine which Edge Transport servers have subscriptions to the Hub Transport server that you plan to move, expand Organization, select Hub Transport, and then select Edge Subscriptions. You will need to resubscribe these Edge Transport servers later in this procedure.
Shut down the Hub Transport server.
On another computer in the Exchange organization, to open Active Directory Sites and Services, run the following from a Command Prompt window:
```
%systemroot%\system32\dssite.msc
```
In Active Directory Sites and Services, expand Sites, expand Subnets, right-click the subnet that the Hub Transport server is in, and then select Properties.
On the General tab, in the Site drop-down list, select the site to which you want to move the Hub Transport server, and then click OK.
Turn on the Hub Transport server.
To verify that the site membership has replicated, run the following command:
```
Get-ExchangeServer
```
Click Start, click Run, type Services.msc, and then click OK.
In the list of services, right-click Microsoft Exchange Transport, and then click Properties.
On the General tab, under Startup type, select Automatic from the drop-down list, and then click OK.
In the MMC, right-click Microsoft Exchange Transport, and then click Start.
To resubmit messages from queues with a status of Retry, which you noted in Step 4, run the following command:
```
Retry-Queue <Identity of queue> -Resubmit:$true
```
To resubmit messages in the Unreachable queue, run the following command:
```
Retry-Queue Unreachable -Resubmit:$true
```
Verify that the Status of all queues is Active or Ready and that the MessageCount is less than 100 by running the following command:
```
Get-Queue
```
Resubscribe the Edge Transport servers that you identified in Step 11. For more information, see Subscribing the Edge Transport Server to the Exchange Organization.

Note:
We recommend that you also remove the Hub Transport server that you plan to move from the list of source servers for the connector.

To move a Client Access server to a different Active Directory site

If the server or site where the server resides is in a failed state and no computers are connecting to the Client Access server, skip to Step 3.

On the Client Access server that you plan to move, configure the virtual directory properties so that no traffic is proxied through the Client Access server by running the following commands:

set-owavirtualdirectory "<OWA virtual directory name>" -externalurl $null -internalurl $null
set-activesyncvirtualdirectory "<ActiveSync virtual directory name>" -externalurl $null -internalurl $null
set-webservicesvirtualdirectory "<web services virtual directory name>" -externalurl $null -internalurl $null -internalurlnlbbypass $null
set-oabvirtualdirectory "<OAB virtual directory name>" -externalurl $null -internalurl $null

Shut down the Client Access server.
On another computer in the Exchange organization, using an account that is a member of the Domain Admins group, to open Active Directory Sites and Services, run the following from a command prompt window:
```
%systemroot%\system32\dssite.msc
```
In Active Directory Sites and Services, expand Sites, expand Subnets, right-click the subnet that the Client Access server is in, and then select Properties.
On the General tab, in the Sites drop-down list, select the site to which you want to move the Client Access server, and then click OK.
Verify that the site membership change has replicated by viewing Active Directory Sites and Services from another computer in another site.
Turn on the Client Access server.

To configure site affinity for Autodiscover for the site to which you moved the Client Access server, run the following command:

Set-ClientAccessServer -Identity "ServerName" -AutodiscoverServiceInternalURI "https://internalsitename/autodiscover/autodiscover.xml" AutodiscoverSiteScope "SiteName"

On the Client Access server that you moved, configure Microsoft Office Outlook Web Access by running the following command:

set-owavirtualdirectory "<OWA virtual directory name>" -externalurl https://<FQDN for external access>/owa -internalurl https://<FQDN of Client Access server>/owa

On an Exchange 2007 server in the organization, configure ActiveSync by running the following command:

set-activesyncvirtualdirectory "<ActiveSync virtual directory name>" -externalurl https://<FQDN for external access>/Microsoft-Server-ActiveSync -internalurl https://<FQDN of Client Access server>/Microsoft-Server-ActiveSync

On the Client Access server that you moved, configure Exchange Web Services by running the following command:

set-webservicesvirtualdirectory "<web services virtual directory>" -externalurl https://<FQDN for external access>/ews/exchange.asmx -internalurl https://<FQDN for external access>/ews/exchange.asmx -internalurlnlbbypass https://<FQDN of the Client Access server>/ews/exchange.asmx

On the Client Access server that you moved, configure the offline address book virtual directory by running the following command:

set-oabvirtualdirectory "<OAB virtual directory name>" -externalurl https://<FQDN for external access>/ -internalurl https://<FQDN for external access>/

On the Client Access server that you moved, test Outlook Web Access, ActiveSync, and Exchange Web Services connectivity by running the following commands:
```
Test-OWAConnectivity
Test-ActiveSyncConnectivity
Test-WebServicesConnectivity
```
On an Exchange 2007 server in the organization, verify that only the required services are started by running the following command:
```
Test-ServiceHealth
```

For detailed syntax and parameter information, see the following topics: