Recipient update service not updating
Proxy addresses are always calculated and sent to the task which will re-write them to the directory.
Other attributes, such as name etc, are only written to the directory if they were specified in the set command to be changed.
If we found an object that was changed after the USN stamped on the RUS, we knew we would need to take action against it.
In this case the RUS always utilized a single Exchange server to calculate addresses and a single domain controller to read objects and write objects.
It won’t set if the proxy Addresses were manually added• Set other mail attributes, like target Address, text Encoded ORAddress and mail.
Address List:• Set the show In Address Book attribute based on the Address Lists present.
The RUS then calculates valid email addresses, and provides them back to the set task.
Once this information is provided the set task then commits the changes to the directory.
The email address change should include a primary SMTP address of Barbara. The attributes written to the directory are as follows: sn: JONES proxy Addresses (3): smtp: [email protected]; SMTP: Barbara. [email protected] next step of the application is to reset the hide from address book value.
The following command is called: set-user –identity Barbara –last Name Jones –domain Controller DC-2 At this point the task contacts the directory and reads the attributes.
It then contacts an Exchange server, and passes in the current attributes plus the attributes that changed.
If one is not present, the task will look to adjacent Active Directory sites.
Let’s take a look at how this changing from a directory scan to a task based system could cause the symptoms I outlined above.