DEP enrollment Profiles "Set as default "
Please add the feature "Set as default" in SCCM DEP Enrollment Profiles so that we don't need to do this manual for the DEP sync devices.
It is in Intune standalone - we just need the same feature in SCCM.

It's possible to create a new node in the console with favorite actions.

Example:
Favorite\Frequent Action 1 (Device collection)
Favorite\Frequent Action 2 (Monitoring content)
Favorite\Frequent Action 3 (Application Deployment)

If you want to add any action in the console to favorite Node, just right click on the action and select add to favorite actions...

In this wau

Currently it appears that when the SCCM agent in the WinPE boot image connects to a Management Point, it selects one without using the Boundary Group rules, instead selecting one from the AD published list, starting with the first alphabetically.
Instead this should behave like the full blown Windows SCCM Client and select a Management Point based on Boundary Groups such as IP range.
It is worth noting that Distribution Points are selected correctly according to Boundary Group by the WinPE client, for OSD content.

Even thought Applications are state based there are still use cases when a deployment could be expired so that no future deployments of that application will occur. Either an expiration or the use of automatically disabling the deployment, since Software Updates could be disabled so should Software Application Deployments. The reason to keep the deployment would be for reporting so a way to disable or expire would be ideal if state based is not needed.

The sms_applicationassignment WMI class exposes an ExpirationTime property which actually removes deployments from App Catalog but it does not work with software center.

We have a few Software Updates that we just don't deploy. Every month, our list of "Needed, but not deployed" updates show these updates (for example, IE10). I want a way of filtering these out so we don't accidentally deploy them.

I tried doing a search by adding the article IDs, but this doesn't work (as the attached screenshot shows).

Maybe allow us to add a custom category for individual updates (such as "Do not deploy"), so we can then include these in our search.

When creating custom discovery data using the smsresgen class there is no way to remove this from the discovery related tables in ConfigMgr. Since there is a supported way to add this data, there should be a supported way to remove it. This is necessary as a rollback option, to return ConfigMgr to its default state, before the custom discovery data was added.

Make clients Calls like Ping / MSTAC witrh FQDN and not with Netbios. We have different AD connected to the SCCM . We can not use the build in features like Ping the clients or open RDP as the console only tries the netbios name and not the fqdn. It would be great to have all cleints call done trought FQDN

We have the possibility to select to "Access content directly from the DP" when deploying a operating System image in a Task Sequence. It would be great to be able to do this for "Run Command Lines" as well.
Example scenario, you want to run a Powershell script from a package before the disk is formatted in a scenario where we use Bitlocker for instance.

App Model - Optional User Deployment - When user policy is recieved, perform app eval to check if app is installed, if so show as installed in Software Center. (Currently it doesn't evaluate and shows option to install even if already present. When you click the install button... it then performs the evaluation and changes to installed and provides the uninstall button. This is confusing to our end users)

Sometimes it might be handy to remove a computer from the OSD collection as a final step during the task sequence. Or additionally add the computer to additional collection(s) for for example extra software deployment or another task sequence.
Now scripts need to be created therefore and in my experience this doesn't always work well.
A predefined step where the collectionname or collectionID needs to be added to add (or remove) the computer to (or from) would be much appreciated.

New-CMDuplicateHardwareIdentifier
Set-CMDuplicateHardwareIdentifier
Remove-CMDuplicateHardwareIdentifier

Please create cmdlets to add/edit/remove duplicate hardware identifiers. We have a large organization and those pesky Lenovo Yoga's get a USB to Ethernet dongle with each one. We have over 500 dongles currently, and I don't see a way to automate importing those MAC addresses. Thanks!

Provide Mac Provisioning with CM12.

Other vendors provide the ability to image and fully manage the Mac device, when will Configuration Manager provide this feature? Imaging Windows platforms is only part of a corporation desktop landscape, we also support Mac, having a single solution would make logical sense.

In our enterprise we have quite a few locations where 802.1X is impelemented, e.g. networks port-based network access control and/or VLANs. Some locations even use DHCP snooping.

We would like to implement SCCMs wake-up proxy feature in these locations but it is not currently supported. Also, network administrators are concerned about the IP-to-MAC mapping (MAC flapping) feature used in wake-up proxy.

Please provide us with wake-up proxy support that will work on any type of network.

Allow Remote Control by right-clicking a username so that the user doesn't have to look up the computer name.

This would be enormously helpful in the Education sector where users are constantly moving between PCs. Novell had this feature in ConsoleOne and it enabled superfast remote control of users for our Helpdesk staff.

When creating the Configuration Item (Create Configuration Item Wizard, Settings step) and choosing Registry setting type for the Create Setting window, there are some bizarre registry types mentioned in Data type drop-down box: String, Integer, Date and Time, Floating Point, Version and String Array. Most of these data types are all REG_SZ type. But where is REG_MULTI_SZ? REG_EXPAND_SZ? REG_DWORD? REG_QWORD? REG_BINARY?
There is also possibility to set/check compliance for those registry settings with script, but why the Registry Configuration Item in first place?
These actual registry data types need to be implemented instead of/additionally to currently existing ones.

Currently, the maximum an administrator can give users to reboot their systems is 1440 minutes (24 hours). Please let us specify up to 7 days. The goal of the delay is to allow a reasonable amount of time for an end user to save their work and reboot without losing anything. The 24 hour limit means that if a user is gone for a day, there is a strong chance they could lose their work. Allowing up to 7 days seems like a better compromise between end user control and respecting admin intent/organizational need.

When running a task sequence to deploy a 1703 based image, the second part of the task sequence: "Setup Operating System" does not display.

The screen saying "Just a moment..." is displayed instead of the SCCM task sequence screen, meaning you cannot see the progress.

If the machine is left, it does actually complete the steps, but it would be nice to see the SCCM screen once again!