I have four Exchange servers across four sites. I've made updates to my Global Address List (GAL), but those updates...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
are not replicating to all four sites. How can I fix this once and for all?
Any time you run into an Exchange Global Address List issue, the first place to investigate is the application event logs on the Exchange server that is generating your offline address book (OAB). There are too many event IDs to reference here, but most that are OAB generation-related should be resolved if you updated your Exchange server with the latest service pack and rollup.
You should also check that all four sites can communicate on port 25, in order to allow replication traffic to pass through. The easiest way to test this is to use an old Microsoft tool known as Portqry.exe. Once installed, use the command line to navigate to the directory that you installed the tool to and run the following command:
Portqry.exe -n <remote server name> -p tcp -e 25
If this is working properly, you should receive a "listening" response.
You should also make sure that the OAB references on each site's Exchange server are correct. This helps make sure that Outlook 2007 (and higher) clients using Web access for OAB updates point to the right location. This is located in the Exchange Management Console -> Server Configuration -> Client Access Server -> OAB tab.
Similarly, if your organization uses public folders, make sure that mailbox servers at each site are listed in the replication tab within public folder properties. They should be inherited by any child folders of the OAB public folder by default, but it's not always the case. Therefore, it's important to double check.
Remember, the slower your links are between the sites, the slower replication will be between servers. Thus, Exchange Global Address list updates will process slower as well. If you make a change to your organization and want to ensure that replication occurs immediately, you can force synchronization using the following Exchange Management Shell command:
Update-GlobalAddressList -identity "Default Global Address List "
About the author
Dave Leaver has worked in the IT industry for the last ten years as an IT support engineer. He currently works for an IT support company in Cheltenham, U.K., supporting more than 1,000 users and spanning more than 40 companies. Leaver specializes in Microsoft system migrations and Exchange Server. Leaver has also been a network administrator for the National Health Service and several large construction companies throughout the U.K.
Dig Deeper on Microsoft Exchange Server Performance
Related Q&A from Dave Leaver
The process used to move an Exchange 2013 database isn't immediately obvious if you're not familiar with the new platform. Here's how.continue reading
A frustrated admin wants to know how to remount his Exchange 2010 database after discovering event ID 5003. One of our experts offers proper guidance.continue reading
One admin's Outlook Anywhere instance won't connect after an Exchange 2010 migration. Find out what our expert suggests.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.