After OAB generation has finished, the mailbox server publishes the OAB to the public folder database its private store is pointing to and / or is saving the OAB on the local disk, in order to enable the Client Access Servers (CAS) to pull it from there for the web-based distribution method.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.
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.
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.
In case your client is not member of a domain, please see this article: Troubleshooting Error 0x8004010F When Outlook 2007 Clients Download OAB. When you create a new OAB, you must at least specify the following attributes: In order to work through the process, you need to check a few first things first, as follows.
From the properties of the OAB you can check which server is the generating server: in the EMC (Exchange Management Console) this property is called “Generating server”; in the EMS (Exchange Management Shell) you need to look for the “server” attribute.
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.
The OAB file is compressed and will be downloaded by the client in a compressed format and the client will extract the OAB file afterwards.
So the compressed file size should be meaningful and match your (compressed) GAL size.
You can see the sequence number (“1”) in the end of the subject and when it was received (in my example I took the screenshot at a later date). When the OAB generation processes run over several days, you will also see the delta / differential OAB files.