Image representing Microsoft as depicted in Cr...

Image via CrunchBase

The problem may occur when the Priority of these problematic recipient policy is set to highest.

Solution:

  1. Open ADSI EDIT.
  2. Configuration(server.domain.com)/CN=Services/CN=Microsoft Exchange/CN=<Exchange Org Name>/CN=Recipient Policies.
  3. 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.
  4. Wait for the change to replicate through the domain.
  5. Try to delete that policy from the ESM
Enhanced by Zemanta

Related posts:

  1. Recipient Policies and pure Exchange 2000/2003 sites
  2. Exchange 2003 Databases and the Exchange store
  3. Active Directory &amp; Exchange Schema Versions
  4. ActiveSync Web Administration Tool (Exchange 2003)
  5. Exchange 2003 SP1 install for SBS

Related posts brought to you by Yet Another Related Posts Plugin.