How to Create a New Recipient Update Service

 

Exchange uses the Recipient Update Service primarily to generate and update default and customized address lists and to process changes made to recipient policies. This procedure outlines how to create a new Recipient Update Service.

Before You Begin

You must have at least one Recipient Update Service for each domain in your organization, and it must be run from an Exchange 2003 or Exchange 2000 server. For domains that do not have these Exchange servers, the Recipient Update Service must be run from an Exchange server outside the domain. You can set up more than one Recipient Update Service for a domain, if there are multiple domain controllers. Each Recipient Update Service must read from and write to a unique domain controller.

Note

If you do not have a Recipient Update Service for a domain, you cannot create recipients in that domain.

In situations where you have high network latency in a domain, set up the Recipient Update Service at the local sites. For example, if you have one domain that has sites in Seattle and in Beijing, there might be a long delay before a mailbox that an administrator creates in Beijing is processed by the Recipient Update Service in Seattle. In this case, having a Recipient Update Service on the local domain controller in Beijing will decrease the time the user has to wait to be able to access the mailbox after it has been created.

Procedure

To create a new Recipient Update Service

1. In Exchange System Manager, expand the Recipients container.

2. Right-click the Recipient Update Service container, point to New, and then click Recipient Update Service.

   The Recipient Update Service wizard starts and guides you through the creation process.

   The final step in creating a Recipient Update Service

   

   Note

   If all the domain controllers are currently associated with a Recipient Update Service, you receive an error when you try to create the next Recipient Update Service. You can have only one Recipient Update Service per domain controller.