Once a site has no Exchange 5.5 servers in it, that old "Highest Priority" policy based on legacyExchangeDN isn't needed anymore. As people decommission their 5.5 servers and move to pure Exchange ...
Updated Jul 01, 2019
Version 2.0
Blog Post
Is it possible to have the RUS understand that as an individual person moves from Business unit #1 to Business unit #2, both their own recipient policies keyed on the department field, to have it add the primary address of Business unit #2 and keep the old primary as a secondary?
The way I read things, currently the only way to get the RUS to stamp a new address on an existing mailbox (w/o applying the policy to everyone) is to blank the proxyaddresses field on that mailbox to fool the RUS into thinking it ias new mailbox. This is obviously undesireable.
Basically looking for a solution to have the RUS auto-add new Primary SMTP address as users move between business units w/o affecting the entire populace.
Thanks for the awesome article, it really helped us out well.
The way I read things, currently the only way to get the RUS to stamp a new address on an existing mailbox (w/o applying the policy to everyone) is to blank the proxyaddresses field on that mailbox to fool the RUS into thinking it ias new mailbox. This is obviously undesireable.
Basically looking for a solution to have the RUS auto-add new Primary SMTP address as users move between business units w/o affecting the entire populace.
Thanks for the awesome article, it really helped us out well.