Paul is a Microsoft MVP for Office Servers and Services.He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server.

default offline address list not updating-9

He moonlights as a technical author and consultant.

This morning I was asked to update the Global Address List and Offline Address Book in an Exchange environment.

On top of these delays, if a client does not close/open his or her Outlook, it can take even longer for a change to take place. p=312 It's the Exchange CAS not updating the Offline address book file: C:\Program Files\Microsoft\Exchange Server\V14\Client Access\OAB\Something-Something-Darkside\I just restarted the Microsoft Exchange File Distribution service on the CAS server and it updated.

When a new email account is created in Exchange it will not normally appear in the address book of others until the following day.

Any mailbox users who do not have an existing OAB assigned to their mailbox directly, or to the mailbox database that they are located on, will download the entire OAB from the new default OAB that Exchange 2013 creates.

In organizations with a large OAB or distributed network environment this is obviously not ideal.Frequently users report recipients missing from the GAL. Scenario:– Recipients are not hidden from Exchange Address Lists– Recipients do show up in the “All Users” Address List– Recipients do show up when Outlook’s not in Cached Mode– Recipients resolve in Outlook Web Access Some recipients may not be included in the Offline Address Book when it is generated, for a number of reasons. New users don’t show up in the GAL for clients using Outlook 2003 Cached Mode clients, because Outlook uses an Offline Address List (aka “Offline Address Book” or OAB), which is generated once every 24 hours by default [read previous post “New user does not show up in GAL“] In this case there are who did show up in the GAL earlier but have disappeared now.The reason is that the OAB is generated in the MAILBOX role and needs to be copied to the CLIENT ACCESS role.The CLIENT ACCESS role checks for changes every 8 hrs. p=77 Also you can read up on how the OAB is distributed and the scheduling of that distribution here: Something wrong with Schema update or did you mess up the infrastructure.