Improve client auto upgrade options for servers
Enhance site auto upgrade option for servers. Provide the ability to control the schedule for server operating system client upgrade using the auto upgrade feature. Server changes in production fall under change management control. It would be great to be able to specify when the upgrade will take place so that we can align to the change process. So include schedule option for servers and collection selection
Samuel Erskine
shared this idea
4 comments
-
Calum
commented
This request seems a bit dead compared to this one:https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/15032517-allow-the-client-upgrade-to-be-performed-outside-mNot sure if this could be a candidate to merge but I wanted to add my 2p worth here as well. Being able to define when the client will be upgraded more exactly than we can now would be of immense help, particularly when the current method means the client may a) take a long time to be upgraded if the client has fairly restrictive maintenance windows and b) may be upgraded during a maintenance window when the client is already handling software installations, Windows patches etc which disrupts the process. More control over the client upgrade timings would mean we can avoid these issues.
-
Client Autoupgrade honors the maintenance windows. Maintenance windows are designed to give this kind of control for servers. Rather than create a 2nd way to do the same thing (because that's what makes products complex, is many ways to do similar things).... help me understand why you can't solve this with maintenance windows?
-
Admin note: Updated title for clarity
-
Anonymous
commented
I like this. We end up enabling upgrade on clients only. Allow the Scheduled task to get created on them. Then when we are ready to do servers, we shorten the window to 1 day and enable server upgrade. That is as much control as I can get right now and concentrates them into a 24 hour window.
