Microsoft

Microsoft Endpoint 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 Microsoft Endpoint 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 Microsoft Endpoint Configuration Manager feedback site is moderated and is a voluntary participation-based project. Please send only feature suggestions and ideas to improve 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. client push

    Add a possibility to start the client push over powershell remoting.

    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 →
  2. I have a suggestion for the SMSSLP parameter and registry key.

    I was investigating the registry Key SMSSLP under HKEYLOCALMACHINE\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…

    3 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 →
  3. 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 →
  4. ccmsetup <specific/latest> client

    Create a new Parameter for the ccmsetup to use the latest Client Version. Currently there is no Opportunity to install the newest Client Version by Script. So in Cases of Troubleshooting the Client will be installed/updated two times within an short period.

    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 →
  5. Allow OSD or Application Deployment to Uilitize "Please Wait" Screen (see screenshot)

    There are times where it would be very helpful to basically lock the screen with a message to the end user to please wait for an application or maybe part of OSD to complete (see screenshot).

    This would be extremely helpful for deployments that occur at startup/logon/logoff/shutdown and would prevent the issue of installations being broken due to a user logging on and launching an application while an install is in progress or powering off the device because something is holding up the process.

    As an added bonus, customization of the message on this screen would be useful so we…

    2 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 →
  6. Require Permissions for Client Push

    Provide the option for permissions that would disallow client push. We would like to provide access to users to manage SCCM but do not want them to be able to push the client from ConfigMgr. In our particular case, client push does not work with our network setup, so if someone attempts to do a client push, the process gets stuck. I can imagine some security reasons for this setting as well.

    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 →
  7. 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 →
  8. Disable 24hr cache hold

    Add a checkbox in client settings to disable the 24hr hold on cache packages or set soft limit till hdd reaches x space.

    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 →
  9. Create "sysprep" for SCCM agent

    Microsoft does not officially support the installation of the SCCM agent on template/image operating system. I need an officially supported process to create an instance from an image and have the SCCM agent work correctly with any site.

    2 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 →
  10. No more ccmdata.bak

    Please, for the love of all that is holy, stop creating the ccmdata.bak file and storing guids in a directory that is **** near inaccessible on citrix machines, or at least give me an installation option to specify not to do this. I don't see any benefit to this at all, and you end up getting sccm inexperienced Citrix admins installing clients with duplicate guids even though you remove certs, ini files and other identifying information.

    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 →
  11. Active Directory System Discovery discovers Linux servers and tries to push clients to them

    Active Directory System Discovery discovers Linux servers with an OS type of "Microsoft Windows NT server linux." This triggers automatic client push installation.

    The installation fails because there is no Admin$ share on a Unix\Linux server.

    The CCM.log shows this failure:

    ---> Attempting to connect to administrative share '\server.unix.domain.org\admin$' using account 'domain\SCCMAccount' SMSCLIENTCONFIGMANAGER (0x8434)
    ---> WNetAddConnection2 failed (LOGON32LOGONNEWCREDENTIALS) using account domain\SCCMAccount (00000035) SMSCLIENTCONFIG_MANAGER

    Several workarounds could resolve this issue:


    1. Add an "exclude collection" to client push properties so that *nix clients can be excluded.

    2. Fix the OS type of *nix…
    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. 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 →
  13. Option to throttle content to computers without a local DP at the site

    I love a way throttle content delivery to any computers that do not have a local DP at their site.

    I can setup client policies but if the computer moves from site to site, this doesn't work. As one site may have a local DP and the other does not.

    If there is a DP at the site, they will receive content quickly without consuming bandwidth. So there is no reason to throttle. However, if they're at a site without a local DP, we have it going to our main sccm server at our datacenter. The delivery can consume quite…

    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 →
  14. Client upgrade via APPLICATION rather than PACKAGE

    Rather than use the outdated Package model to deploy Client upgrades after upgrading to a CU/SP I would like to see an application model that can determine cause of failure etc.

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

    I like you to remove or encrypt SCCM NAA username and password in the ZTIGather.log

    its in clear text and a BIG security vulnerability *** it on ALL Client deploy from SCCM it store in C:\Windows\CCM\Logs...

    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 →
  16. define user affinity based on AD logon rights onto specific workstation/system

    define user affinity based on AD logon rights onto specific workstation/system

    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 →
  17. 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 →
  18. I would like to see devices that are online, even if they don't have a client installed. IE, they are pingable.

    I would like to see devices that are online, even if they don't have a client installed. IE, they are pingable.

    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 →
  19. Streamline SCCM Agent installation/upgrade for workgroup or another-AD-domain device

    Include wizard so that it is easier to upgrade SCCM client running on workgroup devices since this usually includes hosts file IP/FQDN update. SCCM 2012 seems to promote side-by-side SCCM Server upgrade instead of in-place SCCM Server upgrade. This makes it more frequent to update hosts file on workgroup devices. This issue is also applicable to devices running on another AD domain but joining the same SCCM 2012 Server.

    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 →
  20. Overview pane to monitor automatic client upgrades to new service pack

    With R2SP1 automatic client upgrades will now function for the first time in an R2 environment.

    It would be nice if that deployment wasn't hidden though so we could actually see the progress of the clients being upgraded.

    1 vote
    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 →
  • Don't see your idea?

Feedback and Knowledge Base