none
SCCM 1902 and Software Center notification RRS feed

  • Question

  • Hi Guys,

    I managed and deployed monthly Windows 10 and MS Office 2016 Patches and Updates with SCCM 1902 using ADR. 

    But the users are finding that the pop up notifications are being missed and we are hearing complaints that we are providing no warning. I have the notifications dialed down to last for just 5 minutes but even if we increased this time period I think that we would still have a considerable number of people miss it.

    Is there a way to make sure the notifications for Software Center more obvious and persist until a user confirms they have seen that message? I don't necessarily want them to have to install it but I do want to know they had a chance to see the message.

    Here is my setting. But the user get not pop up notification

    The users told me that they get and see one time the following message. If the icon is hidden and not showing, the user cannot be informed about new updates and Patches

     

    BR,

    Nick



    • Edited by mpng2008 Tuesday, August 13, 2019 10:07 AM
    Tuesday, August 13, 2019 6:29 AM

Answers

  • Please read the items that I've linked as they cover new features that you have not enabled that may address your concerns.

    If the user is in meeting , the updates beginning to install and reboot the machine.

    Then you need to adjust your configuration and processes including increasing your reboot notification times. You also need to communicate with users so that they are aware of the process and can account for it themselves by proactively installing updates.

    Ultimately, ConfigMgr is simply doing what you've configured it to. If you need to adjust this, then make changes to your client settings where appropriate. Start by reading the documentation and learning what is configurable and then match that to your requirements that you've previously defined.


    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by mpng2008 Thursday, August 15, 2019 3:01 PM
    Wednesday, August 14, 2019 1:08 PM

All replies

  • Hi,

    Check if you have any GPO blocking the popup and notification.

    As per client settings user will get the notification, once they click they will get the user option to install update now or snooze it.

    Once the deadline is reached user will get the pop up about system restart as per client restart settings.

    Check the below link for more details

    https://arjanpater.nl/2017/12/05/deploy-microsoft-updates-with-sccm-the-user-friendly-way/

    Tuesday, August 13, 2019 7:46 AM
  • Hi,

    Thnaks for your replay. The user get notification but only one time, it should pop up until the user see it and click on the OK button

    Tuesday, August 13, 2019 10:09 AM
  • Starting with 1902, you can configure the use of dialog windows for use as notifications instead of the toasts: https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1902#bkmk_userxp.

    As for continuing to "nag" the user, as of 1906, restarts notifications are shown more frequently: https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1906#more-frequent-countdown-notifications-for-restarts.

    I don't think anything is being done about more frequent nags for newly available software (which includes software updates) though.

    Are you using available or required deployments?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, August 13, 2019 1:44 PM
  • Hi Jason,

    As I wrote, I am deploying Windows Patches and Updates with ADR and using required deployments. The user get only one time a pop up message and nothing more. If the user is in meeting , the updates beginning to install and reboot the machine. That is sub optimal

    Wednesday, August 14, 2019 8:16 AM
  • Just configure to Computer Restart settings in your client settings:

    Specify 30 minutes (in the option 2) to show a dialog box that the user cannot close.

    As said by Jason, you can use dialog windows to the user  instead of a toast notification starting with 1902 version.

    Wednesday, August 14, 2019 11:00 AM
  • Here are my settings:

    by "Default Client Settings"

    And by "Custom Client Device Setting"

    I thing it should be OK, but it does not work

    Wednesday, August 14, 2019 11:28 AM
  • Make sure that only "Custom Client Device Setting" is deployed to the desired collection and there is no conflict.

    On the Client Policy, what is the interval to refresh the SCCM client policies with the site server?

    Wednesday, August 14, 2019 11:49 AM
  • I have deployed ONLY the "Custom Client Device Setting" to my Device collection and the "Default Client Settings" is NOT deployed

    The new version 1906 is not displayed at the time on the "Updates and Servicing", would recommend to download it with Fast-Ring script?

    • Edited by mpng2008 Wednesday, August 14, 2019 12:13 PM
    Wednesday, August 14, 2019 12:11 PM
  • Please read the items that I've linked as they cover new features that you have not enabled that may address your concerns.

    If the user is in meeting , the updates beginning to install and reboot the machine.

    Then you need to adjust your configuration and processes including increasing your reboot notification times. You also need to communicate with users so that they are aware of the process and can account for it themselves by proactively installing updates.

    Ultimately, ConfigMgr is simply doing what you've configured it to. If you need to adjust this, then make changes to your client settings where appropriate. Start by reading the documentation and learning what is configurable and then match that to your requirements that you've previously defined.


    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by mpng2008 Thursday, August 15, 2019 3:01 PM
    Wednesday, August 14, 2019 1:08 PM
  • The fast-ring script does not download anything, it simply enables your site to show the 1906 upgrade since 1906 is still considered in the fast ring.

    If you want the added functionality provided by 1906 and can't wait for it to go slow ring, then yes, run the script.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, August 14, 2019 1:12 PM