New SCCM CB 1710 Rollup Update KB4088970 for Co-Managed Devices

New SCCM CB 1710 Rollup Update KB4088970 for Co-Managed Devices. Microsoft SCCM team released a new rollup update KB 4088970. Is the KB 4088970 not available in your updates and servicing node? Don’t worry. Your SCCM infra is fine without this rollup update.

Rollup update applies when your SCCM infra satisfies the following conditions (prerequisites). Video tutorial to explain the needs of Rollup Update KB4088970.

New SCCM CB 1710 Rollup Update KB4088970 for Co-Managed Devices

Prerequisites to get KB 4088970 in SCCM CB 1710

  1. SCCM CB 1710 Rollup HotFix KB4057517 should be installed
  2. Co-Management Feature \Administration\Overview\Cloud Services\Co-management should be enabled on your SCCM environment

Prerequisite  #1

SCCM CB 1710 Rollup HotFix KB4057517 is the major hotfix released by the Microsoft SCCM product group. This hotfix contains 13 fixes as I listed “To Fix 13 Issues Install Hotfix KB4057517 of SCCM CB 1710“. If you didn’t install the KB KB4057517 in your SCCM infra, you won’t get the latest KB4088970 in your updates and servicing node.

  • SCCM CB 1710 Console via – \Administration\Overview\Updates and Servicing
SCCM CB 1710 Rollup Update KB4088970
New SCCM CB 1710 Rollup Update KB4088970 for Co-Managed Devices

Prerequisite #2

The second prerequisite to getting the KB 4088970 in your SCCM environment is related to the co-management feature. Are you already using the co-management feature in SCCM CB 1710 environment? If so, the KB 4088970 will be available to download and install in your environment.

Patch My PC

You should have one co-management production policy in your SCCM environment, as seen in the above screen capture. More details about the co-management setup are available in my following post. “How to Setup SCCM CB and Intune Co-Management“.

  • SCCM CB 1710 Console – \Administration\Overview\Cloud Services\Co-management

When do you want to install SCCM KB 4088970?

The automatic enrollment process may fail on SCCM, version 1710 clients. A message that resembles the following is recorded in the comanagementhandler.log file on the SCCM client:

  • Intune Standalone Account ID is null or does not match MDMTenantID

Note This issue occurs after the installation of KB 4057517, Update rollup for SCCM CB, version 1710.

New SCCM CB 1710 Rollup Update KB4088970 for Co-Managed Devices

What are the DLL changes in SCCM KB 4088970

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table.

File nameFile versionFile sizeDateTimePlatform
Ccm.dll5.0.8577.1111191,36830-Jan-201802:15x64
Comanagementhandler.dll5.0.8577.1111225,16030-Jan-201802:15x64
Comanagementhandler.dll5.0.8577.1111177,03230-Jan-201802:15x86

Resources

Automatic enrollment for co-managed devices fails in SCCM CB 1710

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc……………

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.