This is a buggy, Would we like the option to have ' Uninstall Application when Resource falls out of scope of this collection' when an application is deployed to a collection, this would save us having to create 2 collections ( install and uninstall) and to deployments. This would save SO much time and reduce the complicity of application management.

Basically would like something similar to the Windows Updates Reboot/Postpone nag prompt except with the ability to customize the notification text as applicable to the deployment.

For example:, as a sub-setting of the deployment type for the application you have the option to enable the reboot/postpone prompt and customize the notification text of the dialog box.

If the user that receives the prompt, postpones they will be re-prompted at the end of the postponement period until they either reboot or shutdown the system. (basically exactly the same behavior as the Windows Updates reboot/postpone prompt).

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

Allow packages to be deployed to multiple collections at one time. For instance I need AppX to go to Lab 1, Lab 2 and Lab4. Instead of going into AppX 3 different times to deploy, it would be nice to deploy it to all 3 labs at one time.

I have to create several very large (10GB and up) software deployments each year and install them for two thirds of the user base. Preferred method of delivery is install directly from the DP rather than download the installation files to C:\windows\ccmcache. It would be nice to do this using the application model so I can make use of the extended feature set it provides over the package model. I have to work around the limitations using convoluted wrapper scripts to get everything working properly.

When you deploy an application with dependencies, you loose the option to uninstall it from software center. It would be nice to be able to uninstall the main app and be able to choose if the dependencies would uninstall or not.

It would be great to have a possibility to create a deployment where the User would be logged off during the installation of Software. Useful for Software like Java Runtime or Adobe Pro where a running application can prevent the installation.
The User should be informed that an installation will be started and he will be logged off. The User should be not able to login during the installation.

It would be extremely helpful if administrators could change the default “Time based on:” option used in Software Deployment from “UTC” to “Client Local Time”. This setting is highly subjective and only companies that are based in multiple time zones AND want software to deploy simultaneously across all time zones want UTC as the default. Forcing the UTC default upon all customers needlessly increases the chance of human error. Allowing administrators to change the default would satisfy all customer’s needs rather than just those that leverage UTC.

Please make the SCCM client's ScriptExecutionTimeout attribute a parameter that can be configured within Client Settings policy. This would be the best way to help address the "In-line script execution time-out... DiscoverApp failed (0x87d00321)

The application detection method only runs in the user context if it is deployed to a user collection. This would be reasonable if the Deployment Type user experience were set to "Install for User" (User context), however the detection method runs in the user context when this is set to "Install for system" installation behavior (SYSTEM context).

Currently, a Global Condition cannot be changed or deleted if it is in use in any existing revision of an application. This makes testing a new global condition or fixing an existing global condition extremely cumbersome, either resulting in many duplicates being created or many revisions of the application being deleted every time the global condition must be changed.

While it is beneficial to make it difficult to break an existing application by preventing the global condition from changing, ultimately, SCCM users need the freedom to determine when it is appropriate to change an existing Global Condition on their own.

I work in a quite big Environment, 30k clients and my network team isn’t that happy when we pull the trigger to update our critical LOB apps due to the fact that every computer downloads the content almost at the same time. That puts a lot of pressure on the network infrastructure.
There for it would be great to be able to preload the clients with content for applications in a slow and steady way before the deadline falls for the application.

Even thought Applications are state based there are still use cases when a deployment could be expired so that no future deployments of that application will occur. Either an expiration or the use of automatically disabling the deployment, since Software Updates could be disabled so should Software Application Deployments. The reason to keep the deployment would be for reporting so a way to disable or expire would be ideal if state based is not needed.

The sms_applicationassignment WMI class exposes an ExpirationTime property which actually removes deployments from App Catalog but it does not work with software center.

We would love the ability to change deployments from Available to Required and Required to Available. Currently we have to remove the entire deployment to switch back and forth, and we loose a lot of reporting data during this process

Application groups can be deployed to a collection but cannot be added in a Task Sequence and then deployed. Please enable the Task Sequence deployment for Application Groups.

Office 365 Installer - Detection Method
When creating an application for Office 365 using the built-in "Office 365 Installer" feature, the application gets created with a default detection method that only uses the version.
So, if you create 3 separate applications (Office, Project, and Visio), or if you create Applications with different languages, they all have the same detection methods.
So, if you install Office first, you can't Visio or Project.
The detection method should include a product and language:

Examples:
SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\VisioProRetail - da-dk
SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ProjectProRetail - da-dk
SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\O365ProPlusRetail - da-dk

Add an additional Maintenance Window type specifically for Application Deployments only. Software Updates and Task sequences have their own and there is an "All Deployments" type. There needs to be one on for Apps to better segregate the nature of the changes occurring in the environment.