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.

As more and more devices are shipping without wired network adapters, and more business areas are going "wireless only," the traditional ability to reimage a device in place is getting scarce. This is especially true in primary and secondary education institutions.

Please provide support for adding Wireless drivers to WinPE, and the ability to provision wireless network profiles for the WinPE phase of the task sequence to enable imaging over wireless network connections.

We hear this request a lot, so I'm adding it here.
ConfigMgr integrates with many Microsoft Cloud Services:
* WUFB
* WSFB
* Windows Upgrade Analytics
* OMS
* etc
For each of the above services, sometimes a company may have multiple tenants. Please allow ConfigMgr to manage multiple tenants for each of these services.

With 1610, the Cloud Management Gateway feature arrived. Although it's a Pre-Release feature, as Cloud Solution Provider we're UNABLE to use/implement this. And so are our customers...!

When you try to set this up from the ConfigMgr console, a prerequisite is the Azure Management Certificate, which can't be configured as CSP-tenant because this needs the Classic Azure Portal (ASM). This is unacceptable for us, as CSP, as we would have to instruct our customers to get an Azure Subscription separately.

https://blogs.msdn.microsoft.com/cie/2016/11/28/azure-management-certificates-and-publishing-setting-file-with-csp-subscriptions/

The new Software Center in 1511 should also categorize Applications using the user category even if it is not deployed to users but systems instead. It should reflect the user category no matter what.

Allow the recurrence pattern for maintenance windows to be scheduled with an offset from a base day.

Meaning, if we want a maintenance window on the Wednesday following the Second Tuesday of every month, we could configure a maintenance window for the Second Tuesday with a +1 offset.

(This would be similar to the offset option added to ADRs in 1802.)

Would be nice to be able to advertise Task Sequences to specific users or groups. We have some operating system deployments that we would like only certain users to run, support staff for instance.

Please update the software distribution troubleshooting flowcharts. https://technet.microsoft.com/en-us/library/bb932214.aspx?f=255&MSPPError=-2147217396.

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.

Change default "sort by" order from "Most recent" to Alphabetic list (Application name A-Z). Or remember the setting for the client. Or allow a SysAdmin setting for site-wide default setting. It always resets back to Most recent.

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).

Currently, when servicing stack updates and regular updates are deployed in the same software update group, the patches do not apply in a determinant order. This leads to cases where a cumulative update that requires a new servicing stack is installed before the servicing stack itself.

While this can be worked around by separately deploying the servicing stack update before updates that require said servicing stack, it would be much more convenient if the update installation process checked if there are any servicing stack updates to be deployed and automatically installed them first

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

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

The ability to exclude a single or multiple updates with a simple Right Click > Exclude or Menu item.

After a user installs an application that was deployed as "Available", but later uninstalls the application, the user gets a balloon pop-up every time they logon saying "New software is available".

There is NO way to prevent this from happening apart from removing the user from the collection where the application was deployed, and adding them back. This has been the case since CM12 was released but this is not a desirable behavior especially when there's no "valid" way of preventing this.

Allow packages to be deployed to multiple collections at one time. For instance I need AppX to go to Lab 1, Lab 2 and Lab4. Instead of going into AppX 3 different times to deploy, it would be nice to deploy it to all 3 labs at one time.