When Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 is installed, two Recipient Update Services (RUS) are created, one for the Enterprise Configuration and another for the domain. The domain Recipient Update Service only processes objects in the Windows domain where Exchange was installed. When you create a user in a remote Windows domain, the Recipient Update Service does not process that account.

Back to the top

A Recipient Update Service is not automatically created for a remote or child Windows domain. This causes the Recipient Update Service to not be able to process any mailbox-enabled users or mail-enabled users in the remote or child Windows domain.

Back to the top

To resolve this issue, first run Exchange Setup with the /domainprep switch on a server in the remote Windows domain. Then, on your Exchange server use the Exchange System Manager to create a Recipient Update Service for the remote domain. To do this, follow these steps:

1.	Click Start, click Programs, click Microsoft Exchange, and then click System Manager.
2.	Expand the Organization object, and then expand the Recipients container.
3.	Click Recipient Update Service.
4.	In the right pane, right-click New, and then click Recipient Update Service.
5.	Click the domain that does not have an instance of the Recipient Update service and that has users that must be updated by Exchange.
6.	Click Next.
7.	Choose the server that you want to run the Recipient Update Service and process all the necessary users with the Exchange attributes.
8.	Click Next.
9.	Click Finish.
10.	To manually initiate an update of the recipients in that domain, right-click the Recipient Update Service, and then click Update Now to force an update.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

MORE INFORMATION

Back to the top

Workaround

To work around this issue, manually create an entry in the Hosts file in the following location:

Winnt\System32\Drivers\Etc\Hosts

For example, if the Recipient Update Service server is running in domainA and the domain controller exists in domainB, create the following entry for the domain controller in the Hosts file:

IP Addressdc_name.domainA.com

Scenario 2: Accounts in remote domain not processed because of similar server name in remote domain

After creating the Recipient Update Service for the remote Windows domain, users in the remote domain are not processed. An event similar to the following may be logged in the Event Viewer System log: If Diagnostic Logging on the Service Controller object under the MSExchangeAL service is set to Medium, the following events may be logged in the Event Viewer Application log:

Cause

This issue may occur if a member computer in the local Windows domain has the same name as a domain controller in the remote Windows domain.

Resolution

To resolve this issue, identify and rename the member computer in the local Windows domain that has the same name as the domain controller in the remote Windows domain.

Back to the top