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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Automatic Client Upgrade: Allow option to ignore maintenance windows

    It is great that client upgrades now respect maintenance windows per the "Automatic Client upgrades - respect defined maintenance windows" feedback. However, we now are dealing with the opposite issue.

    We have very narrow maintenance windows defined for our servers and as such 75% of our clients were out of date 2 months post upgrade. It would be great for a toggle on the upgrade configuration so we can choose the behavior for the upgrade to respect the windows or not, similar to a normal application deployment. This way we would not need to manually push the client upgrade out…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Terms "pre-production" and "production" might not be best in context of automatic client upgrades

    Although we use term "piloting" in the package name, and there are references to term "staging" internally (database) as well, for UI/settings we are using term "pre-production". Althoug same "instance" of SCCM implementation/hierarchy can be used to manage multiple environments (development, QA, pre-production, production etc.) using term "pre-production" within the same instance of SCCM implementation/hierarchy can be confusing since it's technically still the same SCCM environment (whereas "pre-production" implies a different environement). This is especially confusing for customers who have separate/isolated SCCM instances/hierarchies managing their pre-production environments (DEV, QA, etc.).

    Therefore, the suggestion is to replace use of term "pre-production"…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  3. client issues in 1610

    We are facing issues with the new client in 1610. mainly it is very slow to load and returns errors at time. The service does not respond to restart calls. Finally, Sorting by status for installations does not work as expected.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  4. "Maintenance Windows" for Client Auto Upgrade feature

    We often found that SCCM Client is not working because SCCM client was corrupt during client.msi installation was failed due to external OS shutdown. OS shutdown during upgrade may cause corrupt SCCM client but we cannot set "Maintenance Windows" for Client Auto Upgrade in current SCCM version and so it is difficult to avoid this situation. We want to add "Maintenance Windows" for Client Auto Upgrade.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Client Uninstall in console

    I'd like client uninstall option by right click. Which will be helpful to remove unwanted machines.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Push client

    To add the possibility to select a specific "Client push installation account" from a list in the client push wizzard

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  7. I have noticed many problems regarding the deployment of the updates but I wanted first before deploy sending a notification to warn during

    I have noticed many problems regarding the deployment of the updates but I wanted first before deploy sending a notification to warn during 5 times that the machine of the same will have to be restarted

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Client push function

    Client push function

    1. The SCCM Client Agent is to be rolled out on a client PC.
    2. For some reason, the SCCM Client Agent can not be installed on the client PC.
    3. Now you can not cancel the rollout on this client PC.

    It would be nice if you cancel the rollout or is prevented.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  9. I have a suggestion for the SMSSLP parameter and registry key.

    I was investigating the registry Key SMSSLP under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM.

    Most of my computers have a decommissioned Management Point in this Key. As far as I can tell this won’t have any effect. But this is confusing when troubleshooting client problems.

    After some experiments these are my conclusions:
    • The key is filled in when you use SMSMP=… as parameter for ccmsetup.exe.
    • The key is read when you start ccmsetup.exe and then added to the command line as SMSSLP=…
    • You can only change the key by adding SMSSLP=… yourself to the command line. (Or edit the registry of course.)

    …

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Easier to implement other Custom OSD menus

    Easier to implement other Custom OSD menus. I have written a new front end (We deploy offline to classified systems with specific configurations). There is very little information on how to implement your own custom OSD. I built one in PowerShell Studio but have yet to implement. Still trying to figure how to do it. Current GUI is limited.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  11. SMS Agent Host Startup Type - Client Setting

    There should be an option in the Client Settings to select the Startup Type for the SMS Agent Host. It takes a couple minutes for the agent to start by default since it's set to Automatic (Delayed Start).

    While I think that this should remain the default, it should be an option in client settings to switch this to a regular Automatic startup type.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  12. Switching Connection Type should be easier

    As far as I know, the only way to change a clients connection type to "Always Internet", "Always Intranet" or to a switching Connection Type (Currently Intranet/Currently Internet), is by re-installing the client. How nice would it be if we could control this setting without having to re-install the client.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Include updated Windows Update Agent during client install

    There are well documented issues with issues when using older versions of the Windows Update Agent. The configmgr client install still just checks for the base level of the Windows Update client. The client install should include the most up to date windows update agent so that customers will not be required to deploying the updated agent after client install to resolve known scan and related issues.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  14. Prevent people from creating programs/deployments from the build-in Configuration Manager Client (xxx00003) package

    When you do an upgrade from CM12 SPx , prevent people to have programs/deployments from the build-in Configuration Manager Client (xxx00003) package . When you do not look / validate closely - your clients all get updated in no-time when your 1511 site servers go's online - even when you disable site-wide upgrade .

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Update SCCM Client install to download and install the latest WUAgent

    Why does the SCCM client still download the 7.6.7600.256 for Windows 7 when the latest version is 7.6.7601.23453?

    Would be good when the sccm installs or upgrades that it attempts to install the latest version.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  16. 0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  17. collection with a deployment

    Run download computer policy automatically when a computer is added to a collection with a deployment.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
1 2 3 4 6 Next →
  • Don't see your idea?

Feedback and Knowledge Base