Search Engine: Elastic

Article ID: 116686, created on Aug 8, 2013, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 5.4


The Address Book Policy (ABP) is not being applied automatically to new Exchange mailboxes in the scope of a particular Hosted Exchange organization. It can be verified by executing the following cmdlet in the Exchange Management Shell (EMS):

Get-Mailbox -Identity <user login> | fl name, AddressBookPolicy
Name              : test
AddressBookPolicy :

Replace the <user login> with the problem mailbox name (e.g. "").

As shown above, the Address Book Policy (ABP) name is blank, which means that the ABP is not assigned to the mailbox.

You can check if the ABP exists using the following cmdlet in the EMS (the ABP probably exists and is just not assigned to the mailbox):

Get-AddressBookPolicy <ABP name>

Affected Exchange versions:

  • Exchange 2010 SP2
  • Exchange 2013


On Exchange mailbox creation POA searches for an Active Directory Other Well Known Object (OWKO) that points to the ABP for the Exchange organization the mailbox belongs to.

In case such OWKO does not exist POA can not find ABP and does not assign it to the new mailbox.

If this OWKO for the ABP has the following common format:

B:32:E375E41B3AE442039E1CC48E0F093EC6:CN=<ABP name>,CN=AddressBook Mailbox Policies,CN=chost,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<Provider Domain Part 1>,DC=<Provider Domain Part 2>

The OWKO GUID has the value E375E41B3AE442039E1CC48E0F093EC6 for all Exchange organizations in any Exchange 2010 SP2/Exchange 2013 environment.


Follow the steps below to resolve the issue.

  1. Check if the OWKO pointing to the APB exists for the Exchange organization in question using instructions from the Parallels Knowledgebase article #10014: How to get OWKO of Active Directory object.

  2. Create the missing OWKO using instructions from the Parallels Knowledgebase article #10015: How to edit OWKO of AD object: add/remove data by MPF call.

It is easy to find the ABP Distinguished Name using the following cmdlet in EMS:

Get-AddressBookPolicy <ABP name> | fl DistinguishedName
  1. After adding the missing OWKO, create a test mailbox in the POA Customer Control Panel and check if the ABP has been assigned to it using the Get-Mailbox cmdlet as described above.

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF