Skip to content
How to Fix SCCM ConfigMgr Software Distribution Notification Issues

How to Fix SCCM ConfigMgr Software Distribution Notification Issues

Written By Anoop C Nair
Last Updated July 25, 2024
Posted In SCCM
SHARE

How to Fix SCCM ConfigMgr Software Distribution Notification Issues. Clients may not get “New Program is Available” pop-up system tray notifications in ConfigMgr even though the “Display a Notification Message” option is checked in the Admin Console.

Index
ConfigMgr Software Distribution Notification Issues
CCM_SoftwareDistributionClientConfig/DisplayNewProgramNotification Policy
CCM_ClientAgentConfig/DisplayNewProgramNotification Policy
How to Fix SCCM ConfigMgr Software Distribution Notification Issues – Table 1

ConfigMgr Software Distribution Notification Issues

Two Policy entries control the “New Program notification” for clients, and if either is set to “FALSE”, then the new program pop-up will not show:

  • CCM_SoftwareDistributionClientConfig/DisplayNewProgramNotification
  • CCM_ClientAgentConfig/DisplayNewProgramNotification

The problem is that the Admin Console makes it relatively easy to get the policy into a state where DisplayNewProgramNotification becomes set to false under CCM_ClientAgentConfig even though the notification option is enabled in the UI.

CCM_SoftwareDistributionClientConfig/DisplayNewProgramNotification Policy

Run WBEMTEST query to determine if either of the ClientConfigs is set to FALSE:

Patch My PC
How to Fix SCCM ConfigMgr Software Distribution Notification Issues - Fig.1
How to Fix SCCM ConfigMgr Software Distribution Notification Issues – Fig.1

Connect to “root\ccm\policy\machine.”

How to Fix SCCM ConfigMgr Software Distribution Notification Issues - Fig.2
How to Fix SCCM ConfigMgr Software Distribution Notification Issues – Fig.2

Click on Query, paste the following query in the “query” window, and click Apply.

select * from CCM_ClientAgentConfig

How to Fix SCCM ConfigMgr Software Distribution Notification Issues - Fig.3
How to Fix SCCM ConfigMgr Software Distribution Notification Issues – Fig.3

Double-click the one row that is returned (note if there is more than one),

How to Fix SCCM ConfigMgr Software Distribution Notification Issues - Fig.4
How to Fix SCCM ConfigMgr Software Distribution Notification Issues – Fig.4

Click the Show MOF tab in the Object editor window.

How to Fix SCCM ConfigMgr Software Distribution Notification Issues - Fig.5
How to Fix SCCM ConfigMgr Software Distribution Notification Issues – Fig.5

Review the setting for DisplayNewProgramNotification. This example below is set to FALSE, so there won’t be any notification for New Programs.

How to Fix SCCM ConfigMgr Software Distribution Notification Issues - Fig.6
How to Fix SCCM ConfigMgr Software Distribution Notification Issues – Fig.6

CCM_ClientAgentConfig/DisplayNewProgramNotification Policy

Run WBEMTEST query to determine if either ClientConfigs is set to FALSE and Connect to “root\ccm\policy\machine.”

Click on Query, paste the following query in the “query” window, and click Apply.

Select * from CCM_SoftwareDistributionClientConfig

How to Fix SCCM ConfigMgr Software Distribution Notification Issues - Fig.7
How to Fix SCCM ConfigMgr Software Distribution Notification Issues – Fig.7

Double-click the one row that is returned (note if there is more than one) in the Query Result window

How to Fix SCCM ConfigMgr Software Distribution Notification Issues - Fig.8
How to Fix SCCM ConfigMgr Software Distribution Notification Issues – Fig.8

On the Object editor window, click the Show MOF tab

How to Fix SCCM ConfigMgr Software Distribution Notification Issues - Fig.9
How to Fix SCCM ConfigMgr Software Distribution Notification Issues – Fig.9

Review the setting for “DisplayNewProgramNotification.” This example below is set to FALSE, so there won’t be any notification for New Programs.

How to Fix SCCM ConfigMgr Software Distribution Notification Issues - Fig.10
How to Fix SCCM ConfigMgr Software Distribution Notification Issues – Fig.10

If either of these have DisplayNewProgramNotification set to FALSE, then as a workaround, you can do the following:

After the notifications are re-enabled in “Advertised Programs Client Agent Properties,” change “Computer Client Agent” as well, such as changing the org name and forcing the ClientAgentConfig policy to update.

We are on WhatsApp. To get the latest step-by-step guides and news updates, Join our Channel. Click here –HTMD WhatsApp.

Author

Anoop C Nair has been Microsoft MVP from 2015 onwards for 10 consecutive years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is also a Blogger, Speaker, and leader of the Local User Group Community. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc..

Written by

Anoop C Nair is Workplace Technology solution architect with 25+ years of experience in global enterprise organizations such as JP Morgan, Capgemini, etc. Microsoft Certified Trainer. Microsoft MVP from 2015 onwards for consecutive 11+ years! He also conducts Intune and modern workplace tech training for enterprise organizations. He is Blogger, Speaker, and Founder of HTMD Community and HTMD Conference. His main focus is on Device Management technologies like Intune, Windows, Cloud PC. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security.

Discussion · 6 comments

  1. Amazing STUFF Anoop !!!…..this shows how powerful and useful WMI can be when it comes to finding valuable information during troubleshooting activity.

  2. Hi Anoop,
    Very great post.
    I encountered this problem today and I could be still searching without your solution.
    Tks

  3. Hi Anoop, I’m approaching an issue very similar to this one in SCCM Current Branch regarding Application deployment. I want the notifications for installation progress and completion status to show balloon tips and system tray notifications but I do not want the clients to receive ‘New Software is available’ notifications. Do you know of a way this can be achieved?

  4. Hi Anoop,
    One of my client is not getting windows updates from SCCM. Could you please assist on this. Below is the WUAHandler.log:

    Search Criteria is (DeploymentAction= AND Type=’Software’) OR (DeploymentAction= AND Type=’Driver’) WUAHandler 12/14/2021 11:45:57 AM 130492 (0x1FDBC)
    Async searching of updates using WUAgent started. WUAHandler 12/14/2021 11:45:57 AM 130492 (0x1FDBC)
    Async searching completed. WUAHandler 12/14/2021 11:45:57 AM 71568 (0x11790)
    OnSearchComplete – Failed to end search job. Error = 0x80244022. WUAHandler 12/14/2021 11:45:57 AM 130492 (0x1FDBC)
    Scan failed with error = 0x80244022. WUAHandler 12/14/2021 11:45:57 AM 130492 (0x1FDBC)
    Its a WSUS Update Source type ({60FFC0D7-C5D6-43D5-B4D3-58B2E834F635}), adding it. WUAHandler 12/14/2021 11:45:57 AM 201168 (0x311D0)
    Failed to check enrollment url, 0x00000001: WUAHandler 12/14/2021 11:45:57 AM 26552 (0x67B8)
    SourceManager::GetIsWUfBEnabled – There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr WUAHandler 12/14/2021 11:45:57 AM 26552 (0x67B8)
    Existing WUA Managed server was already set (http://SCCMWSUS.server.com:8530), skipping Group Policy registration. WUAHandler 12/14/2021 11:45:57 AM 201168 (0x311D0)
    Added Update Source ({60FFC0D7-C5D6-43D5-B4D3-58B2E834F635}) of content type: 2 WUAHandler 12/14/2021 11:45:57 AM 201168 (0x311D0)
    CWUAHandler – Scan(), old SupersedenceMode=0, new SupersedenceMode=0. Need update and save to SourceManager. WUAHandler 12/14/2021 11:45:57 AM 201168 (0x311D0)
    Modified Update Source ({60FFC0D7-C5D6-43D5-B4D3-58B2E834F635}) to new SupersedenceMode: 0 WUAHandler 12/14/2021 11:45:57 AM 201168 (0x311D0)
    Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 12/14/2021 11:45:57 AM 201168 (0x311D0)
    Search Criteria is ((DeploymentAction=* AND Type=’Software’ AND CategoryIDs contains ‘8C3FCC84-7410-4A95-8B89-A166A0190486’)) WUAHandler 12/14/2021 11:45:57 AM 201168 (0x311D0)
    Async searching of updates using WUAgent started. WUAHandler 12/14/2021 11:45:57 AM 201168 (0x311D0)
    Async searching completed. WUAHandler 12/14/2021 11:45:57 AM 65628 (0x1005C)
    OnSearchComplete – Failed to end search job. Error = 0x80244022. WUAHandler 12/14/2021 11:45:57 AM 201168 (0x311D0)
    Scan failed with error = 0x80244022. WUAHandler 12/14/2021 11:45:57 AM 201168 (0x311D0)
    Its a WSUS Update Source type ({60FFC0D7-C5D6-43D5-B4D3-58B2E834F635}), adding it. WUAHandler 12/14/2021 11:45:57 AM 79984 (0x13870)
    Failed to check enrollment url, 0x00000001: WUAHandler 12/14/2021 11:45:57 AM 88736 (0x15AA0)
    SourceManager::GetIsWUfBEnabled – There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr WUAHandler 12/14/2021 11:45:57 AM 88736 (0x15AA0)
    Existing WUA Managed server was already set (http://SCCMWSUS.server.com:8530), skipping Group Policy registration. WUAHandler 12/14/2021 11:45:58 AM 79984 (0x13870)
    Added Update Source ({60FFC0D7-C5D6-43D5-B4D3-58B2E834F635}) of content type: 2 WUAHandler 12/14/2021 11:45:58 AM 79984 (0x13870)
    CWUAHandler – Scan(), old SupersedenceMode=0, new SupersedenceMode=0. Need update and save to SourceManager. WUAHandler 12/14/2021 11:45:58 AM 79984 (0x13870)
    Modified Update Source ({60FFC0D7-C5D6-43D5-B4D3-58B2E834F635}) to new SupersedenceMode: 0 WUAHandler 12/14/2021 11:45:58 AM 79984 (0x13870)
    Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 12/14/2021 11:45:58 AM 79984 (0x13870)
    Search Criteria is (DeploymentAction= AND Type=’Software’) OR (DeploymentAction= AND Type=’Driver’) WUAHandler 12/14/2021 11:45:58 AM 79984 (0x13870)
    Async searching of updates using WUAgent started. WUAHandler 12/14/2021 11:45:58 AM 79984 (0x13870)
    Async searching completed. WUAHandler 12/14/2021 11:45:58 AM 58864 (0xE5F0)
    OnSearchComplete – Failed to end search job. Error = 0x80244022. WUAHandler 12/14/2021 11:45:58 AM 79984 (0x13870)
    Scan failed with error = 0x80244022. WUAHandler 12/14/2021 11:45:58 AM 79984 (0x13870)

Join the discussion

Your email address will not be published. Required fields are marked *

Related guides

Intune

Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws

Key Takeaways Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws! In the July 2026 Patch, Microsoft introduced new features designed to improve the overall Windows experience. The update adds enhancements to Windows Update for more flexible update management and introduces Point-in-Time Restore, providing an additional recovery option for […]

AC Anoop C Nair 9 min read
Intune

2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws

Key Takeaways 2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws! The June 2026 Windows 11 Patch Tuesday update brings several improvements to File Explorer. It adds support for additional archive formats, including UU, CPIO, XAR, and NuGet Packages (NUPKG). The update also preserves View and Sort preferences in […]

AC Anoop C Nair 10 min read
Intune

2026 May KB5089549 KB5087420 Windows 11 Patch | 0 Zero Day Vulnerabilities and 120 Flaws

Key Takeaways The Windows 11 May 2026 Patch KB5089549 KB5087420 Update brings important security fixes, performance improvements, and reliability enhancements across the operating system. The update introduces new features such as Xbox Mode for gaming, File Explorer improvements, enhanced input and sharing experiences, better taskbar and Windows Hello reliability, and additional enterprise management capabilities for […]

AC Anoop C Nair 8 min read
SCCM

ConfigMgr 2603 Introduces New Early Update Enrollment Process

Key Takeaways In this post we are discussing the ConfigMgr 2603 Introduces New Early Update Enrollment Process. Microsoft has officially released Configuration Manager version 2603 to the Early Update Ring, giving organizations an opportunity to test upcoming improvements before the global production rollout. The release is targeted at enterprises running ConfigMgr version 2409 or later […]

AC Anoop C Nair 3 min read