New SCCM 2103 Hotfix KB10582136 – Tenant Attach Update

Prajwal Desai
Posted by Prajwal Desai
New SCCM 2103 Hotfix KB10582136

A new SCCM 2103 hotfix KB10582136 has been released by Microsoft that’s basically a tenant attach update. The KB10582136 for SCCM 2103 includes the reporting fixes for Tenant Attach scenarios.

The SCCM 2103 hotfix KB10582136 should appear in the updates and servicing node of the console. Note that you must install KB10036164 rollup first and only then the KB10582136 update appears in the console.

Along with hotfix KB10582136, Microsoft has released ConfigMgr 2103 hotfix KB10589155 to resolve the issues with the Configuration Manager client. There is no specific order in which you install these hotfixes. You must read the hotfix description and if you know it applies to your setup, install it.

You can read more about this hotfix KB10582136 from Microsoft documentation. This update does not require a computer restart but may initiate a site reset after installation.

This update KB10582136 replaces the below updates. If you haven’t installed the below updates, you can skip installing them and directly install the update KB10582136.

  • KB10216365: Unable to move site database to SQL Always On availability group in Configuration Manager, version 2103.
  • KB10372804: Using the MBAM Agent to escrow BitLocker recovery keys generates excessive policies in Configuration Manager, version 2103.

Install SCCM 2103 Hotfix KB10582136

To install SCCM 2103 hotfix KB10582136 :-

  • Launch the Configuration Manager console.
  • Go to Administration\Overview\Updates and Servicing.
  • Select Configuration Manager 2103 hotfix KB10582136 and click Install Update Pack.
Install SCCM 2103 Hotfix KB10582136
Install SCCM 2103 Hotfix KB10582136

A warning appears because ConfigMgr 2107 update is available which is actually the latest update. If you are installing Configuration Manager 2107 update, you don’t need to install this hotfix. A newer update pack than what you have selected is available. It is recommended that you install the latest update pack. Do you still want to install this update pack? Click Yes.

Install Configuration Manager 2103 Hotfix KB10582136
Install Configuration Manager 2103 Hotfix KB10582136

The ConfigMgr 2103 hotfix KB10582136 includes only Configuration Manager site server updates. Therefore, there will be no console upgrade or client agent upgrade after installing KB10582136. I am going to ignore the prerequisite warnings while installing KB10589155. Click Next.

SCCM 2103 Hotfix KB10582136
SCCM 2103 Hotfix KB10582136

Select I accept the license terms and privacy statement. Click Next.

Accept the license terms
Accept the license terms

On the Cloud Attach window, you can uncheck the enable MEM admin center and enable automatic client enrollment for co-management. Click Next.

If you have already enabled Cloud attach during any previous hotfix installation, you will not see the below window.

SCCM 2103 Hotfix KB10582136
SCCM 2103 Hotfix KB10582136

On the Summary window, click Next and on the Completion window, click Close.

ConfigMgr 2103 Hotfix KB10582136
ConfigMgr 2103 Hotfix KB10582136

You can monitor the hotfix KB10582136 installation from the Monitoring workspace of Configuration Manager console. Go to Monitoring\Overview\Updates and Servicing Status. Right click Configuration Manager KB10582136 hotfix and click Show Status.

The hotfix installation takes roughly around 20 to 45 minutes to install. Under the Updates and Servicing status, the status of the update KB10582136 now shows as Installed. This means the hotfix KB10582136 has been installed successfully.

Install SCCM 2103 hotfix KB10582136
Install SCCM 2103 hotfix KB10582136

You don’t need to restart the server after installing the hotfix KB10582136. The update doesn’t include console or client update.

If you have secondary sites, you must manually update the ConfigMgr 2103 hotfix KB10582136. To update a secondary site in the Configuration Manager console, select Administration > Site Configuration > Sites > 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.

Share This Article
Prajwal Desai
Posted by Prajwal Desai
Follow:
Prajwal Desai is a Microsoft MVP in Intune and SCCM. He writes articles on SCCM, Intune, Windows 365, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information.
2 Comments