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. Detection and remediation scripts should have more control over the execution of PowerShell

    When defining a Configuration Item with Powershell have the possibility to influence the behavior of the script (eg -noprofile, setting allowed time to run)

    286 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  Compliance Settings  ·  Flag idea as inappropriate…  ·  Admin →
  2. Control cache size using client settings

    It would be nice to be able to control the client cache size settings using the client settings policies. This way you have a simple way to increase it if you have a package which is larger than the initial deployed size.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Compliance Settings  ·  Flag idea as inappropriate…  ·  Admin →
  3. "Run scripts using the 32 bit scripting host on 64 bit devices" for Configuration Items and Baseline not working as expected in SCCM 1606

    We are experiencing the issue as mentioned in the below article:
    https://thesccm.wordpress.com/2016/09/02/sccm-1606-bug-32-bit-process-powershell-detection-method-doesnt-work/

    We have tested the same in 1511 and 1606, and behavior is that it works on SCCM 1511 but it doesn’t on SCCM 1606 as it doesn’t run a 32 bit Shell:

    SCCM 1511:
    ==========
    With Run as 32Bit – Compliant for Greater than 0 condition
    Without the option – Non-Compliant as expected because it is unable to find the class

    Script command line: "C:\Windows\system32\WindowsPowerShell\v1.0\PowerShell.exe" -NoLogo -Noninteractive -ExecutionPolicy Bypass "& 'C:\Windows\CCM\SystemTemp\4375f470-32c6-497c-be63-d3ada81153df.ps1'"
    Script command line: "C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -Noninteractive -ExecutionPolicy Bypass "& 'C:\Program Files\SMS_CCM\SystemTemp\cd4b0516-48fd-41f2-a2c3-cd249b53417a.ps1'"

    SCCM 1606:
    ==========
    With Run as…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Compliance Settings  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base