Clients report Desktop Analytics configuration errors in Configuration Manager, version 2006

Applies to: Microsoft Endpoint Configuration Manager (current branch – version 2006)

Symptoms


After updating to Microsoft Endpoint Configuration Manager current branch, version 2006, clients report Desktop Analytics configuration errors. These are shown as "Windows diagnostic endpoint connectivity" errors on the Connection Health node in the Configuration Manager console. Errors resembling the following are also recorded in the M365AHandler.log on affected clients.

When viewed through the Microsoft Endpoint Manager admin center, multiple Desktop Analytics tabs, such as Assets or Feature Security Updates, contain outdated information or fewer devices than expected.

Update information for Microsoft Endpoint Configuration Manager, version 2006


This update is available in the Updates and Servicing node of the Configuration Manager console for environments that are using Desktop Analytics, and were installed by using early update ring or globally available builds of version 2006.
Customers in the Technology Adoption Program (TAP) must have the private TAP rollup installed before this update will appear.
The following update is required for customers that installed an early update ring build of Configuration Manager, version 2006.

KB 4576791: Update for Microsoft Endpoint Configuration Manager version 2006, early update ring

Restart information

You do not have to restart the computer after you apply this update.

Update replacement information

This update does not replace any previously released updates.

Additional installation information

After you install this update on a primary site, pre-existing secondary sites must be manually updated. To update a secondary site in the Configuration Manager console, click Administration, click Site Configuration, click Sites, click Recover Secondary Site, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files. Configurations and settings for the secondary site are not affected by this reinstallation. The new, upgraded, and reinstalled secondary sites under that primary site automatically receive this update.

Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:

select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')

If the value 1 is returned, the site is up to date, with all the hotfixes applied on its parent primary site.

If the value 0 is returned, the site has not installed all the fixes that are applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site.