In Exchange 2007, recipient management is incorporated into the Exchange Management Console and Exchange Management Shell based on Windows PowerShell technology. Shell based management for these...
Updated Jul 01, 2019
Version 2.0
Blog Post
6 MIN READ
Top Exchange 2003 Recipient Problems and how they're fixed in Exchange 2007
A little concerned about the EAP statements in regards to a hosting enviornment.
In 2003 - we actually liked the fact that we could have 2000 users fall under a recipient policy (Company = X, Department = Y), but that the RUS would NOT update their addresses unless the object had the special update GUID on it. This allowed us to maintain legacy addresses on those users (including a 1 off default reply SMTP address), while ensuring any new accounts were stamped correctly.
The way I ready your statements about EAP, those 2000 pre-existing users will get re-stamped to match the policy exactly, even if we want them to be ignored by default. So day 1, we will have to perform a lot of work to keep the EAP from doing its job, or tell the thousands of legacy users that they will have their SMTP addresses changed (which will fly over like a brick).
Please clarify how we can get the EAP to ignore legacy users that fall within the same LDAP filter?
In 2003 - we actually liked the fact that we could have 2000 users fall under a recipient policy (Company = X, Department = Y), but that the RUS would NOT update their addresses unless the object had the special update GUID on it. This allowed us to maintain legacy addresses on those users (including a 1 off default reply SMTP address), while ensuring any new accounts were stamped correctly.
The way I ready your statements about EAP, those 2000 pre-existing users will get re-stamped to match the policy exactly, even if we want them to be ignored by default. So day 1, we will have to perform a lot of work to keep the EAP from doing its job, or tell the thousands of legacy users that they will have their SMTP addresses changed (which will fly over like a brick).
Please clarify how we can get the EAP to ignore legacy users that fall within the same LDAP filter?