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.

I'd like to see the option of logging off the user and performing a Package install and having a "Maintenance being performed" type of screen showing with no ability to logon to shutdown. This could be similar to when software is being installed on an Endpoint in write mode and would be used for critical installs or when you need the user OUT of the application you are upgrading/installing.

We are testing the ability to add a Win 10 upgrade to the Application Catalog with success.

We are able to successfully publish the Win 10 upgrade as a standard Package and simply run Setup.Exe. This has worked and we have successfully updated systems in our Lab from Win 7 to Win 10 with this method. The user clicks "Install" from the App Cat and they are presented with the standard Win 10 setup screens.

We want to offer this as an option to our Engineers and Application developers that want to jump on to Win 10 for testing on their lab workstations independently from a mass rollout of Win 10.

If we had the ability to publish this as a Task Seq. then we could create a much better build, and not just upgrade, but then drop all of the apps down POST build with the Task Sequences that we are creating for an official Win 10 Deployment.

We are testing the ability to add a Win 10 upgrade to the Application Catalog with success.

We are able to successfully publish the Win 10 upgrade as a standard Package and simply run Setup.Exe. This has worked and we have successfully updated systems in our Lab from Win 7 to Win 10 with this method. The user clicks "Install" from the App Cat and they are presented with the standard Win 10 setup screens.

We want to offer this as an option to our Engineers and Application developers that want to jump on to Win 10 for testing on…

When running replica MP's policy is available on the replica MP's DB and Software Center is available and applications are able to installed even if the site server and DB is down. Great for device targeted deployments.

However for user centric deployments that are available via the App Catalog, the users ability to install these is none existent since when the site database is down the App Catalog cannot load as it tries to connect to it and fails.

It might be handy if the database elements that are needed to load the App Catalog are replicated over to the replicated DB's on the replica MP's and if the administrator is able to change from the site DB to a replica DB to keep the functionality of the App Catalog available during an outage.

Or even, if App Catalogs are offloaded from the site server then during their install the administrator is given the option to use a replica DB rather than the site database so no switching is needed during a site DB outage.

When running replica MP's policy is available on the replica MP's DB and Software Center is available and applications are able to installed even if the site server and DB is down. Great for device targeted deployments.

However for user centric deployments that are available via the App Catalog, the users ability to install these is none existent since when the site database is down the App Catalog cannot load as it tries to connect to it and fails.

This is to avoid user install the wrong OS platforms applications and unnecessary error pop up which give wrong impression to end user and increase support costs. It should only shown up whatever is applicable similar like software center / Run Advertised Program (RAP).

Currently, in order to allow an application to have interaction, you need to select the option to install "Only when a user is logged on". It would be better if it allowed interaction if the user is logged on, but install without interaction if NO user is logged on. When running an MSI with /qb, you want interaction because the installer may need to prompt the user to close an application. However, if no user is logged on then it doesn't matter and interaction is not necessary.

With the application model we are no longer able to change the availability schedule or deadline after the application is created - or even expire it. The only way to stop a required application is to delete it, which purges the reporting data. We would like to see this changed so you are able change the deadline/avail time/or if the deployment is required or available.

Instead of creating a Custom Condition of an Application's Existence on specific machines before deploying an app, we could have a drop down that contains the list of already created applications in CM and select the existence or non existence of an application before deployment of said application. Constantly creating Global Conditions is a little strange to me. Thanks.

I would like to see all the policies and deployment listed when i search for single machine, I see this in Altiris for example if i search for "pc-abcd" i should be able to tell how many applications are pushed to the machine or user.

Asset Intelligente and Applikation Management should to Married.
Is it possible to Combine an Applikation with an Asset int. Information so we can get real license Information? and push the cycle on Client to send all Information ( cycle fort Asset Information)

If a plug in is needed for a webpage and it is not installed on the machine redirect the user to the Application Catalog instead of the vendor site. For example, user needs Flash, the page prompts the user to install Flash and directs them to the App Catalog. Do not know if this it technically possible but would be neat. Especially if it worked with all browsers.

Required deployments of SWUpdates gets downloaded to clients ASAP, but required applications wait for the deadline to hit before downloading the content.
I would like the required application deployment to have the same option to pre-download ahead of the deadline. That way we can be positive the installation start at that time.

Office 365 Client Installation deployment features in 1806 appear to be incomplete and problematic. Uninstall statements are not filled in for one. Application Catalog tab is not filled out either. For some reason, creating deployment sources using the new OCT link integration creates sources which are missing files and generates a 30821-1505 error. Running the setup.exe directly from the source also behaves the same. Running ODT manually appears to work, and the source can be imported into SCCM as it was in prior releases.