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.
-
Improve automatic SQL configuration, tuning, and maintenance of the SCCM DB & SQL Server
Current architecture around SCCM’s management of SQL configuration and maintenance is old and hard to use. It requires a lot of manual oversight, and manual SQL tasks. And the default SQL settings created by SCCM are non-optimal. SQL is a powerful beast. Rethink ways SCCM can use it better, and keep it more optimally tuned and configured. Rethink how to run maintenance and backup tasks without downtime or impact to the production sites and deployments (this especially becomes more important with features like Conditional Access, that can never really have downtime.)
150 votes -
Use SQL Backup with Compression for the backup task
With CM 1511, SMS Backup task enabled by default. And that does a volume shadow copy of the DB which means full-sized files. For my tiny lab that means I'm backing up 8 GB alone.
For production it'll mean 850GB per primary site. Under CM12 when we backup just SQL using compression, it's just 160GB per primary site.
Please allow an option to just invoke a database backup instead so that compression can be used and I don't need to go order terabytes of data just for backups.
Also the current backup just erases the last backup. But in a…
126 votes -
Have updates automatically handle MP replicas
It's a real pain to have to tear down and rebuild the MP replicas every time I want to install a servicing update. It would be great to have the update process automatically save the replica state, point the MPs at the primary DB, tear down the MP replicas, do the update and then put it all back.
125 votes -
Add a check box to Maintenance Tasks to disable all temporariliy
When doing an upgrade to SCCM, it has been recommended to disable some, or even all of the site maintenance tasks. (per the upgrade checklist) Would be awesome to have a box on the Maintenance Tasks screen to temporarily disable ALL tasks while the upgrade is being performed. (as opposed to manually disabling all of them) An "upgrade/maintenance mode" box essentially!
59 votes -
suport Azure PaaS for SQL DB
Support ConfigMgr to be installed on Azure VM IaaS using SQL Paas as DB.
36 votes -
Decouple site component backup service from database server
Configuration Manager currently installs binaries and configures the SQL backup site component service on the database server, running under LocalSystem authority. Many environments have separate groups that host and manage the SQL Server enterprise environment, and do not allow for services or additional software to be installed on them, creating unnecessary conflict and drama when SCCM needs to be installed. SQL Server is a networked service, there shouldn't be a reason to install software on the database server running under a privileged account in order to leverage backup routines.
34 votes -
Add preflight checks and improve documentation for the “Modify SQL Server configuration” option
1.) When running the SCCM Setup Wizard and choosing “Modify SQL Server configuration” there does not appear to be an adequate preflight check to ensure Config Manager is running with full administrative rights to A) operating systems, B) SQL instances and C) Config Manager itself. These permissions are (obviously) critical to a SQL configuration change. In enterprise environments, setup.exe should be reaching out to check rights to all the things it needs to modify (file system, registry, certificates, etc.) before it executes the changes. Partial modification of the configuration has catastrophic results.
2.) Execution of the SQL configuration change does…
23 votesThanks for the feedback, updating status to Noted and moving to ‘Setup and Server Infrastructure’
-
Multiple Primary Site Servers for Migration of Host Operating System
Have the ability to add a second Primary Site Server to an environment running as a standalone site to allow migration from an older Operating System to the latest version e.g. Migrate your 2012 R2 SCCM server from 2008 R2 to 2012 R2 by adding a second primary site server, and allowing settings, data etc. to synchronise. Then retire the old 2008 R2 server.
16 votes -
better admin experience for troubleshooting site replication
@JasonSandys: "When it works, it works fine. When it breaks, God help you cause no one else can."
Add your comments on how we can make this better.
14 votes -
Ability to upgrade multiple CM07 secondaries to CM12 distribution points
CM12 is able to migrate only one secondary at a time.
10 votes -
Improve the process for using certificates within ConfigMgr
Setting up and managing the certificates for MPs, DPs and boot media is not straight forward. Could you improve the certificate management process to reduce the complexity and overhead in managing it. So automation with internal CAs for automatic certificate issuing would be good.
8 votes -
When running the "Modify site database configuration" option, allow support for keeping SQL servername the same
When going through the process of changing the configuration for the site database (in order to move it to a new SQL server), if you are keeping your SQL server name the same, the wizard will not allow you to input the same SQL server name as the old. We want to get rid of our SQL 2008 R2 servers running on Windows 2008 R2 and replace with Server 2016 and SQL 2016, but also keep the same hostname for the new server. Our only option since the wizard doesn't support this scenario is to do a backup and restore.
7 votesNoted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
great idea.
-
Service accounts should be domain aware to prevent account lockouts
Service accounts should be domain aware so that they do not attempt to authenticate against the wrong domain to lock out service accounts with the same username but on another domain.
6 votes -
Check if Cloud Service name is valid during Cloud Proxy Wizard
When deploying the new Cloud Proxy Service role in SCCM 1606, the user is asked to provide a Cloud Service Name. However, the UX does not explain that this is needs to be globally unique in all of Azure. I chose the name of 'SCCMCloud' turns out someone else already got that one though, and so the wizard completes and then fails in provisioning.
This is sloppy. The UX should include instructions for the end-user to validate their name first (which can be done in Azure -> Cloud Service -> New, you're able to test various names until you find…
5 votesNoted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
Thanks for early feedback. We have to make this simpler to not get wrong.
-
Upgrade logging improvements
Upgrade needs to have better logging - for example during an upgrade, the spimportinventory stored procedure was failing on a merge with SQL error 8672:
The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more than one source row.Tracking this down was difficult because of the MERGE statement - if each row were being processed separately, the specific problem data could be called out when an error occurs.
5 votes -
Reduce the number delta mismatch BADMIFS Generated
We get about 1000 deltamismatch BADMIFs generated each day.
Here is the case of sccm client Inventoryagent.log says successfully sent but the ccmessaging.log shows the upload failed.
Why can’t the client inventory agent act on the status back from ccmmessaginglog and if the upload of the inventory fails, don’t increment the delta number.
This would greatly reduce the number of deltamismatch files generated each day and improvement keeping the inventory up to date without having to force a full inventory sync for this case.Here are the details:
Dataldr.log for computer: CHOSIJ1-L2
Thread: 6108 will use GUID GUID:c28fa179-d722-4692-be69-a71f5a81e75c SMSINVENTORY…4 votes -
Show Last Backup Time of Site in Console (SQL / Site Maintenance)
It would be really useful to have the Last Backup Time of the SQL database and successful site maintenance task listed somewhere against each site. In addition, being able to right-click on a site and selecting "see backup log" would be useful (displaying the smsbkup.log or corresponding status messages for the SMSSITEBACKUP component via the console). This would make checking for successful backups much simpler for admins.
So far the only screen I can see this being useful on is under Admin > Hierarchy Configuration > Sites, but it obviously fits better under Monitoring. Maybe a new node…
2 votes -
Do not allow "SMS" as Site Code Name
I found some customers which has "SMS" as name of SCCM site. This make a lot of problems with normal management. This name should also be make as do not allowed (wizard blocks also other names). And if already named, it should allow one time change.
1 voteNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We do document this, and this has been the case since at least SMS 2003.
See:
https://support.microsoft.com/en-us/help/279868/reserved-site-code-names-in-sms-2003-and-configuration-manager
https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/prepare-to-install-sitesI’ve also confirmed that Setup disallows you from using the several “reserved” site code names and has done so since at least 2012 SP2.
Was unattended setup used? That’s the only way I can think of that may have bypassed this validation.
-
prerequisite
If prerequisite checker fails with a warning there should be an option to continue with the upgrade anyway.
1 voteThanks for the feedback. Can you provide an example of the failure, please? We have support for continue upon pre-req warning both in In-console upgrade and main setup
- Don't see your idea?