23:23:00
Maintenance windows is nothing but a time frame set by administrative users to carry out the operational activities related to configuration Manager on members of a device collection. The reason for setting up maintenance window is to avoid the delay in productivity of the organization due to configuration manager operational task such as installing updates, application, packages, rebooting machines etc.
Maintenance windows are configured for a collection with a start and end date with accurate timing. It is also possible to set a recurrence pattern. Each maintenance window must have duration of less than 24 hours. By default, Machine reboot caused by a deployment are not allowed outside of a maintenance window, but you can override the default in the settings for each deployment. You can also set the deployment to run in maintenance window but the download action to run outside of the maintenance window.
The following Configuration Manager operations support maintenance windows:
- Software deployments
- Software update deployments
- Compliance settings deployment and evaluation
- Operating system deployments
- Task sequence deployments
If we set two maintenance windows and if both the time overlaps, then configuration Manager will assume it as single window encompassing the time period covered by both maintenance windows.
How to set up maintenance window?
Create a collection, for the group of machine you are intended to create specific maintenance window time frame.
Once collection Created, right click the collection > Properties
In maintenance window tab, click the yellow label as highlighted in below figure.
Mention the name, date, time frame and apply this schedule as per your needs like Deployment, Task sequence, software updates etc.
Hope this Helps!! Thanks for reading. If you have any questions, please post it below.
Posts
