PENDING How to setup for devices that are powered off during their Maintenance Window

[PeterFranken]

I manage about 4000 devices over 120+ locations. Some locations have (part of) their workstations setup to patch every 2nd Sun or so (example).
Some operators have developed the habit of powering off devices in weekend.
I have developed a way to identify these cases, but that is partial handwork.

Do you think it is possible to have trick in SCCM to have these devices do a 'catch-up'? Without having to identify them every month/week and putting them in a special 'monday morning' collection. And also without triggering immediate monday morning patching on devices that are kept powered on properly?
Similar to the scheduled tasks setting 'run as soon as possible after missed'.

If I give these 'weekend' devices a 2nd MW on every monday morning, then it will also happen that devices would patch when a new deployment deadline is reached. (I deploy with a 2-month delay each month. Starting on the 1st)
Some devices are kept powered on properly. These should just be allowed to patch on those days that they are scheduled for. Like 1st Sun, 2nd Sun, 3rd Sun, etc

I just wat to do that catch-up thing for the misbehaving ones. Preferably automated.

 

[Garth]

I manage about 4000 devices over 120+ locations. Some locations have (part of) their workstations setup to patch every 2nd Sun or so (example).
Some operators have developed the habit of powering off devices in weekend.
I have developed a way to identify these cases, but that is partial handwork.

Do you think it is possible to have trick in SCCM to have these devices do a 'catch-up'? Without having to identify them every month/week and putting them in a special 'monday morning' collection. And also without triggering immediate monday morning patching on devices that are kept powered on properly?
Similar to the scheduled tasks setting 'run as soon as possible after missed'.

If I give these 'weekend' devices a 2nd MW on every monday morning, then it will also happen that devices would patch when a new deployment deadline is reached. (I deploy with a 2-month delay each month. Starting on the 1st)
Some devices are kept powered on properly. These should just be allowed to patch on those days that they are scheduled for. Like 1st Sun, 2nd Sun, 3rd Sun, etc

I just wat to do that catch-up thing for the misbehaving ones. Preferably automated.

This is exactly why it is not recommended to have mw on nonservers. You will be always playing wackamole.

Look I would give them 5 days to install the su then force them to be installed. If the operator can find any time during those five days... Too bad. Now you have to wait and reboot. It is very hard for anyone to say but.... I could fine the time during those five days...

 

[PeterFranken]

Yes indeed. It is tough. You would think that finding 10-15 min for a reboot would not be asking too much. But they disagree.
Not for the majority, they just deal with it. Especially in the sites where we have Odd/Even workstations side by side in controlrooms and they can work from either.
But we also have smaller locations. Working 24/7, as they claim. (And still power off when they are down ???)

For now I'm trying to get them to keep devices powered on at all times, but they don't understand. Language barriers etc.

So any trick that could help me towards this 'catch-up' method withoud having to think 'manual' each month would be welcome.

 

[PeterFranken]

To automate catch-up patching for powered-off devices during their maintenance window in SCCM without affecting regularly powered-on devices, consider configuring a second maintenance window (MW) for these devices on Monday mornings. Set up a query-based collection to include devices that missed their primary patching schedule due to being powered off. Use the "Run as soon as possible after a missed deployment" option to ensure that any devices that were powered off during the weekend receive their updates during this secondary window.

Additionally, ensure that your patch deployment settings allow devices in this collection to catch up without overlapping with the primary devices' patching schedule. This approach minimizes manual intervention while allowing misbehaving devices to receive necessary updates automatically.

Is that a thing indeed ? : Use the "Run as soon as possible after a missed deployment" option
I'll have to look into that.
Or better, can you show me?

Thank you