Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

MVP - DCR wanted for server groups

My customer has +_ 600 maintenance windows using the server grouping feature .

Feature Request Nr1 : They use the node drain / node resume feature with PowerShell. They are still modifying and changing the script almost every week . That script is used for those 600 collections :

a) a central repository/place to enter the script details and be able to reuse that for each server group collection like for power management custom templates .
b) If they make a change in the “central” PowerShell repository , it keeps history ( Like application revisions ) and replaces that automatically in all Server Groups Collections where applied.

Feature Request Nr 2 : More options per server group

I would like to see a fourth option ( in the server group options) that is a combination of option b) and c) , meaning that you define a list but that from that list a number of machines in that list sequence can be patched at the same time. The reason is that you may have 20 servers in a maintenance window of 3h , then you don’t want to wait until the first one is patched , then the second one and so on . It would take way to much time to complete. If you have a predefined sequence list and you can from that list patch for example 5 servers at a time , that would help saving you time. Best one would be that you can create blocks in the sequenced list that can patch at the same time within the same maintenance window.

Feature Request Nr 3 : Powershell remoting (credential Manager)

Support for a credential manager within Configmgr where you can store certain credentials that the script (powershell remoting) need to run with ? to support a kind of “run as” scenario .

Feature Request nr 4 : Decent RBAC

Can you please create an RBAC role that only allows you to edit the maintenance windows or server group settings ? Reason is that most of the time , the business or release managers are defining their maint windows and not the server teams.

1 vote
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
kenny buntinx shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

5 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • René Kierstein commented  ·   ·  Flag as inappropriate

    Is the original idea with server group dead or do you have an Update for to share with us?

    Managing an Enterprise, we nede a nice Way to Update clusters

  • René Kierstein commented  ·   ·  Flag as inappropriate

    - Please also add the possibility to use a powershell function library

    - Excuete script at local directory at the server being updated

    - cmdlets, so a server group can be configured remotely. We will use a CMDB system to store server group info / configuration and will use this info to configure the group in SCCM

  • kenny buntinx commented  ·   ·  Flag as inappropriate

    Djam - I would indeed like to have a script repository where I can have versioning and pick a script out of that repository from the server group node ( drain / resume )

  • WRT:
    Support for a credential manager within Configmgr where you can store certain credentials that the script (powershell remoting) need to run with ? to support a kind of “run as” scenario .

    We do support this today in some capacity. You can use New-PSDrive with -Credential to connect to any ConfigMgr site with alternate credentials.

Feedback and Knowledge Base