ConfigMgr 2010 Hotfix KB4594177 – Fix Client Notification Issues

Prajwal Desai
Posted by Prajwal Desai
ConfigMgr 2010 Hotfix KB4594177 - Fix Client Notification Issues

ConfigMgr 2010 Hotfix KB4594177 was made available by Microsoft to fix the client notifications problem. Installing the KB4594177 hotfix will prohibit the client notifications from being broadcast to all collection members when triggered on a single computer in a device collection.

This KB4594177 update does not require a computer restart but will initiate a site reset after installation. In addition, there is no client update or console update required after you install KB4594177.

The hotfix KB4594177 applies to ConfigMgr 2010 environments that were installed by using early update ring or globally available builds. KB 4594177 appears in ConfigMgr console with package GUID 1A19DE07-0F36-4959-A2CF-0C957274F9D7. The ConfigMgr hotfix KB4594176 was the previous update for early update ring customers.

In ConfigMgr 2010 console, when you select a subset of devices in the collection membership view and choose an option under Client Notification, it results in all collection members receiving the notification. For example, after selecting one device in a collection and choosing the Restart option, all collection members receive the notification instead of just the selected device.

Ad imageAd image

However, it must be noted that the Start CMPivot and Run Script options are not affected by this issue. This is something that I had tested in my lab. I initiated the reboot on one of the devices in a collection. The other computers also received the client restart notification. To fix this issue, you must immediately install the ConfigMgr 2010 Hotfix KB4594177.

You can wait until the subsequent release if you do not wish to install the hotfix KB 4594177. The deployment might include more fixes than simply the one for the client notifications bug. The ConfigMgr 2010 Hotfix KB4594177 details are listed on Microsoft support site.

ConfigMgr 2010 Hotfix K4594177
ConfigMgr 2010 Hotfix KB4594177

Install ConfigMgr 2010 Hotfix KB4594177

Here are the steps to install hotfix KB4594177 for Configuration Manager 2010:

  • Launch the Configuration Manager console.
  • Navigate to Administration\Overview\Updates and Servicing.
  • Right click Configuration Manager 2010 Hotfix (KB4594177) and select Install Update Pack.
Install ConfigMgr 2010 Hotfix KB4594177
Install ConfigMgr 2010 Hotfix KB4594177

You should now see the Configuration Manager updates wizard. Note that the hotfix includes only the Configuration Manager site server updates. On the General window, click Next.

Install ConfigMgr 2010 Hotfix KB4594177
Install ConfigMgr 2010 Hotfix KB4594177

Accept the license terms before installing the hotfix and click Next.

Accept the License Terms
Accept the License Terms

Click Next on the Summary page.

ConfigMgr 2010 Hotfix KB4594177
Hotfix KB4594177 Summary

On the Completion window, click Close.

ConfigMgr 2010 Hotfix KB4594177
Hotfix KB4594177 Completion

Monitor the KB4594177 Installation

The hotfix KB4594177 installation should be quick because overall the size of the hotfix is small, and it contains just one fix. In the Configuration Manager console, go to Monitoring\Overview\Updates and Servicing Status. Here you can monitor the installation progress of the hotfix KB4594177.

Monitor Hotfix KB4594177 Installation
Monitor Hotfix KB4594177 Installation

Install hotfix KB4594177 on Secondary Sites

After you install this update KB4594177 on a primary site, pre-existing secondary sites must be manually updated. Read more about secondary site installation in SCCM to get an idea on how to install secondary sites in SCCM.

To update a secondary site in the Configuration Manager console, select Administration > Site Configuration > Sites > Recover Secondary Site, and then select the secondary site. 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.
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.
3 Comments