As of right now, Client Settings are configurable during the installation of the client via command-line or via the client-side interface. I believe it would be beneficial to allow this setting to be configured via Client Settings as one organization could have a variety of different use-cases for creating disparate client cache baselines.

SCEP policies do not have the ability to set security scopes. This is a problem because our SCCM is shared by several departments and colleges in the university. For example, someone may inadvertently (or intentionally) modify a policy for DCs which can have a catastrophic effects. Having the ability to set security scopes will restrict who has access to individual SCEP policies.

We should be able to deploy SCCM Gateway servers for deployment to DMZ, Internet and Remote locations where opening ports to the management servers / domains are not feasible. We are unable to forward ports from the internet to our LAN and must use a DMZ. There is no way to implement SCCM for IBCM because of this.

Add a button in Software Center so the user can update the MAchine and User Policy. Would be a great feature for the end-user when waiting for an application to be available!

It would be great if SCCM On Premise MDM would support Windows 10 Devices for scenarios such as settings, required application deployment, wipe and retire.

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.

For each computer under "Devices", display different icons depending on whether a user is logged on or not, or whether the computer is powered on or not (see attached as an example of what this function looks like in Altiris Deployment Console). Such feature instantly allows admins to see which computers are available/online/offline, without having to run a report or ping the computer

Task sequences are only officially supported in operating system deployment scenarios. Task sequences are incredibly useful with their explicit logic and tight control. There's many cases where it can be useful to deploy task sequences outside of operating system deployment scenarios for complex software deployment scenarios.

Task sequences should be made a first class citizen outside of operating system deployment scenarios.

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.