Use Update Registration Tool to Import Hotfixes in SCCM

This tutorial demonstrates how to use the update registration tool to import hotfixes in SCCM. The out-of-band updates released for SCCM are not available in the Microsoft cloud service, and they must be imported using the update registration tool.

The majority of the hotfixes released for Configuration Manager appear in the updates and servicing node of the console for installation. However, some updates require importing them manually in the SCCM console for installation.

When you need to install an out-of-band release and the update or hotfix file name ends with update.exe, you use the update registration tool. This tool imports the update to the Configuration Manager console. It allows you to extract and transfer the update package to the site server while also registering the update in the Configuration Manager console.

The difference between an out-of-band update and a hotfix file is as follows: The out-of-band release has .update.exe file extension, whereas a hotfix file has the .exe file extension. The OOB update requires the update registration tool to register in the console, whereas the hotfix file requires the hotfix installer to install the update.

Prerequisites

The prerequisites for using the update registration tool in SCCM are as follows:

• This tool only installs out-of-band updates that end with the full .update.exe file extension.
• The service connection point can be in online or offline mode.
• You must always run the hotfix registration tool on the server with the service connection point site system role.
• Starting in SCCM version 2107 and later, the service connection point requires .NET version 4.6.2, and version 4.8 is recommended.
• When you run the tool on the service connection point, the account that you use needs the following configurations:
  • A local Administrator
  • Write permissions to the following folder: \EasySetupPayload\offline

Import a hotfix using Update Registration Tool in SCCM

The steps for importing a hotfix into SCCM using the update registration tool are as follows:

Step 1: On the computer that hosts the service connection point, launch the command prompt with administrative privileges. Then change directories to the location that contains the update file. The update file name uses the following format: —ConfigMgr.Update.exe.

Step 2: Run the following command to start the update registration tool: <Product>-<product version>-<KB article ID>-ConfigMgr.Update.exe

Step 3: To register the update, on the Configuration Manager update registration window, click Next.

Step 4: Close the Configuration Manager Update Registration window. After the hotfix is registered, it appears as a new update in the Configuration Manager console within 24 hours. You can speed up this process by going to the Administration > Updates and Servicing node and selecting Check for Updates.

Step 5: In the Configuration Manager console, go to the Administration workspace and select the Updates and Servicing node. The hotfixes that you’ve imported are now available to install.

Log Files for Update Registration Tool

The update registration tool logs its actions to a .log file on the local computer. The log file has the same name as the hotfix file and is located in the %SystemRoot%/Temp folder. This log file is used for troubleshooting issues with the update registration tool.

If this log file isn’t created, it means the hotfix registration tool has been initiated correctly. You may not see the update imported in the SCCM console. To resolve this issue, run the update registration tool again and complete the import wizard.

If the imported hotfix status shows as ‘Downloading‘ in the SCCM console, you should review the dmpdownloader.log file on the site server. Notice that the .cab file (hotfix update file) is downloaded inside another folder, “Offline” within the EasySetupPayload.

Here is a full list of Configuration Manager logs for troubleshooting common issues.