Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2
Topic Last Modified: 2013-01-22
The Mailbox Replication Proxy (MRSProxy) service is installed on every Microsoft Exchange Server 2010 Client Access server. MRSProxy helps to facilitate cross-forest move requests and runs on the remote forest's Exchange 2010 Client Access server. However, MRSProxy is disabled by default.
|All Client Access servers in the Network Load Balancing (NLB) array must have MRSProxy started. When you create a remote move request, and specify the fully qualified domain name (FQDN) of the RemoteHostName parameter, the load balancers that share the same name space as the FQDN you specified can direct the move request to any of the Client Access servers in that array. If you don't have MRSProxy started on one of the Client Access servers, and a move request is directed to that server, the move request fails. For more information about the NLB array, see "Availability Service Network Load Balancing" in Understanding the Availability Service.|
Looking for other management tasks related to move requests? Check out Managing Move Requests.
Use the Shell to Enable MRSProxy in the Remote Forest
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Exchange Web Services virtual directory settings" entry in the Client Access Permissions topic.
This example enables MRSProxy on the Exchange Web Services (EWS) default Web site. It also modifies the maximum number of simultaneous connections that an MRSProxy instance accepts by changing the value to 50. The default value is 100.
Set-WebServicesVirtualDirectory -Identity "EWS (Default Web Site)" -MRSProxyEnabled $true -MRSProxyMaxConnections 50