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.

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.

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.

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.

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

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.

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.

Please add functionality to use the clipboard in the Device -> Resource Explorer tool.
This would enable us to quickly grab some information for one of the systems, like copy a MAC-address or MSI install code.
At the moment, we either have to export the whole table to .txt and filter using a text-editor or manually write out the information which is error-prone.

Functionality should look like:
- Double click in a field in the table.
- Press Ctrl-C to copy to clipboard.

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!

I would like to add setting of LayeredDriver (106/109 key, etc.) during OSD (OS deployment).
These settings are "very important topics" for OSD guys in Japan and Korea.
Without this setting, the keyboard will become an English keyboard.

LayeredDriver [Microsoft Docs]
https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-international-core-winpe-layereddriver

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.

With 1902 we introduced the Community Hub to the current branch release. Even it's a great feature, some users shouldn't be able to see it. It would be nice if we could use RBAC or a site setting do hide it from consoles.

I would like more space in the OSD Task Sequence description field (and possibly even include a link) so that we can adequately tell people what's required before and after running the Task Sequence and to tell them where to find help.

At the moment, we only have 2-3 lines of text available.

Perhaps replicate what's currently available in the application model with the Localised description on the Application catalog tab.

At the moment there is no quick way to see which particular machines require an update. You can run a report from Monitoring, but that means identifying the update then going back to reports and running the appropriate report.

You can however see the the number of devices that require an update when looking at that particular update. A simple "More Details" button here would be useful which would show the machines that require the update or are compliant etc, without needing to run a report.

This applies to both Software Updates and Windows 10 Updates for feature updates.