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. Delivery Optimisation cache server install failed with proxy

    When a Delivery Optimisation Cache server use a proxy configuration the installation fail (CMCB1910).

    The DoinCSetup log show :
    Setting proxy chain to proxyservername:8080
    …/…

     Cound not find existing downloaded content in primary disk cache: H:\DOINC-E77D08D0-5FEA-4315-8C95-10D359D59294\b1.download.windowsupdate.com\mscomtest\cedtest\r20.gif.full
    

    …/…

    Failed to find downloaded content in the primary disk caches

    Allow server cache to use a proxy

    60 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  2. The Summary and Details about the Distribution Point Configuration Status is inconsistent

    The summary can remain blocked under an “error” status even when all the statuses from the “Details” tab are “Success”.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  3. Let Azure Active Directory joined Client be Peer Caching source

    Today peer cache source needs to be an on-prem domain joined device, as customers is moving to Azure Active Directory getting support for AAD joined devices as peer cache source will help customers that are moving to AAD joined devices and want to remove on-prem DP's.

    From docs:
    A peer cache source must be a domain-joined Configuration Manager client. However, a client that's not domain-joined can get content from a domain-joined peer cache source.
    https://docs.microsoft.com/en-us/configmgr/core/plan-design/hierarchy/client-peer-cache#requirements

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  4. Orphaned Content Cleanup disrupted when distribution points are offline

    Currently on Current Branch 1906. There are times when we have certain pull distribution points offline. When distmgr is attempting to do content cleanup for orphaned content, this cleanup process in distmgr.log is disrupted if it come across an offline pull distribution point. Here is an example where it's deleting fine from server XX and then encounters issues with an offline server YY.

    Successfully removed content 889435e8-0ae8-4282-919b-8d078f95b024 from server XX 1/29/2020 7:29:12 AM 13776 (0x35D0)
    permanently deleting 29493F5488AD32889C759D1264C33346F5EA60A46C2C1B0DBF5CE69A59870828 1/29/2020 7:29:12 AM 13776 (0x35D0)
    CWmi::Connect(): ConnectServer(Namespace) failed. - 0x800706ba 1/29/2020 7:54:24 AM 13776 (0x35D0)
    CWmi::Connect() failed to connect to \YY\root\SCCMDP. Error…

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  5. Include an option in a program deployment to not allow peer cache

    Would be a nice option to exclude certain deployments from allowing clients to use peer cache as a content source.

    This would help for situations where content needs to be downloaded but also immediately cleared from the client cache, thus causing other client downloads to fail until they fall back to a DP, or randomly find a peer that hasn't deleted or modified the content.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  6. Monitoring - Distribution Point Configuration node should show BranchCache/MCC

    currently it shows PXE, Multicast etc - would be nice if it could show BranchCache and MCC status too!

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  7. Pull Distribution Points do not recover from BITS Errors -2147024893 "The system cannot find the path specified."

    Pull Distribution points will get into a state where they can no longer download a specific file for a software update package when source version changes. As a result, BITS put many jobs in an error state as such....


    Get-BitsTransfer -AllUsers | select *

    JobId : 3b528bdb-d257-4759-8808-a3ceb867a4cc
    DisplayName : CCMDTS Job
    Description :
    TransferType : Download
    JobState : Error
    TransferPolicy : NoSurcharge
    OwnerAccount : NT AUTHORITY\SYSTEM
    Priority : High
    RetryInterval : 60
    RetryTimeout : 3600
    TransientErrorCount : 58
    ProxyUsage : NoProxy
    ErrorContext : LocalFile
    ErrorCondition :
    InternalErrorCode : -2147024893
    ErrorDescription : The system cannot find the path specified.

    ErrorContextDescription :…

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  8. Option to pre-cache Applications/Packages using right click tools

    Add a Right click option to allow an Administrator to precache content for an Application/Package, which can be delivered to a Peer Cache Source device collection. In addition, add a page under Monitoring (e.g. add to Distribution Status' folder) which will allow an Administrator to monitor the applications/packages currently being precached on Peer Cache Source machines ('SuperPeers').

    It seems strange that Microsoft would introduce Peer Cache feature without a satisfactory way of precaching content (e.g. 'Download Package Content' in TS does not work for Applications!!) and the idea that we should setup a Required application for a date in the…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  9. LEDBAT: Enable on Primary Site Servers and SUPS

    The existing LEDBAT integration only supports DPs serving clients (or Pull-DPs). LEDBAT would also be usefull in other scenarios:

    Distribution Manager's push of content down to 'normal' DPs.
    SUP's WSUS distribution of metadata.

    Both use cases can occasionally/unexpectedly consume more bandwidth than desired so lowering the bar to using LEDBAT would be awesome.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add a function to allow downloading files without extension

    In CB 1906 environment, when performing package deployment, if an empty file without extension is included, the content download fails.
    The file name contains double bytes.
    As an additional condition, it occurs on receiving content from peer cache sources.

    The solution is to add .txt to the extension and the download will be successful.
    We hope that files without extension can be downloaded without any problem.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  11. Enable support for Delivery Optimization and Connected cache for Config Manager deployments

    If you allow fallback to Windows Update e.g. for Windows Updates or Office 365 Updates, enable config Manager Client to use Delivery Optimization to download content, without the requirement of using co-management.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  12. LEDBAT support for Super Peers

    Implement LEDBAT content sharing setting for Win10 1903+/Server 2016+ Super Peers. I'm thinking this is a quick win to implement, since LEDBAT is already present and used for Delivery Optimization.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  13. Bind MP & DP to boundary

    Make it optional wether a client should use normal logic to identify MP and DP or hardcode which site system(s) to use.

    Boundary A : normal behavior
    Boundary B : MP = Server1 DP=Server3

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  14. Binary differential replication column

    Software Library node - Software Updates - Deployment Packages:
    Would be nice to have a column so you can see at a glance which packages are enabled for binary differential replication.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  15. AI-supported, predictive content locations (Super Peers, DPs, Cloud DPs)

    Planning your content distribution in ConfigMgr is usually a one-time thing but over time - especially in large environments - optimization of said distribution infrastructure tends to become a "when we have time for it" job while the network topology can change drastically; sometimes without ConfigMgr admins knowing about it. Proper boundaries, branchcache, delivery optimization, pull-DPs etc. already provide great tools for us to optimize this but some questions remain and are currently not answered within ConfigMgr itself:
    - which clients could become viable peer cache clients?
    - which DPs should act as pull-DPs and from which DP should they…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  16. Redistribute all failed content

    Add an option to Redistribute all Content that has failed to distribute to either a specific DP or in general.

    Also having a Maintenance Task that does this automatically would be great.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  17. Much more robust content distribution

    Most of my time in CM is cleaning up content distribution. Packages in WMI but not in Content Library, in Content Library but not in WMI, content failed validation, etc. We need a much more robust content distribution process. If the package list is not correct, auto repair. If content is in the content library but not vaild, remove it. If content distribution fails, retry it AFTER the previous has been cleaned up. Having to run PS commands to remove orphaned packages from WMI, and then run SQL queries to find packages ID's for Applications (which should be a column…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  18. Seperate repoistory & ccmcache directory on client

    If OS supports Dedup.
    Enable this feature as a pre-requisite to client installation.
    Create a vhdx (mounted as the ccmcache folder.
    Create 2 primary folders in this vhdx (repository & cache)
    set the repository folder as the cmcache folder for downloads.
    subfolder should be named by the guid of the application in console.. not a random folder.. with ".x" designation for the content version.

    When applications are executed from ccmcache.. copy those folder contents to a cache matching folder.. and execute from there..

    This will prevent hash mismatch when peer sharing files.

    enable Deduplication on the vhdx file.. and you…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  19. Separate content within the application model

    Right now, the application is definitely decent and getting better. A major improvement over some other products within the same space. I do however, think that content assignment should be waaaaay better with this simple change.

    Applications have Deployment Types, and DeploymentTypes may or may not have content associated with them. If you create two Deployment Types that share the same content, it is confusing because the content appears as if it is separate (Based on the Content ID), although it is the same (Because of the way SCCM handles content > Single Instance File Storage)

    I think it should…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  20. Redistributing Failed Content

    In the Content Status node of the Monitoring workspace, add an option to allow all failed content to be redeployed without having to go into each package/application and selecting redeploy. When a site has numerous packages that have failed to deploy, having the option to easily redeploy all of the failed content (or specific packages) at the same time would very useful.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 8 9
  • Don't see your idea?

Feedback and Knowledge Base