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. 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. 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 →
  13. 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 →
  14. 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 →
  15. 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 →
  16. Recovery partition

    When creating a recovery partition with the task sequence you only have the option of 1% to place at the end for succesfull creat a recovery partition.

    For a disk of 256 mb its 2.5 gb recovery
    512 mb -> 5gb recovery

    Please make ik possible to choose the space we want, suggestion of 1 gb as the larger the disk the larger the waste of space is.

    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. Chanage the SCCM Client installation so that it can be monitored for completion more easily.

    In cases where we need to install the SCCM client from a script or other process, Ccmsetup.exe launches sub processes then exits. This makes monitoring the installation difficult. It would be helpful to have the setup behave more like a traditional installer.

    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. The ability to set the Client Push installation syntax from the client push wizard.

    Currently the install syntax needs to be set before you initiate the client push request. If your pushing to multiple domains or forests, you need to adjust your syntax, then go back and select your targets to push to. It would be nice if you could specify the install syntax for the client push during the client push wizard.

    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. SCCM client shortcuts

    Shortcuts for the SCCM client should have the ability to be created on the start menu and the task bar. Today, the shortcut can only be created on the desktop

    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. SCCM client Agent deployment too slow after upgradated to 1702

    hi,
    we upgraded SCCM 2012 R2 SP1 to 1702, after up gradation process , to deploy sccm client agent new version, this process is too slow after 3 days only 100 client were updated out 12000.

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

Feedback and Knowledge Base