End users report their address books are out of date and they are unable to share calendars or locate new users in the Global Address List.
This indicates the clients are not getting their daily Offline Address Book (OAB) update from the Exchange servers.
Servers– Server 2008R2 servers running Exchange 2010 SP1
- Exchange01 – Mailbox Server (Upgraded from Exchange 2003 to 2007, and finally to 2010 SP1.)
- Exchange02 – Client Access Server
- Windows 7 Sp1 running Outlook 2010
- Windows XP SP3 running Outlook 2010
The initial suggestion for our end users was to attempt a manual Offline Address Book (OAB) download. No luck, the end users provided the following errors: 0x8004010F and 0x8004011D which basically imply the client cannot find the OAB.
Discovering the issue existed server side led me to the OAB configuration on our Exchange servers. It turns out our Distribution Point was configured incorrectly.
The ‘Enable public folder distribution’ was checked which only supports OAB for Outlook 2003 SP1 and earlier clients. We do not support Outlook 2003 clients so this box needs to be unchecked.
The “Enable Web-based distribution” provides access to the OAB for Outlook 2010 or Outlook 2007 clients. In this scenario the Client Access Server (CAS) is added to the “Distribute the offline address book from the following virtual directories:” and will be the only Distribution Point checked. Distribution Points can be checked simultaneously if your Exchange setup serves Outlook 2003, 2007 and 2010 clients.
The settings from the initial Exchange 2003 installation carried over through each upgrade. Keep this in mind when upgrading Exchange as the original servers configuration will likely be propagated potentially causing undesired results.
After changing the Distribution Points the problem remained unsolved, as the OAB was still unavailable.
Executing Test-OutlookWebServices within the Exchange Management Shell (EMS) showed a test account and mailbox did not exist. To create the test account for Outlook web services the following command must be run from the C:\program files\microsoft\exchange server\v14\scripts directory:
[PS] C:\program files\microsoft\exchange server\v14\scripts>get-mailboxServer | .\new-TestCasConnectivityUser.ps1 -OU "domain.co/IT Staff/users"
(make sure to use ” ” if you include spaces)
Enter a strong password that satisfies the minimum complexity requirements within the domain.
Verify the intent to create the test user by pressing Enter to confirm or Ctrl+Break to cancel.
Now the Test-OutlookWebServices cmdlet can be used to troubleshoot the OAB among quite a few other aspects of Exchange Server.
[PS] C:\program files\microsoft\exchange server\v14\scripts>cd\ [PS] C:\>Test-OutlookWebServices -ClientAccessServer "Exchange02" ***Output Omitted for brevity*** RunspaceId : 6e16aec1-5caf-4296-a56b-82df06fa5d63 Id : 1015 Type : Warning Message : [EXCH] The OAB is not configured for this user in the AutoDiscover response received from https://mail.domain.co/Autodiscover/Autodiscover.xml.
This confirms that the new OAB settings have not propagated. Within the EMC navigate to ‘Organization Configuration > Mailbox’ and select the ‘Offline Address Book‘ tab. Right Click the OAB and select Update. This will force an OAB Generation (OABGen). Upon completion any changes to the OAB configuration become available to clients.