Offline address book exchange 2016 not updating

Example: DB1 hosts the Organization Mailbox and has copies on servers Exch1 and Exch2. The following command can be used to activate DB1 on Exch2 and therefore make it the OAB generation server: Move-Active Mailbox Database DB1 -Activate On Server Exch2 Note: Review guidelines mentioned in “Placement of Organization Mailbox” below before changing the OAB Generation server.Administrators can create additional Organization Mailboxes for fault tolerance or for serving users in a geographically disbursed Exchange deployment.

Offline address book exchange 2016 not updating

We will refer this mailbox as “Organization Mailbox” throughout the article.

Exchange Server 2013 mailbox server hosting the Organization Mailbox will generate all OAB’s defined in the environment.

Use the following command to list the arbitration mailboxes with persisted capability of OABGen and database on which this mailbox is hosted: Get-Mailbox -Arbitration | where | ft name,database Step2: Identify the mailbox server where the database hosting organization mailbox is mounted Use following command to identify active copy of mailbox database: Get-Mailbox Database Copy Status db1 The server where database status is “mounted” is the current OAB generation server.

There are two methods of changing the OAB generation server.

For a non-DAG environment, use following command to identify the OAB Generation servers: Get-Mailbox -Arbitration | where | ft name,servername For a DAG environment, identifying OAB generation server(s) is a two-step process.

Step1: Identify the mailbox database hosting organization mailbox with OAB Gen capability.

Get-Mailbox -Arbitration -database db1| where | New-Move Request -Target Database db2 This method is more suited for environments that have single copy of mailbox database hosting the Organization Mailbox.

This method is suited for environments that have multiple copies of the mailbox database hosting Organization Mailbox.

The management and administration is different in Exchange 2013 because of architecture changes.

Tags: , ,