Integrate the SCUP tool on to SCCM Admin Console. This will give a single pane of glass view for all patching activities (including importing 3rd party patches).

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.

I would like to see the ability to launch one task sequence from within another task sequence. For some processes, you run the same steps across multiple deployments. Today, you have to duplicate these steps across many task sequences. The ability to execute a task sequence from a task sequence would alleviate this need and reduce errors and inconsistencies for administrators.

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

In Windows client, after receiving software updates from the SUP, I want you to be able to use the" install and reboot / shutdown and update" botton.

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

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.

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.

When the end user has multiple monitors, the view is scaled. This is really frustrating sometimes: you have the choice between a blurry view or scrolling a lot...

Sure it's possible to detect multiple monitors and being able to switch between them with buttons (like Team Viewer) would be awesome!

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 the built in use of WOL, and right click to wake up a machine or a collection at anytime. Also fix ConfigMgr's native WOL technology to work on common network infrastructure (no Mac-Flapping.)

Many customers want to be able to force a reinstallation of an application. this deployment should ignore all detection rules and just install the application again.
At the moment this is not possible.

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.

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

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.

Enable an option to quickly see the primary user of a device (within the columns on the console) I don't have time to individually click machines or run reports to find the primary user.

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.