At wizard completion for anything, show the Powershell cmdlet equivalent like in other System Center products.706 votes
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.62 votesunder review · AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
(correction: this change was too late for 1704, it will be in 1705)
For 1705 TP we have added an initial ability to add detection method clauses to a MSI, Script, or Mac deployment type.
Please try it out and let us know what you think. We don’t have full UI parity yet but this is something we are working toward.
Being able to edit task sequences with PowerShell would make managing task sequences much easier. Some possible new cmdlets could include:
Set-CMTaskSequenceGroup51 votesstarted · AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
The initial work for this is now in 1705. We’re working on a blog post to go more into depth.
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.13 votes
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!12 votes
In 1706, once you create a script and approve it (or deny it) there is no way to alter the script except but to create a new one. Would be great to have the ability to set the script back to waiting for approval, which would unlock the code to be edited.10 votes
Create application from PowerShell from the 'Licence for Store Apps'7 votes
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.7 votes
Allow use if DeploymentID as identifier in Set-CMPackageDeployment and Set-CMSoftwareUpdateDeployment
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.6 votes
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.5 votes
Set-CMClientSetting for hardware inventory, add option to add/remove classes as well as enabled/disable attributes to be collected within a class5 votes
When using the "Run Script" against a collection allow the script to accept parameters.4 votes
This capability is in 1706 tech preview.
In 1602 support in the Admin Console GUI was added for additional client notification triggers.
However there is still a gap in the functionality for this cmdlet. Currently as of 1706 you are still only able to invoke user and machine policy per the documentation:3 votesplanned · AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
We will look into closing the feature gaps here for 1710.
This would make it easier to remove multiple packages with similar names.3 votes
Get-CMPackage should already support wildcards today. Remove-CMPackage doesn’t support wildcards and this isn’t something we plan on addressing but you can work around that limitation by doing something like this:
Get-CMPackage -Name “Foo*” | Remove-CMPackage -Force
1. Take me right to script status after running the script.
2. Under Script status after deploying script allow for filtering/export/reporting.3 votes
the ContentLibraryCleanup tool is great, but can we have a PowerShell version of it to aid with automation of same? thanks !2 votes
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 14401 vote
I would like the ability to right-click various nodes, eg packages, applications, task sequences, etc and export the data for that node to a file, eg csv which could easily be read back in via powershell. This would allow test environments to be set up quickly and might even help provide an a way to restore a production environment if all else fails...1 vote
Import-CMComputerInformation is not allowing me the same access via Powershell as the console itself.1 vote
Create a powershell to configure the alerts on a specific collection. like adding collection to EP dashboard and configure thresholds1 vote
- Don't see your idea?