Complex scheduling: Enable patch deployments to servers based on SDLC (Dev / QA / Prod / DR)
Based on Patch Tuesday, allow application / business owners to select appropriate down time for the server as well as a sequenced order (e.g., Development servers during the first week after Patch Tuesday, QA on the second week after Patch Tuesday, Production servers on the third week after Patch Tuesday, et cetera). This allows the business owners to "own their own destiny" and get systems administrators out of the business of coordinating patching maintenance windows. In addition, the ability to insert "change freezes" that force the schedule to increment all downstream targets out by an additional week to compensate for the "change freeze"

10 comments
-
Rodrigo Fronza commented
Any prediction for this to enter a TechPreview?
This is very important for many environments, having this flexibility to manage updates only Windows 10 and yes for Windows Server 2016/2019 and now coming 2022. -
Lee commented
Move Server Groups to production. How many releases is this going to miss and instead stay in pre-release?
-
Anonymous commented
You could start by just adding the same scheduling subroutine for the that is available for when the ADR runs to the deployment schedule. Right now it can only be deployed a set minutes days weeks or months, why can't we just pick a day in the future like every other schedule in SCCM?
-
Chris Champlin commented
They have added the ability to do day "offsets" to just the scheduling for ADRs... But if that same offset function is available to schedules in Collection Maintenance Windows, that would be powerful.
-
Nitin commented
It's really a great idea to have it.
-
Joe Friedel commented
Good idea. I have maintenance windows I have to change monthly which I wouldn't need to if I could set them to be a date relative to Patch Tuesday.
-
Anonymous commented
I completely agree
-
Anonymous commented
all for it. good idea
-
Anonymous commented
+1
-
Anonymous commented
Good idea