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.

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.

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.

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.

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.

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.

Cluster patching feature was added in #SCCM CB 1602, but has been in prelease for a long time. It needs to:
1) Have improved/revamped UI
2) Remove dependency on collections
3) Orchestrate patching for any machines, not just servers/clusters
4) Remove the feature from prerelease

Would be nice to be able to advertise Task Sequences to specific users or groups. We have some operating system deployments that we would like only certain users to run, support staff for instance.

Add an column to the devices view that would display Active Directory descriptions in console.

For MBAM clients I want to use preprovisioned bitlocker volumes.
A requirement is to use the AES256 encryption mode.The pre provision bitlocker step defaults to aes128, and cannot be changed in the step itself.
I now have a extra step before the preprovision bitlocker step with this command:
cmd /c reg.exe add HKLM\SOFTWARE\Policies\Microsoft\FVE /v EncryptionMethod /t REG_DWORD /d 4 /f

Thanks to this website:
https://blog.alschneiter.com/2017/05/03/change-bitlocker-drive-encryption-to-xts-aes-256-during-osd-with-configmgr/

When I go to the Windows 10 Servicing Dashboard, I got a nice PieChart of the Windows 10 Clients and their Version.
But when I click on the PieChart, nothing happens. It would be great to have the same experience on this Dashboard like on the SCEP Dashboards.
That means, if I click on the PieChart one of the Windows 10 Version, a new collection would be opened, with the corresponding Devices.

At the moment it is not easy to add requirements to an application deploymenttype with PowerShell. I think many of us would benefit if this would be simplified.

Many organizations create their own front-ends for ConfigMgr Task Sequences (or leverage popular third-party ones like OSD++, Pretty Good Front End, etc.). However, these only are able to be used when the task sequence is in WinPE.

Please add the serviceui.exe functionality into the default task sequence environment so it is possible to display Light Touch prompts when starting the task sequence from an existing operating system. Including serviceui.exe would be enough, or the functionality to launch interactive UI could be added to the environment natively.

Make the log files directly accessible via the console rather than digging around in the file system trying to remember which file holds which logs and ideally make them accessible from a context menu in the relevant areas.

New-CMDuplicateHardwareIdentifier
Set-CMDuplicateHardwareIdentifier
Remove-CMDuplicateHardwareIdentifier

Please create cmdlets to add/edit/remove duplicate hardware identifiers. We have a large organization and those pesky Lenovo Yoga's get a USB to Ethernet dongle with each one. We have over 500 dongles currently, and I don't see a way to automate importing those MAC addresses. Thanks!

Preview SCCM versions have a basic WSUS cleanup and maintenance task. It should be evolved and expanded to include SQL index optimization, IIS configuration optimization, and deletes of declined updates.

Have the ability to include/exclude certain OU's from both Active Directory User and System Discovery.

E.G. I might have an "All Users and Groups" OU at the root domain level, which may contain sub OU's containing service accounts or mailbox accounts etc. that I don't want being picked up by discovery. The ability to pick which sub OU's to discover/not discover would be really handy in this scenario. The same applies for system/computer discovery also.