Right now there is no way to distinguish between flavors of Windows 10 when configuring OS-based Application requirements. Please split it up into different OS flavors such as 1507, 1511, 1607, 1703...etc.

When deploying Office 365 via SCCM, the client downloads the entire package to its local drive, then streams the installation from the downloaded source. In our organisation we have one master source including all languages (~8GB) and the client streams only the languages it requires (as specified in the configuration.xml), SCCM should allow the clients to stream the installation directly from the Distribution Points and therefore only download the languages they need, not the entire 8GB source.

Split this item from a bigger umbrella item.
This is to allow the changing of the default icons for all task sequences, or all package / programs in software center.

Allow the option of changing the client cache size on a per application basis.
Large applications can then be installed and if set to not persist in client cache, the cache is then resized to the global site default

Add Column in Package\Program\Deployments Tab to show assigned date and time, in order of time newest to latest if multiple schedules are shown.

Currently under the Role Base Access, if you have full control to an application, and wish to add SuperSedence to an application the User only has read access to, you are unable to do that. The ability to do this is currently available when adding a dependency on an existing app the user only has read rights to.

It would be great if an supersedence could be created for programs not deployed via SCCM (or previously deployed via packages). I find myself creating "dummy" applications just for a detection, so that we can automatically upgrade applications that are "Available". In other words, often times we don't care that you installed a specific program, but we do care that if it is installed it's up to date. Maybe when selecting the Application and Deployment type to supersede an additional option to supersede base on a detection rule set could be added?

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!

It would be nice if an Software Package is required in the Future to set a specific Time when a Software CAN be automatically installed ! E.g. : Deployment availability: NOW
Requirement Date of a Software Install: 5 Weeks
Recommended Date of a Software Install: 2 Weeks

If a Client Shutdown after the Date of Recommend Date of Software Deployment is reached SCCM have to install the Application/Update.

Lot of Customers doesn't like to reboot the PC if there is an important security issue or Preparing for a new Software Upgrade.

Allow us to choose where to publish applications for the users. Alot of applications are still installed in Task sequences and it would be great to be able to deploy these and present them in the application catalog.

The users are getting confused when some applications are in software center and some in application catalog. Please let us have a one stop shop for this.

When creating a file detection type, it would be lovely if it were possible to use a standard file type dialog as opposed to the current dialog.

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.

Current behavior is that application icons need to be specified in Application Properties. Wouldn't it be great to pull the app icon from the app content if it is available? This would save a lot of time for environments where application icons are a requirement.

Get-CMApplication shows me a PackageID for my applications. In the SCCM Console in the application item view it is not selectable.

We can turn off software updates, hw inventory, sw inventory, and even the ability to remote control with the client, but there isn't a way to easily disable software deployments (application and packages). In healthcare, we have machines that we cannot patch so we turn off the update component as an added layer of protection. We also have systems we do not want software deployed to as well and there are ways to try and prevent targeting, just turning off that component on the client would be much easier with a client setting option.

If you have e.g. Oracle as dependency set for ~50 applications and a new version is available, you have to manually update all 50 deployment types with this new dependency version.

If you only supersede it, the main applications which are using this as a dependency do not show up in softwarecenter anymore.

There must be a possibility to have an overview of dependent applications and update all of them with one click or exclude some for certain reasons.