Forum Discussion
Enabling OneDrive Health Sync
Hello, once again being victimized by Microsoft đ
Have a series of users reporting constant sync errors. We've reached out to Microsoft technical support and they just successively told us it was garbage and not to use it.
Anyway, trying to get the Sync Health Dashboard to work, based off this document:
https://learn.microsoft.com/en-us/sharepoint/sync-health?tabs=windows
It's one of those Microsoft documents that the community CAN'T edit, so of course - it's out of date and incorrect. From what I can figure, based on research from other sources, most of this process is now arbitrary, and you have to create a 'EnableSyncAdminReport' in some policy location in the registry.
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OneDrive < already exists, but not referenced by documentation
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\OneDrive < key doesn't exist, but is referenced by documentation.
but this sorta 'try it and see' methodology really upsets me. Anyone have any insight to this, and why the documentation team fails to update the documentation, or whether this process will work or not?
1 Reply
The policy path not existing is normalâit is not created by installing OneDrive. Create HKLM\SOFTWARE\Policies\Microsoft\OneDrive and set a DWORD named EnableSyncAdminReports (plural) to 1. The older SyncAdminReports value is no longer supported, and EnableSyncAdminReport (singular) is not the documented value.
Before rollout, open Microsoft 365 Apps admin center > Health > OneDrive Sync > Setup and make sure a Tenant Association Key has been generated. If using Intune Settings Catalog, enable âEnable sync health reporting for OneDriveâ and provide the key in âSync Admin Reportsâ; Group Policy can deploy the same supported setting.
Pilot on a few machines first. Clients need OneDrive 22.232 or later, a signed-in user, access to clients.config.office.net, and enough uptime. Reporting is not immediate: Microsoft says devices can take up to three days to appear, with status normally updating about every 36 hours. Verify locally with reg.exe query against the policy path.
