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. Add the option to set timeouts on more task sequence steps

    We recently added a task sequence step which involves querying a Dell web API for warranty information to write to WMI during OSD. We use a Run PowerShell script step for that. Unfortunately the Dell API is not always responsive which can lead to the TS hanging up on that step. I'm going to create a program for it for now so that it has a timeout, but it would be great if the Run PowerShell Script TS step had the option to check a box and specify a timeout period like some other steps have.

    2 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  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →

      Updating status to started – we’ve made some recent improvements to the Run PowerShell Script step, some of these are in the 1811 Technical Preview. The changes for setting a timeout will be in a future Tech Preview, we’ll update which release has these changes.

      For more info:
      Doc: https://docs.microsoft.com/sccm/core/get-started/capabilities-in-technical-preview-1811
      Blog: https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Add-PowerShell-script-content-directly-in-the-TS-Editor-using/ba-p/294264
      Try it out and let us know your thoughts, all feedback welcome, thanks.

    • Distribute Task Sequence content to cloud distribution point

      In TP1802, new feature allow Windows 10 in-place upgrade task sequence via cloud management gateway, which is very good feature, so please allow distribute Task Sequence content to cloud distribution point. In this moment, clould distribution point is not in the list when try to distribute Task sequence contents.

      1 vote
      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  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →

        Thank you for the feedback. Updating status to Started, I’ll mark as complete when 1810 is completed.

        With the changes we made to allow the Windows 10 in-place upgrade task sequence work with CMG. We also updated the task sequence distribution to no longer filter for Cloud DPs

        This change was made in 1806 release. If you’re on 1806, please try it out and let us know if this addresses you ask.

      • Update ZTIGather.wsf for new Win32_SystemEnclosure values

        Line 419, add values 30, 31, 32:
        Case "8", "9", "10", "11", "12", "14", "18", "21", "30", "31", "32"

        http://thinkdeploy.blogspot.com/2017/04/new-enclosure-types-for-convertible.html

        1 vote
        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  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
        • Folder Redirection Improvements to Permit OneDrive

          Currently the folder redirection feature in SCCM doesn't take an environmental variable as a good path; it requires \\SERVER\SHARE.

          With OneDrive being common place in Office 365, please allow us to enter a command such as:

          %userprofile%\<SyncFolder>

          where Sync folder is the name of your organization's onedrive folder.

          as documented by the Office team.

          https://support.office.com/en-us/article/redirect-known-folders-to-onedrive-for-business-e1b3963c-7c6c-4694-9f2f-fb8005d9ef12

          So that we can use SCCM to manage this.

          Thanks! :)

          1 vote
          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  ·  Compliance Settings  ·  Flag idea as inappropriate…  ·  Admin →
          • Add simple way to exclude an OU from discovery when discovering entire domain.

            Discovery set to entire domain. Add a way to exclude a few OU's from discovery.

            1 vote
            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  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →

              Thanks for the feedback, your request was addressed in our 1806 release. I’ll close this item at the end of current release.

              For details, check https://docs.microsoft.com/en-us/sccm/core/servers/deploy/configure/configure-discovery-methods

              Search for ‘select subcontainers to exclude from this recursive search’

              If you haven’t moved to 1806 yet or don’t have plans for the near future, you can check out this functionality in any of our Technical Previews after 1804 https://docs.microsoft.com/en-us/sccm/core/get-started/capabilities-in-technical-preview-1804

            • Add-CMScriptDeploymentType -AddDetectionClause "OR" functionality

              It would be helpful to have the ability to select OR as a Connector Value (which only has 2 states AND, OR) for the AddDetectionClause of Add-CMScriptDeploymentType
              The best example of this is when trying to create a ConfigMgr Client Update application. The client has a different GUID depending on whether it is x86 or x64.

              Why am I making a separate application deployment for the client upgrade as opposed to the built in one? The built in one will not use the files local to itself and pull the entire content accross the WAN again. So building an application…

              1 vote
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                started  ·  1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
              • CM Messaging SDK Documentation shouldn't be a .chm help file AND...

                The docs that exist for the CM Messaging (note, the messaging SDK is not a part of the larger CM SDK docs here https://msdn.microsoft.com/en-us/library/hh442686(v=cmsdk.16).aspx) is currently a .chm Help file, which is lovably nostalgic.

                However it doesn't do justice to the power of the SDK. For instance, Discovery and hardware inventory are barely covered in the SDK docs. I'm troubleshooting an issue now with the Messaging SDK in which a fake CM Client appears with Windows 6.2 NT Workstation, even though it is a fully patched Win10 machine. Weird stuff.

                Anyway, it would be great if the docs were…

                0 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  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
                • Add import code button to new Run PowerShell script task sequence step

                  The 1811 Technical Preview added a "enter or paste a PowerShell script" function to the "Run PowerShell script" Task Sequence step. That is an awesome feature, but even more awesome would an import code button that automatically puts the code in for you when you direct it to a .ps1 script.

                  0 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  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
                  • Run Powershell Script (Task Sequence Step) passed parameters not visible in logging

                    When parameters are provided on a 'Run Powershell Script' in a task sequence, the SMSTS.log only logs the name of the script. It does not log the full command (including parameters) that are invoked.

                    For example: if I call Java.ps1 with parameters -level 1 -language eng the SMSTS.log only shows...

                    Running powershell script: 'Java.ps1'(PkgID: SCM00000) with execution policy 'Bypass'

                    This would be helpful in troubleshooting what parameters were actually passed to the script that is executing. Otherwise you have to track down the task sequence and assume everything entered is passed and run. Or you have to build your PS1…

                    0 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  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →

                      Updating status to started.

                      We’ve made some improvements with the PowerShell step and Run Command Line

                      For more info:
                      Doc: https://docs.microsoft.com/sccm/core/get-started/capabilities-in-technical-preview-1811
                      Blog: https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Add-PowerShell-script-content-directly-in-the-TS-Editor-using/ba-p/294264

                      This item isn’t directly covered in the documentation yet. The functionality works similar to the variable OSDDoNotLogCommand – in this case it’s OSDLogPowerShellParameters

                      Set that to TRUE and the parameters are logged.

                    1 3 Next →
                    • Don't see your idea?

                    Feedback and Knowledge Base