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.
If you require assisted support, please see https://aka.ms/cmcbsupport for more details.
-
Cloud Management Gateway (as CSP)
With 1610, the Cloud Management Gateway feature arrived. Although it's a Pre-Release feature, as Cloud Solution Provider we're UNABLE to use/implement this. And so are our customers...!
When you try to set this up from the ConfigMgr console, a prerequisite is the Azure Management Certificate, which can't be configured as CSP-tenant because this needs the Classic Azure Portal (ASM). This is unacceptable for us, as CSP, as we would have to instruct our customers to get an Azure Subscription separately.
732 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
We have shipped this functionality in #configmgr 2010.
-
Site Server High Availability or Clustering
Configuration Manager is becoming more mission critical every day. The ability to Cluster the Site Server role (Inboxes & SMS Provider) is more and more important as that is the single point of failure for a Primary Site.
If the Site Server role goes down the Primary Site is down no matter how many Management Points or SMS Provider etc. exist.
If we could Cluster the Site Server or at least have 2 systems share that role for High Availability then this would no longer be an issue.
Even though we can designate multiple SMS Providers, if the site system…
439 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
We have now added hierarchy support with #sccm 1810. There is still some planned work outstanding (represented by UV items in the comments); but the core work for this is now complete in #sccm 1810.
-
Have the ability to remove a CAS when only one primary site is left
Beginning with 2012SP1, we have the ability to add a CAS to an autonomous primary site. It could be interesting to reverse the proposition by having the ability to remove a CAS above a Primary when a CAS is no longer needed or has been set for a wrong reason.
I know that it could be done through creating another hierarchy and using migration tasks by this is quite difficult for it requires additional hardware.273 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
I will mark this completed for now to raise awareness. This feature is in 1906 and 1910, but hidden. If your company wants to try it, and you have a premier support agreement, have your pfe reach out to the product team and we will partner with you on it.
-
Modify the Configuration Manager prerequisites checker to look for KB 3095113 if Server 2012 or Server 2012R2 is detected
as KB 3095113 is required to do Windows 10 servicing and as WSUS 4.0 requires that hotfix in order to correctly display the Upgrades classification, the prereq checker should check for this hotfix and if it's not detected warn the user along with a URL linking to a guide explaining the correct order to install the prerequisites for the hotfix and that the hotfix needs to be installed directly after installing WSUS.
259 votesThis is shipped in 1602. Please take a look and let us know your feedback.
-
Support V3 and newer certificate templates for HTTPS mode
Hi,
PKI- Make V3 Template compatible with SCCM Current Branch.
88 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
This is completed in #ConfigMgr 1710 for most all client communications. Some of the server<→server coms (i.e. app catalog) will be completed in the next release.
-
Support the windows server OS being upgraded on Site Servers (in place), w/o backup & recovery or migration.
Older version of windows server are falling out of support, or are deprecated for ConfigMgr current branch. i.e. Windows Server 2008 and 2008 R2. Support an easy way of upgrading those operating systems to newer versions of windows server.
77 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
Marking this complete. We support 2008 R2 → 2012 R2 with SCCM 1602 production build. We are investigating WinServ 2016 will will announce when that’s ready.
-
Reduce the amount of time needed perform a CM upgrade
For most companies, Configuration Manager is becoming a mission critical service the requires less and less downtime. Upgrading large environments/DBs can take up to 5 hours for the CAS, and 4-5 hours for primary sites. Also, most customers want to get the latest hotfixes installed right after performing an upgrade. In some cases, the hotfixes take just a long to complete as the original upgrade. Overall, this can require long outages (sometimes 2 days) to get current.
Potential Solutions:
The ability to upgrade directly to the latest hotfix as noted here:
https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/33166225-upgrade-sccm-directly-to-rollup-versionReduce the time needed to regenerate DRS sprocs…
66 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
We have made optimizations during SCCM upgrade to not do unnecessary SQL tasks. We are not considering upgrade directly to the latest hotfix.
-
SCCM Gateway Servers for Deployment to DMZ's
We should be able to deploy SCCM Gateway servers for deployment to DMZ, Internet and Remote locations where opening ports to the management servers / domains are not feasible. We are unable to forward ports from the internet to our LAN and must use a DMZ. There is no way to implement SCCM for IBCM because of this.
61 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
This is working now e2e in 1706. There is one more thing we’d like to fix, which is to have software center (optional software) to work through CMG too. We’ll track that remaining work with this UV:
https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/20353534-allow-optional-software-via-software-center-to-w -
Request for intelligent MP, SMP and SUP selection based on network location, like current DP selection
This is a DCR requesting that we improve the logic around MP, SMP and SUP selection by clients. Currently, we gather AD Site and IP Subnet details for DPs, store that in DPInfo and include that information in the XML body returned on content lookup requests. Why can we not do this for other server roles so that the client can choose the best server to connect to based on matching AD Site and/or IP Subnet? This would provide a far better solution than having to populate AllowedMPs, too.
49 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
Boundaries have been rearchitected and improved from 1610, 1702, and now finally 1706 production releases.
-
Download only applicable ConfigMgr upgrade packages with ServiceConnectionTool.exe
If you have deployed offline Service Connection Point, ServiceConnectionTool.exe now (in ConfigMgr 1511 - 1606) downloads ALL published ConfigMgr update packages when you use -connect parameter. E.g. if your site only requires post 1606 hotfix, ServiceConnectionTool.exe downloads 1602, 1606 installation packages although they are installed! Currently it will download over 7 GB of updates, when you just need about 25 MB update package. This is just waste of time, network traffic & disk space.
Please improve ServiceConnectionTool.exe, so it would only download the update packages that are applicable for the current installation.
43 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
This should be fixed now. Should only download the latest.
-
12 months to decommission any SCCM site servers running on Windows 2008 and Windows 2008 R2
Now that Configuration Manager vNext Build 1511 has been released, we have 12 months to decommission any SCCM site servers running on Windows 2008 and Windows 2008 R2.
All the details can be found here - https://technet.microsoft.com/en-us/library/mt210917.aspx
I'm working in a large organization and our SCCM infrastructure is made of 1 central site, 4 primaries and 622 Distribution Points running the Windows 2008 R2 OS...and we can not migrate as many servers in just one year...especially in the middle of the fiscal year where the IT budget has already been reviewed numerous times and approved by our management several months…
38 votes -
Make Cloud Distribution Point fully functional
Enable appropriate distribution point functions on Cloud DPs like Group Relationships, Content, Boundary Groups, Schedule, Pull Distribution Point, and Rate Limits.
of course, PXE and Multicast would not be appropriate Cloud DP functions.
36 votes -
Better control of settings like fallback of SUP site, Bandwith limitation, replication priorities of metadata
better control weather I want a site to fallback to primary or not.
real bandwith limitation instead of current posibility. Control priority of metadata35 votes -
Download only the latest Branch \ upgrade of ConfigMgr
both in online and offline modes of the Service Connection Point, when installing 1511 and then get the updates, ConfigMgr downloads 1602, 1602 hotfixes and 1606 EasySetups (and all of their prerequisites) when in 99% of the cases - we only need the latest release.
this causes a lot of time waiting and bandwidth usage for nothing and it will probably get worse as there will be more future release.
we want an option to choose what release to download instead of download them all28 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
This is fixed in ConfigMgr 1702. Beginning with that build, it will more intelligently only download newest updates. It will also do a better job of cleaning up old updates.
-
Support SQL Always On AG Asynchronous-commit
Configuration Manager Current Branch (1602) Supports SQL Always On Availability Groups, however it only in a Synchronous-commit replicas.
From TechNet:
Asynchronous-commit mode. This availability mode is a disaster-recovery solution that works well when the availability replicas are distributed over considerable distances.Synchronous-commit mode. This availability mode emphasizes high availability and data protection over performance, at the cost of increased transaction latency. A given availability group can support up to three synchronous-commit availability replicas, including the current primary replica.
This means that Configuration Manager can only support 3 secondary replicas in a SQL AO AG and they need to be in…
24 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
ConfigMgr now works w/ Assync commit.
-
Updates and Servicing does not clean up EasySetupPayload folder once a new version is installed.
As the final step in Updates and Servicing, remove previous installer files for current branch builds and superseded hotfixes from %ProgramFiles%\Microsoft Configuration Manager\EasySetupPayload or add and enable a scheduled cleanup script/
Also there are now 3 locations with the full installation source files:
%ProgramFiles%\Microsoft Configuration Manager\cd.latest
%ProgramFiles%\Microsoft Configuration Manager\EasySetupPayload
%ProgramFiles%\Microsoft Configuration Manager\CMUStaging21 votes -
Code change for the Service Connection Tool to allow proxy configuration
ConfigMgr 1511 CB's Service Connection Point came out of the box with a pretty cool ability to support Offline \ On-Demand updates even for those without internet access to their ConfigMgr environment through the Service Connection Tool. However for those in environments who have to content with Proxy this becomes an issue. While you can configure the site server system with proxy information that is only good for the system housing the Service Connection point, this post is requesting a change to add a switch and code base to support the switch to the Service Connection Tool to allow the…
20 votescompleted ·AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Changing status to completed. This has been address in SCCM 1606 production build, released yesterday
-
Non-cloud support continue
Please don't forget about those of us who work in an environment where we can't connect to the Internet. I've been very concerned by Microsoft's cloud-first effort turning into cloud-ONLY effort.
17 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
ConfigMgr will continue to be supported and innovated for non-cloud scenarios including servers and clients that cannot connect to the internet
-
Support for renaming a site server
Support for renaming a site server. Our stand-alone primary site server is the last server named by our old server naming conventions.
16 votes -
site restore
Add a way to perform a site restore to a system with a different name (but keep the same site code). In the event of a Datacenter Move, often times we are not allowed to retain the same system name (location based naming) and we end up having to stand up and entire new infrastructure and migrate.
While this is doable, it's tedious work and when operating in a Hybrid scenario with Intune, it means that we have to re-enroll the Intune managed clients to a new management authority. It's a whole lot of pain.
15 votescompleted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
This can be done in #SCCM 1806 with Site Server High Availability – by bring up a new machine with a new name, and making it the passive site server. Then you can fail over to it (making it active), and you can get rid of the original server.
- Don't see your idea?