Microsoft Exchange Server 2003 Service Pack 1 (SP1) adds new functionality to the Recipient Update Service. When the Exchange Server 2003 SP1 Migration Wizard is used to migrate a user, a new GUID is added to the
MSExchPoliciesIncluded attribute of that user. The GUID that is added to the
MSExchPoliciesIncluded attribute is the following:
{23668AD4-4FA1-4EE8-B2BB-F94640E8FBA0},{26491CFC-9E50-4857-861B-0CB8DF22B5D7}
When the Recipient Update Service is running on an Exchange Server 2003 SP1 server, the Recipient Update Service will recognize that specific GUID and act as if the policy has been applied to that user. This causes the secondary proxy addresses to be added to the recipient.
If recipients were not migrated by using the Exchange Server 2003 SP1 Migration Wizard and if your Recipient Update Service is running on an Exchange Server 2003 SP1 server, you can still take advantage of this new functionality. To do this, add the GUID that was mentioned earlier to the
MSExchPoliciesIncluded attribute of those recipients whose proxy addresses should be generated. The
MSExchPoliciesIncluded attribute can either be manually set or set in bulk by using a script or an LDIFDE import.
For more information about the steps that are used by the Recipient Update Service to evaluate recipients, click the following article number to view the article in the Microsoft Knowledge Base:
328738
How the Recipient Update Service applies recipient policies
When you create a new account, there is no proxy address. The Recipient Update Service applies all policies to the mailbox and all the proxy addresses are stamped. However, when you migrate a user who already has the proxy addresses stamped, when the Recipient Update Service parses this account, it does not change the addresses that already exist. The Recipient Update Service only stamps the account with recipient policy proxy addresses that are not present.
For more information about how the Recipient Update Service applies recipient policies, click the following article number to view the article in the Microsoft Knowledge Base:
328738
How the Recipient Update Service applies recipient policies