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.
-
Updates and Servicing: Deploy new client package prior to upgrade
One of the most time consuming steps when we perform an SCCM upgrade is waiting for the new client install\upgrade packages to replicate to our lower bandwidth sites. Currently we are installing the latest update in the test lab and manually creating a package and distributing it in production with those files so the content library has the files at upgrade time. It would be helpful if there were an option similar to "run prerequisite check" to create the packages and distribute the content ahead of time.
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.
-
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…7 votes -
Refresh button in the Site Servicing Status node
A Refresh button in the Site Servicing Status node under the Monitoring workspace would really be useful. Just like the Refresh button in Updates and Servicing, it would provide an easier update method for the admin to be able to simply refresh the node, instead of switching between other nodes. These small enhancements are not critical,but they do provide a huge value.
7 votes -
Remove dependency on default document in IIS configuration
A common security vulnerability exists in the default IIS configuration when SCCM is installed. Having the default documents (eg iisstart.htm) can aide a malicious actor in discovery https://www.rapid7.com/db/vulnerabilities/http-iis-default-install-page
IF the default document is removed, Workgroup clients are unable to communicate with SCCM. The default document should not be a dependency on SCCM, or on workgroup clients ability to connect.
Symptoms: Clients not joined to the domain can not connect to an SCCM server
Client Location log shows http 403 errors
Error sending HEAD request. HTTP code 403, status 'Forbidden' ClientLocation
Text=CCMEBADHTTPSTATUS_CODE ClientLocationWorkaround:
Adding a default…7 votes -
Additional logging for DP upgrade
I would like to have additional logging when Distribution points get updated. Currently the update process is not really verbose if you look it from the SCCM Console point of view.
I had an issue with dll's not being upgraded in the DP Upgrade process and there was no trace of the error.Thanks
7 votes -
Put the complete SCCM Version into the database instead of having to query registry keys to get it
Currently the Database contains the build number and shows the base version such as 5.00.8498.1000 where the updated version is 5.00.8498.1700 or 1702 (currently in my case).
It cant be hard to store the "Friendly" version information in the database.
You could even break it down into Site version, Console Version and Client version if necessary if these components are likely to get out of step due to hotfixes.
7 votes -
ADK Presence check on Remote SMSPROVIDER in SCCM CB Upgrade Setup
MS Case : 17052664 >> Post upgrade of SCCM CB 1906 we realised that one of remote SMSPROVIDER server was not working properly. This remote SMSPOVIDER never had ADK installed on it since SCCM infrastructure was setup. Error never reported in the past in any upgrade but it stopped working post successful upgrade of 1906. In order to fix this issue in future it should be part of Prerequisite check in upgrade setup.
7 votes -
Allow Site system proxy to be configured as Winhttp proxy when we enable PullDP to fetch the content from CDP
Hello, When we try to configure the PullDP to use CDP as Source, the pullDP only uses the proxy configured on Winhttp service, neither the proxy configured in site system property or the Configmgr control panel applet are used. Seems at moment the admin has to configure Winhttp proxy manually to allow the pullDP to get the content from CDP, whereas this should be handled by sccm, whenever the Pulldp is being enabled in the console, the proxy configured on the Site system props has to be applied in the winhttp service on the system context as well.
Got to…
7 votes -
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 -
Add ability to configure location of OfflineImageServicing location
Would like the ability to configure location of OfflineImageServicing location.
6 votes -
Allow More Clients To Be Supported on a Primary site
Ability to support more clients than 150k on a single Primary site. Our environments could get rid of bottlenecks and less administration overhead if there is no need to deploy a CAS. It would be great if a Primary site supports up to 200k clients, because we have currently 160k in our environment.
6 votes -
Provide same MP forwarding for clients connected to standalone MPs than for Secondary Site MPs
When clients upload Information to a Secondary Site MP, that Information gets consolidated, compressed and then sent up in the hierarchy by ONE single file, in order to minimize WAN issues.
However at standalone MPs each small Client communication is being sent up using one little file, resulting in many little packages consuming lots of unnecessary WAN bandwidth.
That prevents us from getting rid of our secondary sites even though we urge to do so, i.e. because they caused critical failure when updating to ConfigMgr 1511 (classified by Microsoft as known Bug)6 votes -
Status Message Query - Double Click to Run
At the moment if you double click a Status Message Query, it edits it, So to run it you need to right click it or select it and click the button on the ribbon.
It would be better if this was reversed so that double clicks run the query and to edit it you right click it
6 votes -
Improvements to SQL AlwaysOn Pre-Requisite detection
Improve the SQL AlwaysOn Pre-Requisite detection so that "Set Trustworthy" and "Enable CLR" are flagged; if that's not possible prior to DB creation, could a note be added to the pre-req page with a warning stating these pre-reqs for SQL AlwaysOn? Today using 1606 baseline media, the installation nearly completes and then logs this error when those pre-reqs are not installed:
INFO: SQL Connection succeeded. Connection: <myserver> CMXXX, Type: Secure Configuration Manager Setup 1/26/2017 4:11:30 PM 5276 (0x149C)
SELECT dbo.fnConvertBinaryToBase64String(thumbprint) FROM master.sys.certificates WHERE name='ConfigMgrEndpointCert' Configuration Manager Setup 1/26/2017 4:11:37 PM 5276 (0x149C)
[42000][6263][Microsoft][SQL Server Native Client 11.0][SQL Server]Execution of…6 votes -
Geographical view that allows for adding site system location
With the ability to support 250 DPs and 2000 PDPs on a site, it would be helpful to be able to see the site systems on a map. Currently, the geographical view only accommodates site servers. DPs also make good sense, since they are typically geographically dispersed and would make a pretty map to show off to management.
6 votes -
Allow Slash (/) Character in Organizational Units for Group Discovery
When Group Discovery for the whole Domain is activated and there are Organizational Units containing the Slash Character in the Name, you get "failed to bind to Container" Errors in SCCM.
As long a Slash is an allowed character in LDAP, SCCM should be able to process these OUs correctly.
6 votes -
Pre-Req Checks
Perform permission checks on key locations where sccm will be setup. We had a problem experienced a few years ago where we had a "hash mismatch" error b/c the account I was using to perform the upgrade did not have permission to the install directory.
https://sccmf12twice.com/2017/02/sccm-2012-r2-sp1-failed-upgrade/
this problem is still possible in CB
6 votes -
check performance gains for specific compatibility levels when servicing sccm
When servicing SCCM (for example from 1802 to 1806) the compatibility level was changed from 110 to 130. The compatibility level was set to 110 specific because of major performance issues with level 130.
With the compatibility level being reset the update from 1802 to 1806 is already running for 43 hours and still not completed (CE level is already changed back to 110). Why not running a few SQL query's, based on this article: https://support.microsoft.com/en-us/help/3196320/sql-query-times-out-or-console-slow-on-certain-configuration-manager-d to check performance for each possible level. Then based on the results, change the compatibility level? If we have this kind of performance issue…6 votes -
SQL Native Client
The Components which were installed during the SCCM Setup should be updated during the Current Branch process if it's an necessary feature for the Environment.
For Example the SQL Native Client. The most Companies got an separated SQL Team and got an Problem of responsibility during the Upgrade process.
6 votes
- Don't see your idea?