Image via CrunchBase
The problem may occur when the Priority of these problematic recipient policy is set to highest.
Solution:
- Open ADSI EDIT.
- Configuration(server.domain.com)/CN=Services/CN=Microsoft Exchange/CN=<Exchange Org Name>/CN=Recipient Policies.
- Right click the problematic recipient policy and select Properties. On the Attribute Edit tab, ensure Show only attributes that have values is check.
Find attribute msExchPolicyOrder and Change the attribute msExchPolicyOrder for that policy and set its value to 2. - Wait for the change to replicate through the domain.
- Try to delete that policy from the ESM
About the Author
Jason Benway Has Written 1320 Articles For Us!
I am the admin of this site and enjoy enterprise technologies and gadgets.
Related posts:
- Recipient Policies and pure Exchange 2000/2003 sites
- Exchange 2003 SP1 install for SBS
- Exchange 2003 /3GB Quick Reference
- Setting up an exchange 2003 cluster?
- ActiveSync Web Administration Tool (Exchange 2003)
Related posts brought to you by Yet Another Related Posts Plugin.
So this is how you do it! Thanks, I had this problem for quite some time now.
Stancjes last blog post..Wrocław 05.06.2009: Mam do wynajęcia
You came right up in my search. Thanks.