Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

Tom Brisby

My feedback

  1. 193 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  2. 1,722 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    96 comments  ·  Ideas » Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Tom Brisby supported this idea  · 
  3. 169 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Ideas » Compliance Settings  ·  Flag idea as inappropriate…  ·  Admin →
    Tom Brisby supported this idea  · 
  4. 17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Ideas » Application Management  ·  Flag idea as inappropriate…  ·  Admin →
    Tom Brisby supported this idea  · 
  5. 654 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    30 comments  ·  Ideas » Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
    Tom Brisby commented  · 

    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.

    Tom Brisby supported this idea  · 

Feedback and Knowledge Base