At wizard completion for anything, show the Powershell cmdlet equivalent like in other System Center products.

At the moment it is not easy to add requirements to an application deploymenttype with PowerShell. I think many of us would benefit if this would be simplified.

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

PowerShell PackageManagement is a unified interface to package management systems and aims to make Software Discovery, Installation and Inventory (SDII) work via a common set of cmdlets (and eventually a set of APIs). Regardless of the installation technology underneath, users can use these common cmdlets to install/uninstall packages, add/remove/query package repositories, and query a system for the software installed.

Providing a dashboard/portal with the ability to manage the NuGet repository underlying the packagemanagement solution would make SCCM more attractive over phasing it out to go towards Chocolatey Enterprise.

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!

Create application from PowerShell from the 'Licence for Store Apps'

Set-CMPackageDeployment and Set-CMSoftwareUpdateDeployment do not allow DeploymentID as unique identifier. Instead you need to use e.g. programname and packageid.

In the case of Set-CMSoftwareUpdateDeployment this requires DeploymentName which is not even possible to retrieve from Get-CMDeployment

Please, allow DeploymentID as an option to identifying the deployment in these cmdlets.

Powershell cmdlet "Remove-CMMaintenanceWindow" should accept StartTime as a parater. Current implementation only accepts limited parmaters of collectionid, and maintenance window name. If you have two windows by the same name, with different start times... you will remove both by using this utility. I suggest it should also accept the StartTime as a paramter for specific window deletion. Maintenance windows are a point in time schedule, and therefore the Point in time should be considered as a parameter for removal. The current implementation of this cmdlet is dangerous, and cannot be used for finite window removal.

Set-CMClientSetting for hardware inventory, add option to add/remove classes as well as enabled/disable attributes to be collected within a class

The ConfigurationManager module does not have any *-folder cmdlets.

I would like to see some created that allow for more folder manipulation within system centre configuration manager, for example Get-CMFolder -Name "Test" would provide me with the Folder ID, Name, Heirarchical Location in ConfigMgr and more!

As well as New-CMFolder, Move-CMFolder, Remove-CMFolder, etc!

I would also like to see the ability to add -Folder to other cmdlets, such as New-CMDeviceCollection -Name "Test" -Folder "TestFolder" so the collection called Test is made in the folder called TestFolder instead of the Device Collections root.

This would make it easier to remove multiple packages with similar names.

the ContentLibraryCleanup tool is great, but can we have a PowerShell version of it to aid with automation of same? thanks !

While setting Computer restart settings in the console requires the notification dialog box display value (for example 1440) must be greater than the countown dialog box value (for example 120), in Powershell it is swapped and the following fails:

Set-CMClientSetting -Name "Default Client Agent Settings" -ComputerRestart -RebootLogoffNotificationFinalWindowMins 1440 -RebootLogoffNotificationCountdownMins 120

This way in Powershell it is not possible to set the correct values except if you swap the parameters:

Set-CMClientSetting -Name "Default Client Agent Settings" -ComputerRestart -RebootLogoffNotificationFinalWindowMins 120 -RebootLogoffNotificationCountdownMins 1440

Create a powershell to configure the alerts on a specific collection. like adding collection to EP dashboard and configure thresholds

add filter to return values based on current status. right now for any automation we need to report thousands of requests and filter them by Where-Object.

Add the certificate used to sign the PowerShell module to trusted publisher during installation. It is cumbersome to script around and the certificate itself should be trusted anyway.

Would be good to have a PowerShell CmdLet to get information on all collections and deployment for a computer is listed for.

Add the Remote Powershell option in the list when you right click on a device and hit Start and it gives you the List of Remote tools. By adding the Remote Powershell option and adding a Policy to configure and allow Remote powershell. This would allow for remote administration of a specific machine without having to use the other less secure methods of sending commands to a specific system.

The folder names are different in the console and the cmdlet Move-CMObject.
Console: Applications
Cmdlet: Application
Since this is a standard folder regardless of site code, the names should be the same.