Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

Ideas

What features would you like to see?

All of the feedback that you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building System Center Configuration Manager, though we can’t promise to reply to all posts.

Please do not use UserVoice to report product bugs or for assisted support.
If you believe you have found a product bug, please send us a bug report through the Configuration Manager Console (1806 and newer). To do this, press the ? button in the top right corner and choose “Send a Frown”. For more details, see https://docs.microsoft.com/en-us/sccm/core/understand/find-help.

If you require assisted support, please see https://aka.ms/cmcbsupport for more details.

Standard Disclaimer – our lawyers made us put this here ;-)
We have partnered with UserVoice, a third-party service, so you can give us feedback. Please note that the System Center Configuration Manager feedback site is moderated and is a voluntary participation-based project. Please send only feature suggestions and ideas to improve Microsoft Configuration Manager. Do not send any novel or patentable ideas, copyrighted materials, samples or demos. Your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms.

How can we improve Configuration Manager?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Improve and speed up adding or removal processes of direct members to collections, optimize handling in backend

    We need a quick way to quickly populate or empty collections. Targets should be imported as rules without triggering other processes in the background (eval/re-built). The same also applies to removal rules.

    Please implement something like an cmdlet “Add-CollectionMemberRules” / “Remove-CollectionMemberRules” with fast adding rules method, without delays, without rebuilding the complete collection sets in the background. The cmdlet should support especially adding rules like "DirectMembers".

    Note:
    This will help to control and steer application (ramp-up / ramp-down) rollouts, depending on device target lists, created by internal IT or delivered by business partner. The lists could based on different information…

    64 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    • PowerShell cmdlets for editing task sequences

      Being able to edit task sequences with PowerShell would make managing task sequences much easier. Some possible new cmdlets could include:

      Add-CMTaskSequenceStep
      Get-CMTaskSequenceStep
      Remove-CMTaskSequenceStep
      Set-CMTaskSequenceStep

      Add-CMTaskSequenceGroup
      Get-CMTaskSequenceGroup
      Remove-CMTaskSequenceGroup
      Set-CMTaskSequenceGroup

      58 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        10 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
      • Add missing InstallationBehaviourType parameter to new DeploymentType cmdlets in SCCM Powershell Cmdlets.

        This goes for all new Add/Set-CM*DeploymentType but for my example, I'll refer to Add-CMScriptDeployment.

        An example below is my generic Script Deployment Type.

        Add-CMScriptDeploymentType `
        -ApplicationName "$PublicName" `
        -DeploymentTypeName "$AppName Client" `
        -ContentLocation "$AppLocation" `
        -InstallCommand "$InstallStr" `
        -UninstallCommand "msiexec /x $MSICode /qn" `
        -MaximumRuntimeMins 720 `
        -LogonRequirementType WhereOrNotUserLoggedOn `
        -UserInteractionMode Hidden `
        -ProductCode
        -ScriptLanguage PowerShell `
        -ScriptText $scriptDetect

        When this is run, the DT is created with the Installation Behaviour set to the default value of "Install for system if resource is device; otherwise install for user"

        The previous version of this cmdlet - Add-CMDeploymentType had the parameter available…

        27 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          5 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
        • PowerShell cmdlets need to be cleaned up

          I use a LOT of PowerShell ... and the PowerShell modules in SCCM are ... well... bad.

          Issue 1: I should not have to set my running location to a site to run a cmdlet. No one uses a set-location to make sure they are in the AD domain root before running a get-ADUser (unless they have a multi-domain environment and need to call something specifically), yet SCCM requires this to be true. It makes scripting needlessly complex.

          Issue 2: there are a pointlessly large number of cmdlets. Do I really need a Get-CMDeviceCollection and a separate Get-CMUserCollection? Why can't…

          25 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            7 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
          • PowerShell Redistribute Content

            Create a PowerShell cmdlet that will redistribute (not refresh) content on a specific distribution point

            12 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
            • invoke-cmclientnotification improvements

              In 1602 support in the Admin Console GUI was added for additional client notification triggers.

              https://blogs.technet.microsoft.com/manageabilityguys/2016/03/29/whats-new-with-configmgrs-client-notification-feature/

              However there is still a gap in the functionality for this cmdlet. Currently as of 1706 you are still only able to invoke user and machine policy per the documentation:

              https://docs.microsoft.com/en-us/powershell/sccm/configurationmanager/vlatest/invoke-cmclientnotification

              11 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                2 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
              • Updates and servicing - Powershell CmdLet

                Working for a company with several Configmgr hierarchies, it would be great with a PowerShell cmdlet to initiate and control the updates and servicing.

                11 votes
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  3 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                • SCCM 2012 R2 - PowerShell Commandlet needed to remove Updates from Group (Add-CMSoftwareUpdateToGroup exists)

                  Hi all, my customer is using the PowerShell on a really high level to automate nearly all his ConfigMgr Patchmanagement Tasks. They are using Add-CMSoftwareUpdateToGroup but they're missing the matching Remove Commandlet.

                  10 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                  • Set-CM<Type>DeploymentType fails with Invalid Property when updating Content Location

                    Since I updated to 1706, any of the Set-CM<Type>DeploymentType cmdlets fail with an error when I try to update the content path/location to another location. Based on the error message, it seems the cmdlets need to have extra parameters added to handle the separate Install and Uninstall content paths/locations. Perhaps you could add -UninstallContentLocation and a switch for -UninstallContentSameAsInstallContent.

                    Set-CMScriptDeploymentType : Invalid property: object Application(ScopeId_8C35D19A-F107-4878-83CC-9E26B213220D:Application_a463d8c5-c106-43ae-993b-f5bcb2f4ae4c:15) property
                    DeploymentTypes.DeploymentTypes[0].Installer.Installer.UninstallContent: Uninstall Content not found in Contents collection
                    At line:54 char:3
                    + Set-CMScriptDeploymentType -ApplicationName $cmApplicationNa ...
                    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                    + CategoryInfo : NotSpecified: (:) [Set-CMScriptDeploymentType], InvalidPropertyException
                    + FullyQualifiedErrorId : Microsoft.ConfigurationManagement.ApplicationManagement.InvalidPropertyException,Microsoft.ConfigurationManagement.Cmdlets.AppMan.Commands.SetScriptDeploymentTypeCommand

                    9 votes
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                      7 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                    • Add ability to Create CM Computer with SMBIOS GUID

                      Add Ability to create a new Computer in ConfigMgr with New-CMComputer and use the SMBIOS GUID instead of MAC address.

                      6 votes
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                      • Allow parameters to "Run Script"

                        When using the "Run Script" against a collection allow the script to accept parameters.

                        5 votes
                        Vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                          3 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                        • Set-CMClientSetting hardware inventory

                          Set-CMClientSetting for hardware inventory, add option to add/remove classes as well as enabled/disable attributes to be collected within a class

                          5 votes
                          Vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)
                            You have left! (?) (thinking…)
                            0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                          • SUP Sync Status

                            Add a Get-SupSyncStatus cmdlet as it does not exist today.

                            the only way to achieve this is via WMI
                            gwmi -Class SMS_SupSyncStatus -Namespace "root\sms\site_$SiteCode" | select LastSyncErrorCode, LastSyncState

                            4 votes
                            Vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)
                              You have left! (?) (thinking…)
                              0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                            • Add the new "If any update in this deployment requires a system restart, run updates deployment evaluation cycle"

                              Add the new "If any update in this deployment requires a system restart, run updates deployment evaluation cycle" option into the Start-CMSoftwareUpdateDeployment cmdlet.

                              4 votes
                              Vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)
                                You have left! (?) (thinking…)
                                1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                              • New-CMPackageDeployment missing parameter to specify deployment expiration time.

                                We currently use the cmdlet Start-CMPackageDeployment to create deployments to our patching collection and schedule reboots. We use the parameter DeploymentExpireDateTime to set the expiration for the deployment. We are now getting a message that start-cmpackagedeployment is being deprecated in favor of New-CMPackageDeployment, but the new command doesn't appear to have a parameter to set the deployment expiration time. Oddly, it does have a parameter "-UseUtcForExpireSchedule", so possibly it's just an omission?

                                4 votes
                                Vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)
                                  You have left! (?) (thinking…)
                                  4 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                • Add a "Description" Parameter to the Get/Set/Add CMDistributionPoint cmdlets

                                  I'd like to see a "Description" parameter added to the Get/Set/Add CMDistributionPoint cmdlets so descriptions can be programatically added w/o having to try this through separate WMI cmdlets.

                                  4 votes
                                  Vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)
                                    You have left! (?) (thinking…)
                                    0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Add wildcard support to Remove-CMMaintenanceWindow

                                    I use a custom New-CMMaintenanceWindow to create a series of maintenance windows based off of which day Patch Tuesday falls on, and at year end when I create new MWs, I would like to use Remove-CMMaintenanceWindow to delete all MWs under a specified collection. Could you all please add supports for wildcards so it can delete all MWs?

                                    4 votes
                                    Vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)
                                      You have left! (?) (thinking…)
                                      1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                    • New-CMSoftwareUpdateAutoDeploymentRule 5.0.8373.1182 (1604)

                                      Since release Cmdlet Library Update 1604 it is finally possible to manage ADR and multiple deployments via Powershell *bigsuccess*

                                      unfortunately my previous powershell script for creating ADR's is not working anymore. Parameters for the Software Updates property filters are not getting applied anymore :( e.g Required is not getting applied
                                      'WARNING: BUG: Unrecognized filter type: NumMissing'

                                      ADR will be created but no property Filters getting applied

                                      Kind Regards

                                      3 votes
                                      Vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        Signed in as (Sign out)
                                        You have left! (?) (thinking…)
                                        0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Save-CMSoftwareUpdate cmdlet crashes PowerShell console

                                        Sometimes, when the cmdlet comes across certain cumulative Office updates, it crashes the whole PowerShell console, which makes it very inconvenient, when this cmdlet is used in scope of a scheduled task. The thing is that in such case, the script just terminates like nothing happened, which requires some advanced wrappers to be built around to alert when such issues occur.

                                        Here's the event that gets logged in the Application log:
                                        Log Name: Application
                                        Source: Application Error
                                        Date: 11/14/2017 7:06:37 PM
                                        Event ID: 1000
                                        Task Category: (100)
                                        Level: Error
                                        Keywords: Classic
                                        User: N/A
                                        Computer: --- cut out ---
                                        Description:
                                        Faulting…

                                        3 votes
                                        Vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          Signed in as (Sign out)
                                          You have left! (?) (thinking…)
                                          5 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                        • Bug in -Location parameter for Save-CMSoftwareUpdate

                                          The -Location parameter for Save-CMSoftwareUpdate doesn't work. It always returns an InvalidArgumentException with the following message:

                                          WARNING: File path '<file path>' does not appear to be a valid local or UNC path. Must be in the format of C:\myfile.ext or \\myserver\share\myfile.ext

                                          Tried using local and UNC paths both in elevated and non-elevated PowerShell, both 32 and 64 bit instances.

                                          3 votes
                                          Vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            Signed in as (Sign out)
                                            You have left! (?) (thinking…)
                                            3 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                          ← Previous 1 3
                                          • Don't see your idea?

                                          Feedback and Knowledge Base