And additional load from OAB generation and distribution cycles running more frequently may be undesirable to some administrators.
But, assuming you do want to improve this situation in your environment, here is what you can do about it.
Consider the following process: So it is easy to understand why changes may not appear in the address book for cached-mode Outlook users for 24-48 hours after the change is actually made.
Note: a good way to verify whether an inconsistency is OAB-related or not is to use Outlook Web App to look up the person in the address book.
In order for some GAL entries to show up properly you may need to turn off Cached Exchange Mode.
If OWA shows the correct details, and cached-mode Outlook does not, then it is likely an OAB-related issue whether that is simply a normal delay as shown above, or possibly an OAB problem of some kind. Well first of all, consider whether you should take any action at all.
A delay for changes appearing in the OAB may be perfectly acceptable to some organizations.
Open up the latest log file in the directory and see what errors are being reported by the client.
In our case, we had these error messages: Notice the error “Is Local OABFile Current: Manifest Enforcement Disabled And Local File Too Old”.This document seeks to address and clarify the small misunderstanding surrounding the GAL (Global Address List) and the OAB (Offline Address Book).