Hello!
We use maintenance windows as a way to aggregate changes during the week and apply them once the server’s maintenance window has arrived. This is done by constraining the action on the “In Maintenance Window” property:
The problem with this is that if you want something to apply sooner for a specific machine (a new computer, a test computer, etc) you would then have to produce multiple actions for each piece of content instead of relying on application during maintenance windows.
We wanted an easy way for developers and administrators to put their own systems into maintenance prior to the enforced maintenance window (so they could test changes ahead of production rollout, make changes occur more quickly on certain devices, etc).
To accommodate this we simply added or exists (values whose (it as boolean = true) of settings "MaintenanceWindow_Override" of client)
to the end of the In Maintenance Window property and then produced two fixlets: One that enables the override and one that disables it.
Here are the Fixlets:
Override Fixlets.bes (2.1 KB)
In Maintenance Window with Override Property (4.9 KB)
We push out a policy which disables overrides every night so that a machine doesn’t stay in maintenance forever
Hope this is helpful for someone!
Bill