How to Fix SCCM ConfigMgr Software Distribution Notification Issues

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.

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

Latest Post – SCCM CMPivot Query Patches Installed In Last 90 Days | ConfigMgr HTMD Blog (anoopcnair.com)

How to Fix SCCM ConfigMgr Software Distribution Notification Issues

a. CCM_SoftwareDistributionClientConfig/DisplayNewProgramNotification

Patch My PC

b. CCM_ClientAgentConfig/DisplayNewProgramNotification

The problem is that through the Admin Console, it is 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.

Steps to check “CCM_SoftwareDistributionClientConfig/DisplayNewProgramNotification” policy

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

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

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

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

a.3. Click on “Query” and paste the following query in the “query” windows and click on “Apply.”

select * from CCM_ClientAgentConfig

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

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

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

a.5. On the Object editor window, click the “Show MOF” tab.

image

a.6. Review the setting for DisplayNewProgramNotification. In this example below, it’s set to FALSE, so there won’t be any notification for “New Programs.”

image

Steps to Check “CCM_ClientAgentConfig/DisplayNewProgramNotification” policy

b.1. Follow the steps “a.1” & “a.2.”

b.2. Click on “Query” and paste the following query in the “query” windows and click on “Apply.”

select * from CCM_SoftwareDistributionClientConfig

image

b.3. Double click the one row that is returned (note if there is more than one) in the “Query Result” window

image

b.4. On the Object editor window, click the “Show MOF” tab

image

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

image

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,” make a change in “Computer Client Agent” as well, such as changing the org name. This then forces the ClientAgentConfig policy to update.

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 a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…

6 thoughts on “How to Fix SCCM ConfigMgr Software Distribution Notification Issues”

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

    Reply
  2. 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?

    Reply
  3. 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)

    Reply

Leave a Comment

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