Microsoft KB Archive/294792

= XADM: Multiple Recipient Update Services in a Single Domain =

PSS ID Number: 294792

Article Last Modified on 1/28/2004

-

The information in this article applies to:


 * Microsoft Exchange 2000 Server

-



This article was previously published under Q294792





SUMMARY
This article describes two types of Recipient Update Services. One Recipient Update Service processes Exchange System objects in the Configuration container, and the other Recipient Update Service (RUS) processes recipients in each domain.



MORE INFORMATION
There is only one of the first type of Recipient Update Service in the entire Microsoft Windows forest because there is only one Configuration container. The second type of Recipient Update Service can have multiple instances, even in the same domain. Exchange System Manager lists the first type of Recipient Update Service as &quot;Recipient Update Service (Enterprise configuration)&quot;. Exchange System Manager lists the second type of Recipient Update Service as &quot;Recipient Update Service &quot;.

You must have at least one Recipient Update Service for each domain in your organization, and you must run the Recipient Update Service from an Exchange Server computer. Each Recipient Update Service reads from and writes to a unique domain controller. If there are multiple domain controllers in a domain, there can be multiple Recipient Update Services running in the same domain.

You must set up multiple Recipient Update Service to overcome network latency issues when the domain spans several sites and when the connection between sites is slow. For example, if you have a site in Seattle and another site in Beijing, there may be a long delay before a mailbox that was created in Beijing is processed by the Recipient Update Service in Seattle. The user cannot log on to the mailbox until the Recipient Update Service populates mailbox e-mail attributes. Ideally, you can set up a second Recipient Update Service in Beijing that can use the domain controller in the local site. To add multiple Recipient Update Services to each domain:
 * 1) Start the Exchange System Manager snap-in.
 * 2) Click the Recipients container.
 * 3) Right-click Recipient Update Service, click New, and then create a new Recipient Update Service.
 * 4) Click Browse, and then click the domain.

NOTE: You cannot click a particular domain controller at this point because the Exchange Server computer defaults to an unused domain controller in the domain. After you create the new Recipient Update Service, you can change the domain controller.
 * 1) Click the Exchange Server computer that the Recipient Update Service services.

The name of the new Recipient Update Service defaults to Recipient Update Service where   increments one, two, and so forth.
 * 1) You can create as many Recipient Update Services as there are domain controllers in this domain.

To view the current Recipient Update Service connections in Exchange System Manager:
 * 1) Right-click the Recipient Update Service, and then click View.
 * 2) Click Columns, and then add the domain controller and the Exchange Server computer.

Due to replication latency, Microsoft recommends that you have at least one domain Recipient Update Service for each Windows site. This can be especially helpful when the connections between sites are slow. You can create up to one domain RUS per domain controller. The best number of Recipient update services for an installation will be dependent on individual scenarios such as number of Domain controllers per site, bandwidth, number of users in the domain and a host of other factors.

Additional query words: dc

Keywords: kbConfig kbinfo kbsetup kbSysAdmin KB294792

Technology: kbExchange2000Search kbExchange2000Serv kbExchange2000ServSearch kbExchangeSearch

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.