I'd like to see a "Description" parameter added to the Get/Set/Add CMDistributionPoint cmdlets so descriptions can be programatically added w/o having to try this through separate WMI cmdlets.

Add the possibility to set an operating system requirement on program for legacy package. The cmdlet set-cmprogram has no switch for that.

Make it possible to assign multiple DP's to a boundary group with the ability assign an order in which they are accessed by clients. ATM if there are multiple DP's per boundary group and all are defined as fast (or slow), the DP is chosen randomly. At the very least a DP that resides in the same subnet with the client, should always take precedence,

When a user installs updates from Software Center only the updates that were selected to be installed are evaluated for their state post reboot. The whole deployment those updates were in, even if all updates in the deployment were selected, will not be queried for compliance post reboot. This causes a delay in the deployment compliance reporting as you need to wait for the deployment to be evaluated on schedule. In some instances this could be days. Running evaluation on the deployments those selected updates were in post reboot would solve the reporting delay.

Configuration Manager is a great source of information for organisations. The problem with this repository of data is that it requires someone to take advantage of it. Reports or queries need to be generated by someone who knows what they are doing. Connecting Configuration Manager to PowerBI or providing an OData interface would allow Configuration Manager inventory data to be more easily accessed and used

RBA Viewer from the toolkit no longer opens after the application of CU1 for SCCM 2012 R2 SP1. I show this VERY useful tool to almost every customer of mine as most of them struggle with creation of roles correctly. The viewer crashes with the following message in the debug.

Hi all, my customer is using the PowerShell on a really high level to automate nearly all his ConfigMgr Patchmanagement Tasks. They are using Add-CMSoftwareUpdateToGroup but they're missing the matching Remove Commandlet.

When you uninstall an application and the content for all the deployment types is not in the cache then the entire content will be downloaded again even if this is not required for the uninstallation routine.

The client should be able to determine whether or not it needs to download the content before initiating an uninstallation.

I think it would be great if SCCM could have a configurable value in registry for TFTP windowsize just as it has with TFTP blocksize. Both WDS and bootmgr.exe seem to handle it but there is no easy way to get this option into the generated BCD file upon PXE boot. Seems like a low hanging fruit.

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

Integrate the SCUP tool on to SCCM Admin Console. This will give a single pane of glass view for all patching activities (including importing 3rd party patches).

Being able to edit task sequences with PowerShell would make managing task sequences much easier. Some possible new cmdlets could include:

Add-CMTaskSequenceStep
Get-CMTaskSequenceStep
Remove-CMTaskSequenceStep
Set-CMTaskSequenceStep

Add-CMTaskSequenceGroup
Get-CMTaskSequenceGroup
Remove-CMTaskSequenceGroup
Set-CMTaskSequenceGroup

Client logs for OSD are constantly purged and overwritten. This can make troubleshooting difficult in a standard environment. For example, logs are saved to X:\Windows\Temp during winPE phases. This file system is destroyed upon reboot. Even after the WinPE phases, log files (especially smsts.log) are constantly overwritten.

Please prevent logs from being lost or overwritten during OSD.

Please add the ability to select a primary site or site code when creating stand-alone media from a CAS.

When creating stand-alone media today, it automatically sets the SCCM client to install using the site code of the site that is used to create the media. When using a CAS to create the media, this will cause the client to deploy without a usable site code.

You cannot currently override this behavior through setting installation properties in the Setup Windows and ConfigMgr step.

In Windows client, after receiving software updates from the SUP, I want you to be able to use the" install and reboot / shutdown and update" botton.

It could be great to have a notification (for users I mean) when a new application or a new version of an application is published in the software Catalog.
Underline new version or special icon visible in the catalog.
Little notification through SCCM client.
And what about RSS ?

Still searching for clear guidance on automating updating the Windows Update Agent in an enterprise.

Have an option to set a specific boot image for PXE. In an environment where there are multiple boot images, when a device PXE boots it will first download whichever boot image (that is PXE capable) associated with the most recently deployed task sequence. It would be nice to have an easier way to just set a default or preferred boot image for PXE instead.