Exchange 2016 OAB After running into this issue, I fired up my Exchange 2016 RTM lab and I was able to reproduce the issue with a good copy and a failed and suspended copy of the database where the OAB generating mailbox is located.
This would leave the source database mounted and the destination (the second database copy) would end up in a “Failed and Suspended” state.
We should also check to make sure we can update the OAB using Power Shell.
So, first, check to see where the mailbox is: Which gives us this result: Then we can check and the database is mounted: Next we can try to update the files for the OAB.
Exchange 2013 has gone through an evolution in the way the Offline Address Book is generated and maintained.
While most of the changes are advantageous, I ran into a chink in the armor while working with a customer who was having an issue with Exchange 2013 DAG replication.