A delay for changes appearing in the OAB may be perfectly acceptable to some organizations. Well first of all, consider whether you should take any action at all. So what can we do to optimize this process? 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. 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. 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. ![]() The OAB is updated at next Outlook startup the day after that.Up to 8 hours later (ie as late as 1pm) the OAB file distribution process runs.At 5am the next day the OAB generation process runs.At 9am the help desk changes the user’s surname.So in real world conditions that process may actually look like this. The OAB is downloaded to the Outlook client (at startup).The OAB file distribution process runs (every 8 hours by default).The OAB generation process occurs (5am daily by default). ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |