2016 oab not updating
One affected public-folder based OAB distribution and the other affected web-based distribution.
I want to provide some hints on things that need to be checked in order to follow the OAB generation and publishing process from the server to the client.
Then you need to check the application event log for entries of source “MSExchange SA” and category “OAL Generator”, so events like this one In order to have the system log these events it is a best practice to have event logging level increased for this category on a permanent basis, because you might be missing important events otherwise in case OAB creation fails.
The flow of events will also show which version of the OAB has been successfully created and which have failed.
While this info is great technical background, in this post I want to shed some light on the publishing of the OAB through Public Folders and through Web-based distribution, especially on where to look first.
It is important to note, that I am concentrating on a domain joined Outlook client.
We continue on the mailbox server that created the OAB.While checking this list, the administrator can be sure that the OAB has been generated successfully and check if it has been published at the place where the Outlook client is expecting to find it.At the end of this post, I will give a recommendation regarding the best way in my opinion for rolling out a new OAB to your whole user base, in case you face a situation where a full OAB download for all Outlook clients is necessary.One of the most important events will tell you that the generation process has published the OAB to the public store.This event will also tell you the OAB GUID and, even more important, the OAB sequence number (1 in this case): The mailbox server will use the public store it is pointing to for publishing the OAB.