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.

Downloading the boot image with TFTP is slow and download may fail within slow or unreliable networks.
Downloading with HTTP or iSCSI will increase the speed dramatically and the stability is improved also.
With iPXE this technology is implemented and works fine.
My idea is to implement the HTTP download with SCCM.
This would be a great enhancement to performance and stability in the OS deployment.

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.

Support SUP/ESD/WSUS/update-based packages via the "Upgrade Operating System" task sequence step so that task sequence-driven upgrades can benefit from the smaller size of the ESD files (2.5GB) compared to the full media used today (3.5GB).

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.

With a standalone WSUS-Server deployed Windows Updates can be uninstalled/removed from clients. With SCCM SUP this is not possible,
Implement a function to remove installed Windows Updates from clients.

Enabling MDM management of IOS devices on premise

With the new 'cumulative updates' model I think it would be a good idea to change the maximum run time of cumulative updates to 30 minutes (or whatever is best suited). I have noticed more timeout issues with patching in the last couple of months due to the default 10 minutes not being enough time to install 'X' patches as a single CU. This would be preferred to manually overriding them every month.

It's time to retire the fat console. Updating wouldn't be a problem if everyone just hit a website. Preferably an HTML5 based website that handled high latency fine for those CAS scenarios where the CAS may be half-way across the globe.

It would be really great if when configuring an Automated Deployment Rule you could configure it to run based on the number of days / weeks since "patch Tuesday" (especially in countries other than the USA where "patch Tuesday" is actually a Wednesday and not necessarily the second Wednesday of each month). I currently get around this by having a script detect when patch Tuesday has passed and subsequently execute an ADR and create one or more deployments based on the number of weeks since that date. This works fine, but an in product solution would be better

Enable support for Android management on premise

Many places like to give users custom UIs when an application is being installed. It would be nice to be able to prompt the user for input or give them information without losing the ability to add that application to a task sequence.

It is possible to "Install Application" in a Tasksequence. It would be nice to be able to "Uninstall Application" too.

Configuration Manager should be able to configure all aspects of a workstation that can be done using other Microsoft tools. Some group policy items already exist such as folder redirection and Firewall Policies. It would be great if Firewall could be expanded to include creation of firewall exceptions. It would also be great if we could configure all group policies from within SCCM perhaps using compliance settings.

Instead of having us integrate MDT, why not just include the scripts in a new SCCM install by default?

Allow custom icons for Task Sequences and Packages/Programs in Software Center.

Currently the icons are all a default icon, which can be confusing for end users if there are multiple deployed to a workstation.

I know Windows 10 is bringing much better support of HiDPI, but I don't believe the console is taking advantage of those enhancements.

Most of the console renders OK on HiPDI screens, but there are many windows that are simply unusable due to improper support of scaling. The examples I've attached are from a 4K monitor at 150% (which is the default for Windows). This issue also occurs on HiPDI screens on laptops like the Dell XPS 13.

Enable easier integration with partner products or have the ability to pull down 3rd party catalogs.