1. Overview
🚀 This technical guide addresses a specific synchronization failure where Microsoft Outlook is unable to successfully download the Offline Address Book (OAB) via HTTP(S). IT administrators frequently encounter scenarios where the “Outlook Send/Receive Progress” dialog initializes the OAB download but the progress bar remains indefinitely static or “stuck.” This prevents the local client from updating its directory information, leading to stale address data. Because modern versions of Outlook (2013, 2016, and later) rely exclusively on HTTP-based OAB delivery, ensuring the underlying transport mechanisms are functional is critical for maintaining accurate Global Address List (GAL) data on endpoint devices.
2. Key Technical Details
🖱️ Peripherals and Driver Conflicts: A known, yet often overlooked, cause of OAB sync failure involves outdated drivers for wireless HID (Human Interface Device) hardware. Specifically, legacy drivers for wireless keyboards or mice can interfere with the system’s ability to process the data stream required for address book updates. Admins should verify if the following update is required:
- Microsoft HID Non-User Input Data Filter (found under Optional Hardware Updates in Windows Update).
- Latest IntelliPoint or IntelliType software suites.
⚙️ BITS Policy Restrictions: Since Outlook utilizes the Background Intelligent Transfer Service (BITS) to manage OAB downloads, any Group Policy Objects (GPOs) or local registry configurations that throttle BITS bandwidth can effectively kill the download process. Administrators should audit the following registry hive for restrictive policies:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\BITS
Specifically, look for these DWORD values which may be enforcing transfer limits:
EnableBitsMaxBandwidth(If set to 1, throttling is active)MaxBandwidthValidFromMaxBandwidthValidToMaxTransferRateOnScheduleMaxTransferRateOffSchedule
🛡️ Service State Management: The OAB cannot be retrieved if the BITS service is disabled or hung. For a successful download, the service must be in a “Running” state. Admins can manage this via Services.msc by locating Background Intelligent Transfer Service and ensuring the Startup type is set to Automatic (Delayed Start).
The configuration can also be verified (but should not be modified) via the registry:
Key: HKEY_LOCAL_MACHINE\system\currentcontrolset\Services\BITS
DWORD: Start
- 4 = Disabled
- 3 = Manual
- 2 = Automatic
🔍 Diagnostic Verification: To confirm that a client is indeed attempting an HTTP-based download, administrators can use the “Test E-mail AutoConfiguration” tool.
- While Outlook is running, hold CTRL and right-click the Outlook tray icon.
- Select Test E-mail AutoConfiguration.
- Enable only Use AutoDiscover and click Test.
- Review the Results tab for the OAB URL. If it begins with
HTTP, the client is using the modern web-based distribution method.
3. Impact
⚠️ Operational Impact: When OAB downloads fail, users are unable to see newly created mailboxes, updated distribution groups, or changes to existing contact information. This often results in “undeliverable” reports when users attempt to mail new employees who are not yet in their local cached address book. From an administrative perspective, this issue can be misdiagnosed as a server-side Exchange error, when it is frequently a localized client-side configuration or a BITS policy conflict. Resolving these issues ensures that the local .oab files are properly updated, reducing help desk tickets related to directory discrepancies.
📅 Version Considerations: While Outlook 2007 and 2010 supported both Public Folder and HTTP distribution, Outlook 2013 and newer versions rely solely on HTTP. This makes the health of the BITS service and the absence of restrictive network policies mandatory for all modern Office environments.
Official Source: Read the full article on Microsoft.com