Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice - Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more

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. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  2. ccmeval fails to correct missing or renamed ccmexec.exe

    If the ccmexec.exe is missing (ie Malware) the ccmeval is not able to remediate and it does not trigger a repair of the SMS Agent Host client

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  3. AD forest discovery fails with "unexpected exception"

    AD forest discovery fails and does not continue parse through the other forests after and "Discovery is being aborted due to an unexpected exception".

    We would like to see where the discovery sees that it cannot contact or reach any given forest but is able to continue with the other forests to collect the data.

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. Add MAC addresses to Heartbeat Discovery data

    We find ourselves trying to go from MAC address to device in the console fairly regularly, especially when troubleshooting things like PXE from the logs (which only shows MAC address) and needing to kill off failed OSD records (which may be named "Unknown" or have a random computer name in ConfigMgr, but you're now in WinPE ready to kick off the TS again).

    If the MAC Address information was pulled with Heartbeat discovery, it could easily be used to filter the device list and find the resource .As the information rarely changes, it seems like it would be very lowā€¦

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  6. Missing WMI Classes needeed for Security Features

    For Windows 10 Credential Guard:
    -Processor class lacks information if Virtualization is enabled
    -Processor class lacks information if VT-x is enabled
    -No information available if Secure Boot is enabled (I had to add a custom MOF (local|HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\State|UEFISecureBootEnabled)

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  9. Registering network devices or printing devices.

    I would suggest the power option register within the SCCM network devices
    (Router, Switch, Access Point), network printers, my suggestion reflects a problem that meeting the clients.
    Since they always ask if it is possible to register these devices.
    My initial suggestion for registration may contain the following fields:
    - Device name;
    - Combobox if the device Network or device Printing;
    - IP address of the device;
    - Device location;
    - Device manufacturer;
    - Device model;
    For this active control of the company stands out, often the customer registers it in a spreadsheet.
    Say this registration is possible to achieveā€¦

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  10. Force AD Group Discovery to stay inside the configured domain

    We have a sub domain configured in AD group discovery for our site. However in our various AD groups we have users of that specific domain along with users from other sub domains in the forest. When group discovery runs, it escapes outside of our domain and tries to discover these users in the other domains. that dramatically slows down the discovery process to the point it can take more than 24 hours. I would love a check box option in group discovery to strictly limit discovery of users and groups to only the domain that is configured for theā€¦

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  11. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Client deployment and discovery  ·  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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  14. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  15. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  16. Allow different Discovery Schedules for each configured location

    We have many Discovery locations configured but we do not need discovery to run against them all on the same schedule. For example, we have many smaller domains where new objects are rarely created. We should be able to discover these environments less often than a workstations OU in our primary domain. The option to set both the Full and Delta discoveries would be ideal. This could extend to group and other discovery types as well.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  1 comment  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  18. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  19. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  20. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  0 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base