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.
The “New Program notification” for clients is controlled by two Policy entries, and if either is set “FALSE”then the new program pop-up will not show:
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:
a.2. Connect to “root\ccm\policy\machine”
a.3. Click on “Query” and paste the following query in the “query” windows and click on “Apply”
select * from CCM_ClientAgentConfig
a.4. Double click the one row that is returned (note if there is more than one),
a.5. On the Object editor window Click “Show MOF” tab.
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”
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
b.3. Double click the one row that is returned (note if there is more than one) in the “Query Result” window
b.4. On the Object editor window Click “Show MOF” tab
b.5. Review the setting for “DisplayNewProgramNotification”. In this example below it’s set to FALSE so there won’t be any notification for “New Programs”.
If either of these has DisplayNewProgramNotification set to FALSE, then as a work-around 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.