Exchange rus not updating
An active writer and contributing editor for international IT publications such as PC Quest, Bharat was also a technical reviewer for Exchange Server 2003 24 Seven by Jim Mc Bee. The Recipient Update Service was introduced in Exchange 2000 to discover and provision recipient objects.Multiple RUS objects for a single domain: By default, Exchange Server creates two RUS objects -- one for the enterprise, which processes Exchange system objects, and the other for the domain in which the Exchange server resides.It is generally not recommended to create more than one RUS pointing to domain controllers (DCs) in the same domain.By following these recommendations, you can achieve better performance, scalability, reliability, and uptime.For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at
Recipient Update Service (RUS) in a multi-domain forest: If your forest has multiple domains where recipients reside, you will need to run Domain Prep in those domains.If an instance of the Recipient Update Service is missing for a domain, new user objects created in the domain will not receive e-mail addresses issued to them.To resolve this issue, verify that an instance of the Recipient Update Service exists for each domain and create an instance of the Recipient Update Service for the domains that do not have one and then rerun Microsoft Exchange setup.Deleting email address rules in the default recipient policy: Rules in the default recipient policy can be modified to accomplish tasks like generating email addresses for an SMTP address space for your public/registered DNS domain.These rules should not be deleted, and the recipient policy GUI actually prevents you from doing so.
If you need to apply the policy to all OU recipients, you can either use the common attributes or one of the extension attributes -- perhaps by populating one of them with the name or the distinguished Name of the OU, or some other string.