Please add the Availability to use get-cmdevice -Devicename with the FQDN and not only with the Hostname (as it is possible with get-cmdeviceVariable)

Add an option to scripts to be able to define a package source so that you can access additional files from your script without needing to point to a network location. Not everything fits neatly into a single script and sometimes you need additional files for modules, config files, etc. This could work similar to the "Run Command Line" task sequence step.

Yes I know you can just use a package for these, but packages are so 2007. Besides, we all want speed!

Can a PS commandlet be updated to show the "Scheduled Update Status" column from the GUI. Currently when applying patches to OS image only the GUI shows the status of the update progress.
Would be very useful to poll for this via PShell so it could be added to automation scripts.

For Upgrade there's a PS cmdlet but for Site Recovery there's none. Neither a wmi method nor a sql sp afaik.
Please enable automation of Site recovery especially since for secondaries that is the supported way to deploy a hotfix.

Add a vendor parameter to Get-CMSoftwareUpdate

This will help identify updates from specific vendors that have been provided through Third-party Software Update Catalogues.

The current commands New-CMAutoDeploymentRuleDeployment & Set-AutoDeploymentRuleDeployment are missing the ability to enable "If software updates are not available on distribution points in current, neighbor or site boundary groups, download content from Microsoft Updates.

This parameter is available in the command New-CMSoftwareUpdateAutoDeploymentRule. It would make sense for the other 2 commands to be able to use it.

Currently, Get-CMPackage only returns “ordinary packages”, not software update packages or task sequence packages or other types. If you run the command in verbose mode, you can see the WQL query filters PackageType=0 and activity <>3.

Documentation for this cmdlet states “Get-CMPackage returns all packages” and this is wrong. It returns all packages where type = 0. Can we please create PackageType as a parameter so all packages can be managed with one cmdlet?

The sccm powershell cmdlets do not currently support the ability to add repair command to a app model deployment type. You have to deserialize the SDMPackageXML to be able to do this via automation. All of our apps are created via script and this capability would be much appreciated.

Actually, it is possible to create a collection with a cmdlet. But we cannot create it in a specific location. We need moving it after creating the collection. Why not just add a parameter to the New-CMDeviceCollection cmdlet?

Now that optimization of the WIM and removal of superseded updates is available as an option for offline servicing in the console, it would be great if this option could be added as a switch to the New-CMOperatingSystemImageUpdateSchedule cmdlet. I use this cmdlet to automate scheduling of updates in an ADG against all my WIMs so it would be great if I could shrink them down at the same time without needing to do this in the console.

I'd like the ability to add a description for the Script I'm adding into "Run Scripts". Right now I try to make the names descriptive, but would like to go into further details about what parameters they can use, what's going to happen, etc.

It would be nice to be able to control the file name generated by Invoke-CMReport when using parameter -OutputFormat.

Run Script: Define # of concurrent jobs (optional)

It would be nice if, optionally, we could limit the number of machines the script is being executed on simultaneously.

For instance, I created a script that is collecting some local logs and pushing them back to a network location.
I do not want it to run on 1000+ servers simultaneously so if I could define the maximum number of servers the script should be run from concurrently, that would be nice.

Provide ability to rename scripts. We'd like ability to differentiate between test and production scripts or rename if the functionality changes. Or, just have the ability to fix typos without recreating the script/approvals.

Currently the script seem to sort by 'Type' or 'Approval State' and I have to choose 'Name' every time I go in to scripts.

Create a powershell cmdlet to perform a DP reassignment as we can do on SCCM console

allow setting "delay enforcement of this deployment according to user preferences, up to the grace period defined in client settings" check box via New-CMSoftwareUpdateAutoDeploymentRule