1,382 votesplanned · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, System Center Configuration Manager) responded
Saw a working demo of this recently so updating to planned.
Looks like 1902 has this feature called "Server groups", however it is still in Pre-release. Any idea in what feature SCCM version it will be brought to release status?
on our short term radar.
@Gregor Achmed: This is not "a perfect way" at all. For example a big IT infrastructur can have several thousands of servers, and you might not have the time (or other priorities) to install updates within the 12 months window. There are several reasons why there could be server(s) who only allow a maintenance window for example every 2 years. Available must mean at all times available, so no deadlines whatsoever.
This request is open for more then1 year and 9 months now. I hope it will be available in the new release.
The current option we will use is to let the ADR's run at patch tuesday, for the available SUGs we would NOT enable the Deployment. Then we need to run a powershell script to kickoff after the ADR's have ran, search for the "Available" SUGs (use it in your SUG names), put them on "Availabe" instead of "Required" and after that Enable the deployment.
A tricky solution because if the script for some reason doesn't run, we are behind on patches. I would love to see the Available deployment option in the ADRs!
Phase 1 of these feature is in 1602 production