We went about 5 years before finally having a “reboot everything now” incident from monthly Windows last month.
The use action constraints, specifically “Run only when” to match one of our maintenance windows. Last month that constrain checkbox apparently was unchecked. Management is asking if there are any ways to either stop these actions automatically if the constraint is missing, or force that constraint to be checked before deploying. I know on an individual task/fixlet you can do action constraints but I don’t see that is possible with baselines.
Has anyone had a similar issue and found a way to prevent it from happening again?
There’s no specific way to have a requirement like you’re mentioning that I know of. The closest I can think is the four eyes approval where two people have to approve an action :
When you build baselines, at the bottom of the Components window you can define Action Presets. I use that to predefine constraints, so they are in effect when you take the action unless an operator specifically clears the constraint.
If you’re looking for something more global, you could use Locking. There’s a Maintenance Window Dashboard, either in Bes Support or BigFix Labs, I think, to manage locking/unlocking on a regular schedule.