Event Type: Information Event Source: MSExchange AL Event Category: Address List Synchronization Event ID: 8169 Date: 3/27/2006 Time: AM User: N/A Computer: EX-01 Description: Retrieved all directory changes under: 'DC=tlaconsulting, DC=ca'.
The Exchange Server Recipient Update Service (RUS) is important to the overall health of your messaging environment.
I have setup 3 new Org units in the AD, and created 3 more Org units called Users below them, then added the users there.
Now i run the apply policy, but it seems the only policy being applied is the DEFAULT policy.
When you edit a mail-enabled object's properties and select the Automatically update e-mail addresses based on recipient policy check box (on the E-mail Addresses tab of the object's Properties dialog box), as Figure 1 shows, the RUS determines which recipient policy to apply to the object, then carries out the instructions that the policy contains.
Some deployments, such as hosted application service provider (ASP) or ISP installations, opt not to use the RUS to generate email addresses.
However, if any of these are deleted using a tool like ADSIEdit, which the Exchange System Manager GUI has no control over, it will prevent critical services like the information store service and MTA Stacks service from starting. Recipient policies based on organizational units (OU): Another misconception and a frequently asked question in many forums is how one can apply a recipient policy to recipients in a particular OU, or apply the policy to an OU so it gets applied to all recipients in that OU. Recipient policies are applied to recipients filtered on recipient attributes, such as department, location, city, or country.
Recipient Update Service creates and maintains Exchange Server 2003-specific attribute values in Active Directory.
If you create a mailbox for a user, Recipient Update Service automatically generates the user's SMTP address and any other proxy addresses that you defined for your recipients.
In small organizations, the RUS often stays in the background.
However, if you work with large or complex deployments, you're likely to find yourself trying to cope with multiple recipient policies or wishing you understood why the RUS doesn't do quite what you'd expect it to do.