A truly great feature would be to be able to customize all dialogs show to the end-user, both for OSD, but also reboot prompts basically all dialogs shown to the end-user.
Adding a company logo so that the end-user actually knows it is from our company and trustworthy.

SCCM only supports up to version 6, latest hardware uses version 10.
SCCM provisioning uses SOAP which was deprecated by Intel.
This is now a big hassle for people who want to use Intel Vpro in combination with SCCM. We need to make use of an Intel Add-on (Intel SCS) to get things working but it’s far from ideal.
Please bring back the provisioning support compatible with the latest versions of Vpro and bring support for new features such as KVM.

When sorting by Compliance % for some reason the sort is done as a string sort so 80% is a bigger number than 100%.

Please add the ability in discoveries to:
- exclude OU's
- exclude Virtual Cluster resource

A function to instruct a distribution point to clean-up/rebuild its content library would be great. This would be particularly useful to fix the "package list in content library doesn't match the one in WMI" errors.

We have 260+ DPs, all members of the same Distribution Group, and 35% of them have mis-matched content library sizes. So obviously content clean-up does not succeed. A way to force them to re-evaluate (without redistributing existing content) would be great.

Please don't forget about those of us who work in an environment where we can't connect to the Internet. I've been very concerned by Microsoft's cloud-first effort turning into cloud-ONLY effort.

Now that we have the option to define both Distribution Points and Management Points as preferred, it'd be terrific if we could have the same option for Software Update Points. It would make a strong case when designing a flat hierarchy.

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.

Ability to change an approval requests that has already been approved to denied.

We would like to see a single web portal, preferably HTML-based, to marry the Software Center and Application Catalog. We deploy both types of offerings, and a single place for users to get new software would be great.

Currently if we add a new machine to sccm, and the OEM was lazy and reused a UUID builds won't start, and there seems to be no easy way aside from standalone build media to get around this.
since we have to provide a uuid and mac address when we create new machines, why is it not smart enough to use the mac with the generic uuid to identify the correct machine?

Add a retry count and delay between retry properties to at least the most critical task sequence steps, if not all, so that we can make task sequences more resilient when there are hiccups to servers or network.

Would be nice if the application approval request feature had built-in support for emailing.

Allow the groups in a Task Sequence to be collapsed allowing a better overall view.

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.

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.

Everyone who knows WSUS misses the feature in ConfigMgr to allow the installation of software updates when the machine is shut down. This is being requested for a very long time now. For most businesses it's not the best approach to install updates only when a user is logged on. Of course the scenario changes with Windows 8 and 10, but it's still a valuable addition to the option a ConfigMgr admin should have.