Deployment Notifications/Restarts

Context -
There seemed to be some confusion regarding patching / deployments / restarts. Upper management needed an explanation. This document aimed to clear that ambiguity.

posted May 28, 2015, 6:32 PM 

HSV1AMCM12W01 - Remote Desktop Connection Manager v2.7 2015-05-28 17.21.24.png
HSV1AMCM12W01 - Remote Desktop Connection Manager v2.7 2015-05-28 17.23.06.png

The policies above are what is enforced for everyone and are fairly self explanatory.  As you can see there are several notifications regarding a pending deadline leading up to the actual event.  

Scenario 1 - Monthly Updates

Typically for patching there will be a 7 day "opportunity" as I will call it to update your system.  Based on this schedule the user should get notified:

  • Once a day for 6 days.

  • Once every hour in the last 24 hours

  • Once every 15 minutes in the last hour

  • Pending a restart is due

    • 90 minute countdown with a notification window that can be closed

  • After 30 minutes of the 90 minutes has expired

    • 60 minute countdown with a notification window that cannot be closed

Scenario 2 - Past Due Updates

Client installs software that requires patches or client resumes from an unmanaged state.  Compliance scan determines patches are missing. This scan runs weekly and is randomized from client to client.  Past due patches are scheduled for deployment.  Being that these are "past due", patches are deployed immediately.

  • Pending a restart is due

    • 90 minute countdown with a notification window that can be closed

  • After 30 minutes of the 90 minutes has expired

    • 60 minute countdown with a notification window that cannot be closed

Scenario 3 - Updates Test Candidate

Client has been assigned to the updates test group.  Client is not subject to a 7 day grace period in order to provide quick results to gauge a company-wide deployment and its impact.  

  • Pending a restart is due

    • 90 minute countdown with a notification window that can be closed

  • After 30 minutes of the 90 minutes has expired

    • 60 minute countdown with a notification window that cannot be closed

Scenario 4 - Outside Business Hours Installation

Client has elected to not be disturbed with any pending notifications.  Reboots are deferred outside of business hours.

Scenario 5 - Application Installation

This scenario is not typical but it is possible. Testing should identify any of these issues.  Client receives an application deployment which hides all notifications and forces a reboot.  In the event that this does occur the Computer Restart  settings are enforced.

  • Pending a restart is due

    • 90 minute countdown with a notification window that can be closed

  • After 30 minutes of the 90 minutes has expired

    • 60 minute countdown with a notification window that cannot be closed

User Experience for Deployments

2020-05-20_13-03-39.png

User Notification Log Files

2020-05-20_13-04-12.png
Previous
Previous

EndPoint Logs / Info / CMD Line / Def DL

Next
Next

Software Center / Application Catalog Error