Troubleshooting OAB downloads.

Troubleshooting Offline Address Book downloads in Exchange/Outlook 2010

First thing, verify the OAB is being generated. On the Generating server you’ll have 2 directories.

D:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB\85c8d192-d03a-4558-996e-d90c4c907d04


D:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB\d6ec84a4-95a2-418b-ae44-dd1ce5a4ba35

Inside both you should have an oab.xml file and numerous .lbx files looking something like this



On the other Servers, you’ll only have D:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB\ directory.

If you restart the Microsoft Exchange File Distribution service, you should see the directory update with files from the current time.

This gets updated automatically according to your maintenance schedule once a day. You’ll want to make sure that’s happening.

If you’ve only got an oab.xml file, and the files will not replicate, try deleting the oab.xml and restart the service again.

Turn up logging –

Set-EventLogLevel -Identity "MSExchangeSA\OAL Generator" –Expert

Run update-offlineaddressbook and restart the Microsoft Exchange File Distribution service, then check the event logs

If the servers are replicating and you still can’t download. Here are a few things to ask yourself.

Is the Internal and external URLs set?

Run Get-OABvirtualdirectory to see what they are.

What servers are in the distribution list?

Get-OABvirtualdirectory will show that as well.

Are you using a load balancer for the URL?

This can be bypassed with a host file (be sure to bypass all URLs), or by setting the Internal URL back to the server name.

If you are using HTTPS are all names in the certificate?

Run test-autoconfigure from the outlook client.

Run and test autoconfigure.

Getting the wrong URL? Did you set sitescope and affinity? If you have multiple sites with exchange, you’ll need to configure it so your sites connect to the right server(s)

Set-ClientAccessServer -Identity "ServerName" -AutodiscoverServiceInternalURI "https://internalsitename/autodiscover/autodiscover.xml" -AutodiscoverSiteScope "SiteName","SiteName2","SiteName3"

Set-ClientAccessServer -Identity "ServerName(in site2)" -AutodiscoverServiceInternalURI "https://internalsitename2/autodiscover/autodiscover.xml" -AutodiscoverSiteScope "SiteName4","SiteName5","SiteName6"

So how is it different in Exchange 2013? Read for yourself.




Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s