Global address list is not updating outlook 2016
Murray has been working in IT for over 15 years specializing in the Messaging Arena and in particular IBM Domino and Microsoft Exchange and now of course Office 365.Working with like minded colleagues now specializing in very large scale complex migrations from Lotus Notes and On-Premise Microsoft Exchange to Office 365.You can see the list of attributes that will be put into the GAL using When Outlook users are running in cached mode, they rely on the Offline Address Book (OAB) to provide them with access to one or more addresses (that are always available when they are connected directly to Exchange) The OAB is rebuilt and downloaded on a default schedule as shown below.Because of this, a new user may not be visible in the address book, or changes to a user’s name, address, etc.Outlook does not use OS X Directory Services stack Im referring to the Outlook setting located here Outlook I have seen that MS Tech Net document, thank you @jonnydford. I'm using Office 365, so I can only show you what I get from that (below).
Quite often all Administrators, even Exchange Administrators simply refer to the users they see in the Address section of Outlook casually as the GAL for ease of reference, but really more often than not, you are looking at the OAB.
This will update contact information, pictures, phone numbers, etc. Now you have the most up-to-date information from Active Directory in your local address book. Under Send/Receive Groups, you should see an option to "Download Address Book." Now you will be prompted for a few options, and you can choose to update from the Global Address List (this is how your AD should push out contacts). I download the full address book and it loads for a couple of seconds. I open some contact which I haven't updated yet, click on update - it is updated.
Also the Update button seems to have to do something with "Outlook Social Connector" - see the other screenshot I added?
may not be available even though such changes have been made in Active Directory.
This can occur even though no errors are present within the OAB rebuild process.