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.

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.

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.

The "More Details" right-click function in the Asset Details view under each monitored deployment currently does not allow you to highlight and copy any of the text. This might sometimes be handy while sending deployment information to colleagues or building hand-made lists of computers with a specific error status, etc.

It would be nice to be able to control the client cache size settings using the client settings policies. This way you have a simple way to increase it if you have a package which is larger than the initial deployed size.

At the minute have to completely restart the TS when a dependency is not found. Could we not introduce a retry option once the dependency issue is resolve. Similar to checking for installation pre-req's

better control weather I want a site to fallback to primary or not.
real bandwith limitation instead of current posibility. Control priority of metadata

How is this still a problem? Ask any MVP and they all agree: the built-in task sequence for patching during OSD doesn't work. It doesn't survive double reboots, it has a upper patch limit before it crashes ... it's basically garbage. I don't mind making golden images in MDT, but I shouldn't have to ... and yet I do. I makes SCCM feel less like a singular solution.

Every time you add additional columns to display in the views it is lost when you close/reopen the console.

Be able to have a local Package of a windows app instead of using the deep link feature.

• same as exits for Package/Programs and Apps and Updates!

When defining a Configuration Item with Powershell have the possibility to influence the behavior of the script (eg -noprofile, setting allowed time to run)

Currently, when changing nodes from Application, to Packages to Collection, every time you begin a search, you must re-check the box to 'Search all Sub-nodes'. As the average SCCM admin might make dozens of searches a day to find content, computers, collections, this is really irritating. It would be a better behavior to automatically search all sub-nodes.

When in the properties of an application, package etc on the summary tab there is a hyperlink to content status. It would be a very productive update to take you directly into the status of the object instead of dumping you into the root of content status and having to search for the application etc you were just in.