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. 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 →
  2. Keep the CM client store current and secure

    A new client should never result in an unpatched machine. Can't we get a way to keep the redistributable files like Silverlight up to date at all times?

    3 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 →
  3. Force Client Deployment on metered network

    We have several users who are ALWAYS on metered networks and will never get client updates.

    The client deployment currently does not honour the option "Client Setting - Specify how clients communicate on metered network connections".

    We need an option to override it for manual client deployment / update as well. (Force install checkbox doesn't work)

    Setting the connection to "not metered" in Windows 8.1/10 doesn't work when a 3rd party connection software is used and doesn't work at all for TCT Mobile LTE sticks so this is not a solution.

    64 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    11 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. Client Cache Maintenance

    Option for the Client Cache to be "purged" on a schedule. This helps keep systems clean and rid of unwanted files.

    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 →
  5. Reboot required after client upgrade

    sometimes the client needs to be rebooted after an automatic client update. if you're not connected to the machine (ie server), once you connect a notification appears but if you open the software center (old and new) you will not see anything pending reboot (installation status is empty or does not have the information that anything is asking for reboot). it would be great to see under installation status that the client was upgraded and it the machine needs a reboot to complete the installation

    2 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 →
  6. Include seperate client push settings for workstations and servers

    We would like the ability to have seperate client push settings for Workstations vs Servers, specifically the ability to have seperate installation properties.

    12 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    4 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. Computer Restart and patch installation notification before a Window hits.

    It would be nice to have a client setting that would allow for a notification before a maintenance window hits. So if I have a Window from 6PM - 5AM, and computer restart is set for 90 minute notification instead of it notifying me of a restart that will happen in 90 minutes at 6PM, it would notify a user at 4:30 that patches are going to apply and the computer will be restarting in 90 minutes.

    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. honnor / discard work hours for client upgrade

    Please provide an option to honor or disregard the (maintenance windows) working hours set locally. In some scenarios client does not update to the latest CU level when client only operates in the work hours and is shut down.

    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. Purge content from ccmcache when it is no longer referenced in ConfigMgr.

    It would be great if you could set a schedule on the client (like weekly, monthly, etc) where the client could look at the content in its cache, and see if it still exists in ConfigMgr - if not, purge it. For example, run a content location request for each instance in the client cache, and if no locations are returned, remove it from client cache.

    4 votes
    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. The ability to tell an SCCM client to IGNORE specific NICS for site determination or SCCM Client communications

    The ability to tell an SCCM client to IGNORE specific NICS for site determination or SCCM Client communications.

    We have a number of clients that are multi-homed, the SCCM client is often choosing interface that cannot communication with the SCCM infrastructure to determine site membership.

    Our clusters fall into this category. 'secure web application servers' that have a "Client Network", "Admin Network", "Backup Network" and "Management Network" connections.

    May something similar to the NOSMS file, that will tell the client to not use specific interfaces but continue to inventory, configure, etc.

    17 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  1 comment  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  11. Check for an existing CCMexec service before ccmsetup.exe executes.

    Problem: On the client machine, CCMEXEC service is already running, the client is in a healthy state. Then a GPO or Client Push happens, ccmsetup.exe starts and breaks the client communication. The client ends up getting an error stating "another instance of ccmsetup.exe is already running".

    Question: Could you have ccmsetup.exe check for the ccmexec service and quit if the ccmexec service is running?

    4 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 →
  12. Change target computer mapping for state migrations (USMT)

    Please make it possible to change the target computer when using state migration points as a means of transferring user data to one pc to another.
    The scenario would allow the backup (scanstate) of the old pc data, utilizing all positive aspects of SMP (centralized, encrypted, storage based on boundaries). IT could then later set target computer, which may not be known at the time the data gets saved.
    Ideally this should be possible in the admin console by ā€œeditingā€ the state item to map to a new computer, just after it has already been created. ā€œLate mappingā€ so toā€¦

    91 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  13. Add Agent Installation Monitoring from Console

    I think the missing half of agent installation from the console is a way to monitor installation progress, success, or failure. SCOM has this, and I think it could be added to the Monitoring workspace, in client operations. Installation progress should be viewable by device collection or individual device. Monitoring installation progress should also be a last, optional step in the install client wizard, where an administrator could close that if he/she so chooses and see the same information inline in the console, as mentioned.

    2 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. Sccm client resets its policies and download new ones every couple of days

    Sccm client reset its policies and download new ones every couple of days, it should delete it's policies, inventory and then download new policies, perform inventory and perform a DDR. I currently have a script that does this via a scheduled task.

    3 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. Exclude workgroup computers from Automatic Client Upgrade

    When using ACU computers in workgroups cannot upgrade because they are not able to query Active Directory when "ccmsetup /upgrade" is executed. We have seen some scenarios where the installed client on workgroup machines crashed after each failing installation trial. It would be great if an option was implemented to either exclude workgroup computers or provide a list of domains that should be considered during ACU.

    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 →
  16. Combine ClientPatch and Patch property

    The outdated ClientPatch folder in the 'Configuration Manager Client Package' is unsupported, however it is a great combination for retrieving from a local DP (leveraging the /mp-option to retrieve content based on boundaries) and getting the patch installed.
    Considering that CCMEval also reruns with the last command-line used the availability of a ConfigMgr patch is vital (otherwise a 1635 error is generated if the new installation attempt can't access the MSP-file) perhaps the supported Patch-property and the ClientPatch-concept can be combined into a new supported way of deploying patches?

    The scenario would be as follows;
    CCMSetup detects that there isā€¦

    27 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  1 comment  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  17. WMI Fix integrated with SCCM Console

    WMI Fix integrated with SCCM Console and improve client installation description error.

    23 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  18. Deploy certificate with the Client (like in Intune)

    Certificate would tie up the ConfigMgr Client to a specific site and would make connecting ConfigMgr Clients from the Internet easier with MP in Azure.

    3 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 →
  19. Ability to Control/Limit Wake-Up Proxy Candidates

    The nomination for Wake-Up proxies is fully automated.
    From testing, up to three devices per subnet will remain switched on (or in some cases start back up if a user shuts them down). This is not appropriate in cases where a small office may contain only 4 or 5 machines.
    Additionally, if a server is located at a particular site (DP for example), this should be the sole wake up candidate, due to the fact that the likelihood of that device shutting down is minimal.
    I propose changes to achieve the following:
    1) The ability to designate specific Wake-Up proxies ā€¦

    4 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  0 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  20. Client Push installation status in ConfigMgr console

    It would nice to have a client push installation status in the console. We already have client installation status messages (FSP), so why not display them in the console? As a consultant I always see a disappointment in the admins faces when I try to explain that they have to wait for the client flag, search client logs or use reporting for client installation status.

    11 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base