System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Implement native cluster aware patching within SCCM to support cluster aware updating

Implement native cluster aware patching with SCCM to support cluster aware updating.

509 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    David shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      • Anonymous commented  ·   ·  Flag as inappropriate

        As I can understand, this feature is abandoned.
        It would be useful to:
        1) implement availanility sets with update domains
        2) implement pre- and post-update scripts running from run as acounts (it also possible to involve JEA approach)

      • Ben commented  ·   ·  Flag as inappropriate

        Is this feature dead or what? 2 years on and it's still in pre-release, no word anywhere about that changing, and it still doesn't work.

      • Benoit Machiavello commented  ·   ·  Flag as inappropriate

        Same problem here. First computer in the group can patch. Each other never get updates with the status "waiting for lock".

      • bdam commented  ·   ·  Flag as inappropriate
      • bdam commented  ·   ·  Flag as inappropriate

        Now that we have the 'Run a PowerShell Script' option it seems pretty obvious to use that feature here for the node drain scripts. That should fix the 512 character limit. Additionally, I hope it would make sense to then add a run-as feature to use service accounts for thinks like Exchange and SQL where workloads need to be moved and the local system isn't going to have that kid of access.

      • bdam commented  ·   ·  Flag as inappropriate

        For those looking for documentation:

        I just tried using this for the first time in 1702 and it would appear the script is limited to 512 characters. I have difficulty believing that's going to be enough. I had to condense and cheat just to get a script to run scheduled tasks.

        Which raises another suggestion here; we need to be able to run the scripts as a particular account. The machine account shouldn't have access to move Exchange/SQL resources.

      • Tom Brisby commented  ·   ·  Flag as inappropriate

        The server group functionality is nice, but I've been struggling to find any documentation describing what happens when deployments are applied to collections with this setting enabled. With no custom node drain or resume scripts applied, are the nodes simply rebooted without any sensitivity to the cluster resources? Are there any example node drain/resume scripts available? What I'd eventually like to see is a more true integration of Cluster aware updating and how that process proceeds with SCCM. Right now, SCCM can be used to select specific patches to place in a SUG and then deploy them, but using SCCM to patch clusters is still nebulous and feels..dangerous. Cluster aware updating is much healthier for the clusters, but doesn't have any connection to SUGs in SCCM meaning that WSUS has to be directly managed as well.

      • Brian commented  ·   ·  Flag as inappropriate

        It would be prudent to 1. include basic documentation on use of feature 2. the feature does appear to be functional but has issues in 1606, tech preview for 1609 does not even mention this feature or improvements to it. 3. This feature should be a number one priority as it is a basic requirement for datacenter automation. 4. No new version preview or production should be released without updates to this feature which is currently broken.

      • Anonymous commented  ·   ·  Flag as inappropriate

        I notice there are more features released in 1606, but the maintenance sequence list only populates in one of my environments... Is there a trick or step that I am missing, or is that a known issue?

      • Martin Wüthrich commented  ·   ·  Flag as inappropriate

        Hi djam,
        the feature is shipped within the Current Branch 1602. Will there be some more information on the TechNet Pages?

      • Justen H. commented  ·   ·  Flag as inappropriate

        Take a look at what Infront Consulting has to offer - OPAS; it's a great tool to addon to SCCM. It handles the patching of clusters and other applications or server groups such as web farms or Exchange DAGs - it SO easy to use and is becoming hugely popular.

        A must have IMO:

      • cgsilver commented  ·   ·  Flag as inappropriate

        Hi, I did try this out with a 2 Node cluster. The following happened:
        allowed offline 51% - both rebooted at the same time
        allowed offline 50% - both rebooted at the same time
        allowed offline 49% - none of them rebooted: even though the restart windows indicated, that an automatic reboot will happen, after the grace period, nothing happened. both windows were showing 00s remaining, none of them rebooted.

      • Nicolas Vaneberg commented  ·   ·  Flag as inappropriate

        What would be great, would be to be able to create one collection and all clusterer machines as members of it and that sccm could handle that in once. For the moment we need to create one collection for each cluster. I need to work with maintenance windows, so creating x collections + x maintenance windows is not feasible for me. For the tests I had with TEchnical Preview 3, it's a lot of work to configure and maintain it. One collection with all clusters and same maintenance window should be a very great improve. Else i'll continue with Orchestrator runbooks to handle the clusters patching.

      • René Kierstein commented  ·   ·  Flag as inappropriate

        True, they talked about it at ignite, but the new feature must include better control with the cluster progress update than presented in the session.

      • René Kierstein commented  ·   ·  Flag as inappropriate

        You should consider to include following functionality and error checking:

        What should happen if one server in a sequence fails updating? Should the sequence stop and perform a rollback and report the error.
        (generally, the ability to rollback software updates deployed by SCCM would be nice)
        At least make it possible to configure if the sequence should stop or continue in case of an error.

        Using scenario “Specify the maintenance sequence”
        Each step should have pre and post script options, including error handling (return codes). This is required to be able to control if a cluster resource is successfully moved to another cluster node before continuing the update sequence

        Make sure that the function works with both software deploy and Windows updates.

        Make sure that there are good logs. I can foresee some issue troubleshooting a failed update sequence if logging is missing.

        Automated Support for patching SharePoint Farms (without having to take the entire farm offline)

        Validate cluster services are online pre / post patching

        Improved In-console Monitoring for patching critical servers like cluster > more detailed state messages sent back to server > state messages for critical server patching sent through with a higher priority (like the state messages for SCEP are)

        Ability to configure alerts for cluster patching .

        Ability to configure email enabled alerts for cluster patching failure / success

        Ability to trigger Orchestrator runbooks as pre / post cluster patching actions

        PowerShell cmdlets to configure cluster patching feature in Config Manager

      Feedback and Knowledge Base