Default global address list not updating

6854933580_2c8b688306_z

However sometimes in large complex organisations we have a situation where a new joiner joins and their colleagues want to email them immediately, but they don’t appear in Outlook for them so they call the Helpdesk “Why isn’t Joe Bloggs in the GAL??

” Well, the truth of the matter is that our new joiner Joe is in fact , an update to the Address Book won’t become available to the user until about 48 hours after the change.

It still takes a few minutes to locate his information.

There is easily enough technology to solve this problem but it is often ignored.

If you are a system admin that is on the lookout for ways to optimize the smartphone experience, GAL search maybe a weak link.

Many organizations prefer to sync the Jamie Gomez has a lab in the basement of the oldest building on campus. You open the contacts icon on your i Phone and discover that he isn’t in your address book.

Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from Tech Target experts.

default global address list not updating-51default global address list not updating-20default global address list not updating-70default global address list not updating-49

If these attributes are present, then the AD Objects that are Mail-Enabled or Mailbox-Enabled will appear in the GAL – and ultimately the Offline Address Book.

Rather than waiting 24 hours for Outlook to update the Offline Address Book on its own, you can force an update via the Send/Receive menu button.

You can disable the option “Download changes since last Send/Receive” to make sure you get a complete fresh copy of the OAB but this could take longer to download.

To solve this issue, you need to do the following steps.

Start Adsi Edt (be careful with this change) Go to default Naming Context Microsoft Exchange System objects Open the properties of the objects which gave the warning in the Power Shell message.

/Microsoft Exchange System objects/OAB version 2″ is invalid and couldn’t be updated.” This warning occurs in my situation way after the migration of exchange 2007 to exchange 2013.

You must have an account to comment. Please register or login here!