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

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 System Center Configuration Manager feedback site is moderated and is a voluntary participation-based project. Please send only feature suggestions and ideas to improve Microsoft 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.

How can we improve Configuration Manager?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

When an admin closes an idea you've voted on, you'll get your votes back from that idea.

You can remove your votes from an open idea you support.

To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".

Tell us your idea

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

Problem: When an application has "require approval" enabled we get a long list of users or devices where this application is approved for. But when I add a new application and delete the old, I loose all approvals! And the users need to request again.

This is a problem in multiple cases:
1) Example 1: We have an application in version 1.0.1 that and get a new version 1.0.2 I want to make a new application and test this. When it is tested I want to turn on "superceede" and then remove the old application. The license is still valid for all that got the previous version approved, so these users should not need to request a new approval. And new users should request the new version from Software Center

2) Example 2: We have a software in a major version and get a new version in a newer major version. For instance we may have Visio 2016 and then we want to use Visio 2019. Again I want to create a new application, test this, and then when it is tested automate upgrade. We have enterprise license so all users that are approved for 2016 version are allowed to use 2019. No need for new approval.

--
If it is difficult to add the feature in the console itself, a powershell script would be OK.

Br
Torstein

Problem: When an application has "require approval" enabled we get a long list of users or devices where this application is approved for. But when I add a new application and delete the old, I loose all approvals! And the users need to request again.

This is a problem in multiple cases:
1) Example 1: We have an application in version 1.0.1 that and get a new version 1.0.2 I want to make a new application and test this. When it is tested I want to turn on "superceede" and then remove the old application. The license is still valid…

Right now when you setup the Microsoft Store for Business connector and when you approve apps in MSfB. CM downloads all new updates of this apps.

After a while, the storage used by staled versions is quite huge.
For example, if you approve 10 apps (especially Office Apps : Word, Excel, PowerPoint). If there are lots of updates on it, you can reach up to 40 GB of storage content after 2 years. Around 38GB are not used anymore and takes space on the site server.

You should include an automatic cleanup process to delete old versions.

When deploying software to device collections that have a maintenance period the software downloads then waits for the maintenance period to begin installing. It would be great to have the option to defer the downloading process until either the maintenance period or a set amount of time before the maintenance period. This would allow IT departments to defer large software deployments to a time when network traffic is low.

Optionally, provide a new option in the maintenance period settings for when application downloads are allowed to happen.

The new App Approval feature in 1810 is looking great. So we can build on integration with other services and service desk software it would be handy to include the users “comment” in the email body.
Expanding on this and having the ability to add a “cost” and “billing code” field to the app request will enable the app procurement lifecycle to more streamlined.

Thank you for the Auto close of the executable specified on the install behavior, the problem I have is chrome.exe, aftre the application closes, it starts the install, if the user just starts it up again, it continues to run again, leaving 2 versions installed, chrome.exe, and new_chrome.exe, with the request to admin credentials to update, corrupting the installation

Can we add to the Automatically close, keep closed until installation returns a Zero

Update the estimated install time shown in Software Center for applications based on install times from other clients. This could use an average of the install time over all clients or be more advanced and take into account system specs to determine an estimated start time.

We want to be able to differentiate the Windows 10 versions. Some Appliactions should only be available to a typical Windows 10 version for example Windows 10 1803. Now(SCCM 1810) we only have the option to add a requirement for All Windows 10 (x64) or All Windows 10 (x86).

First off - Thank-you very much for the Email approval in CM 1810.
For the first improvement request, I'd like to request it be able to be sent to Manager or Application / Support owner already identified in the application.

These 3 options would cover nearly every workflow possibility instead of a hardcoded email address.

Usually you require permission from a BA or Business owner of the application, a Technical resource (Helpdesk, etc), or your Supervisor for an application. 2 of these items are already tracked in the application, and the third is (should) populated in AD for the requesting user.

First off - Thank-you very much for the Email approval in CM 1810.
For the first improvement request, I'd like to request it be able to be sent to Manager or Application / Support owner already identified in the application.

These 3 options would cover nearly every workflow possibility instead of a hardcoded email address.

Usually you require permission from a BA or Business owner of the application, a Technical resource (Helpdesk, etc), or your Supervisor for an application. 2 of these items are already tracked in the application, and the third is (should) populated in AD for the requesting…

Allow already deployed applications to be modified for email approval.

With 1810 you can now select to have emails sent when an application approval request is generated. That's great! However, you can only do it for applications that are deployed after the upgrade to 1810

It would be great if this functionality could be added to applications that are already deployed.,

Make it easier to troubleshoot application deployment with:
- Consolidated log file
- Make logging easier to understand and find the reason for failures.
For a new SCCM Admin/Tech troubleshooting appdeployment is hard, have to understand the different log files and know which one to read.

The ability to right-click a single device, or a device collection and select an option saying "Install Application or Package". This would then allow you to deploy an application or package without having to use a collection, especially if just for one device. It would also allow you to deploy the application or package without needing to build out a deployment for that application. It will just install the selected application or package without any additional configurations needed.

How often do we need to deploy an application to just one machine that is outside of a collection, or deploy to just one machine for immediate testing without having to build a test collection, then add the software to that collection, then run the application requests, wait for it to show up and then deploy. This would speed that up substantially.

The ability to right-click a single device, or a device collection and select an option saying "Install Application or Package". This would then allow you to deploy an application or package without having to use a collection, especially if just for one device. It would also allow you to deploy the application or package without needing to build out a deployment for that application. It will just install the selected application or package without any additional configurations needed.

How often do we need to deploy an application to just one machine that is outside of a collection, or deploy to…

Within the Application information tabs such as Summary, Deployment Types and Deployments one for Task Sequences would be helpful. This would allow other SCCM Console users easily identify Apps used within Task Sequences.

Scenario :
I have an application that is deployed to all computers in my environment. The live version of that application is 1.2
I then want to be able to create a new version (1.3) of THAT same application and only deploy those changes to a certain set of testcomputers.
When all testing is done I want to change the "LIVE" version of the application to 1.3 and this will automatically deploy version 1.3 to all my computers.