A precise control over the device reboot from Configuration policy
A precise control over the device reboot from Configuration policy
What we need:
We need to be able to specify a deadline for automatic PC restart and application of updates. Similar to the setting in Group Policy, the deadline time frame can be between 2 and 14 days. After the deadline has passed, devices restart regardless of active hours. Currently, it is between 15 to 180 minutes.
What we have in Atera through configuration policy:
• Disable auto-restart with logged-on users
• Restart outside of active hours
• Restart after selected time period
o 15 – 180 minutes
• Allow end users to control device restarts
o Prompt users to restart their devices
o Force restart option after a certain number of prompts
o Option to customize the toast message
What we have in MS Windows server Group Policy:
• Turn off auto-restart for updates during active hours
o the PC will not automatically restart after updates during active hours
• Always automatically restart at the scheduled time
o A restart timer will always begin immediately after Windows Update installs important updates, instead of first notifying users on the login screen for at least two days
o The restart timer can be configured to start with any value from 15 - 180 minutes
• Specify deadline before auto-restart for update installation
o 2 – 14 days past the default (7 days) restart date
o Restart can happen inside active hours
• Specify deadlines for automatic updates and restarts
o Updates will be downloaded and installed as soon as they are offered and automatic restarts will be attempted outside of active hours
o Once the deadline has passed, restarts will occur regardless of active hours, and users will not be able to reschedule
o Set a grace period for feature updates and quality updates to guarantee users a minimum time to manage their restarts once updates are installed
o Option to set device to delay restarting until both the deadline and grace period have expired
• Specify Engaged restart transition and notification schedule for updates
o Control the timing before transitioning from Auto restarts scheduled outside of active hours to Engaged restart, which requires the user to schedule
o The transition period can be set between 0 – 30 days from the time restart becomes pending
o Specify the number of days a user can snooze Engaged restart reminder notifications (1 – 3 days)
o Specify the deadline in days before automatically scheduling and executing a pending restart regardless of active hours (2 – 30 days)
• No auto-restart with logged on users for scheduled automatic updates installations
o Only notify the user to restart the computer
