How is this still a problem? Ask any MVP and they all agree: the built-in task sequence for patching during OSD doesn't work. It doesn't survive double reboots, it has a upper patch limit before it crashes ... it's basically garbage. I don't mind making golden images in MDT, but I shouldn't _have_ to ... and yet I do. I makes SCCM feel less like a singular solution.

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

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.

There should be a few built in maintenance tasks to go through and complete all the maintenance tasks that are needed for WSUS. I find having to run through these steps every month to be quite tedious requiring a lot of change control each month to get the maintenance work completed for WSUS.

Everything described in this article should be automatically done by CM: https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/

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

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.

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.

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.

Right now, if I need to run a PS script in a Task Sequence requires to use the Run Command Line item using PowerShell.exe. However, if I want to run a script with parameters, then I must use the -command option for PowerShell.exe, which has some odd parsing problems that can cause scripts to fail when run this way.

Currently the Asset Details window in the Deployment Status screen is a good overview of what is going on with any given deployment. However, many times assets in the Error or Unknown tabs require additional steps from us. I'd like to propose that the ability to copy information from the Asset Details window (much like Ctrl+C on a collection) is added to the Configuration Manager console.

This would allow us to automate many actions with scripts and provide quick reports without having to write custom queries

Add Option to View TS, instead of "edit". Often times I just want to look at a TS for reference, and not edit it. Just safe guarding the TS from my accidental clicks.

The "More Details" right-click function in the Asset Details view under each monitored deployment currently does not allow you to highlight and copy any of the text. This might sometimes be handy while sending deployment information to colleagues or building hand-made lists of computers with a specific error status, etc.

In the a Task Sequence you have the option to 'Run PowerShell Script' where you have to specify a package \ script name etc. Could we have 'Run PowerShell Command' this saves having to download the script and run it. For example at the moment I 'Run Command Line' and use 'powershell -command start-sleep 300'. It would be great if we could just run native powershell commands.

In our OSD image we utilize the _SMSTSLastActionRetCode for error capturing. This helps us identify in the log where the image is specifically failing, but it doesn't provide very much value to the technician performing the image.

It would be nice if there was an additional variable of _SMSTSLastActionName, which passes the task sequence steps name instead of the return code. This would allow us to display a prompt with the action that failed in addition to the failure code.