Split this item from a bigger umbrella item.
This is to specify an icon per legacy package/program in the Software Center.

Please allow URL links within the text field for localized description. This way you can include a link to contact the helpdesk or a URL for internal documentation. Particularly, the "mailto" and "href" markup.

Please add an option in the Application Model to auto uninstall the application after xx number of days. This could be linked to Software Metering. This would be extremely beneficial to manage applications for license reclamation as well as removing vulnerable applications from the environment.

Phased deployments are great, but we have lots of users, with lots of applications that are nor required, but are superseded.

Say we have 100,000 users, 50'000 have an application installed that has an update. We don't want a required deployment as not everyone has the application, and we don't just want to deploy the update to the application to 50,000 in one go. so this feature would be nice.

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

Provide option to update the license information in Application model. This will help end users to identify the application as license or non-license information in software center.

When making a new application, it would be helpful to have more granularity in the choices for Windows 10 so that we could target particular builds or set a minimum. If I want an application to install on 1809 but not 1803 or older, this would be where I would want to set that.

When you create a few requirements for application I would like to have the opportunity to add a relationship between them ('or', 'and', etc.).

User or support should not need to go to Configuration Manager control panel to run this cycle. I voted for other suggestions to run on forced reboot or logoff. It would also be great to have a user-friendly button in Software Center to run the evaluation.

When setting up a normal (non-phased) deployment, you can schedule a date and time for the deployment to start.

Having the same ability for phased deployments would be very handy!

Once you create a custom requirement, you can then not edit the custom requirement under the Create Deployment Wizard type. We should have an edit button to edit the custom requirement you created.

Make it possible to automatically upgrade an application that is deployed as available immediately (without having to wait for the maintenencewindow to apply.)

This was previously the default behaviour, but is no longer possible? Can this be made an option again?

Same as we have with the application deployment toolkit in powershell.

It will be grate to have a check if application is running before installing.

For ex: We want to update application A.0 . If the application is running user will be asked to close it before installing update A.1 or if not open it will install the update silenty. If the user try to open the application A.0 during the upgrade a pop-up notification will said that the application cannot be open while SCCM is upgrading it.

Wait, wait hear me out. What if you could target a deployment to a single collection and ConfigMgr just thought up random groups of 20-30 machines at a time and made the deployment available to the next group after a specified period of time. Essentially creating an automatically built phases with no real requirements other than "x" amount of time has passed since the previous groups.

For phased deployment, if any application is updated then phased deployment already created for it to be restarted.

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).