Include the Right Click tools adon as part of the Console install, not as a seperate download addon

Split this item from a bigger umbrella item.
This is to specify an icon per App Task Sequence in the Software Center.

At wizard completion for anything, show the Powershell cmdlet equivalent like in other System Center products.

The reboot settings only allow for the user to postpone a reboot for up to 24 hours. Why can't we expand that time or just keep reminding them forever until they reboot themselves? The longer that they have been pending a reboot, remind (pester) them more frequently. Or auto reboot if nobody is logged on.

It is possible to "Install Application" in a Tasksequence. It would be nice to be able to "Uninstall Application" too.

Not really easy to create some SCCM report or Dashboard if your're not a SQL DBA .. even with Report Builder.
Could be awesome to have a new tool where Reports or Dashbaord could be created easily whithout searching which SQL views I need ..ect ... Like some others concurrent application give.

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.

Allow for dynamically selecting Apply Driver Packages, pretty much like it works for normal packages (applications). This would reduce the number of hardcoded Apply Driver Package in the task sequence.

When deploying a device using Autopilot, the Enrollment Status Page (ESP) is used to prevent access to the desktop until the device provisioning tasks are complete. But ConfigMgr doesn't integrate with the ESP, so there's no way to wait for packages, apps, or task sequences - the user doesn't know when the process is done. Add that integration.

Internet based remote control with options such as file transfer and reboot. This could be accomplished using a reverse connection from a client to a new site role hosted in the DMZ.

Provide Support 802.1x Natively w/o the use of prestart up scripts in WinPE. Many large organizations have protected network infrastructure for their environments that want to be able to easily utilizes the Deployment feature on these protected networks.

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

Currently, when servicing stack updates and regular updates are deployed in the same software update group, the patches do not apply in a determinant order. This leads to cases where a cumulative update that requires a new servicing stack is installed before the servicing stack itself.

While this can be worked around by separately deploying the servicing stack update before updates that require said servicing stack, it would be much more convenient if the update installation process checked if there are any servicing stack updates to be deployed and automatically installed them first

Currently Administrators have the ability to set Role Based Access to Collections but we do not have the ability to block access to specific folders. Currently in my environment we have many different departmental administrators who need to manage only their machines and their collections. each time we add collections we then need to grant them access. if the Role Based Administration gave the ability to grant access on the folder level it would reduce the complexity for area's that have a setup similar to mine.

I have attached a screenshot of how my setup looks.

Downloading the boot image with TFTP is slow and download may fail within slow or unreliable networks.
Downloading with HTTP or iSCSI will increase the speed dramatically and the stability is improved also.
With iPXE this technology is implemented and works fine.
My idea is to implement the HTTP download with SCCM.
This would be a great enhancement to performance and stability in the OS deployment.

Implement native cluster aware patching with SCCM to support cluster aware updating.

With a standalone WSUS-Server deployed Windows Updates can be uninstalled/removed from clients. With SCCM SUP this is not possible,
Implement a function to remove installed Windows Updates from clients.

Introduce ConfigMgr Web Console and remove the need to update the console on every device with each SCCM CB Upgrade as local admin rights are needed to update the console.

The ConfigMgr Web Console might be similar to Azure Portal with Microsoft Intune.

With SCCM CB updates getting released more frequently than before, this will provide benefits and ease of management. The Admins can connect to the ConfigMgr console from any computer in the organisation without the need to install it.