At wizard completion for anything, show the Powershell cmdlet equivalent like in other System Center products.581 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.54 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
This work didn’t make it into 1704 but we hope to have it in 1705.
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.12 votes
Create a PowerShell cmdlet that will redistribute (not refresh) content on a specific distribution point12 votes
Working for a company with several Configmgr hierarchies, it would be great with a PowerShell cmdlet to initiate and control the updates and servicing.11 votesplanned · AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
We are working on several new cmdlets to automate servicing and updates. The current plan is for these to be in the 1705 technical preview.
The current tentative cmdlets to support this scenario are:
Also we plan to add support for enabling pre-release features to Set-CMHierarchySettings.
I’ll update this feedback once we we know when this will be ready.
Create application from PowerShell from the 'Licence for Store Apps'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
Add a Get-SupSyncStatus cmdlet as it does not exist today.
the only way to achieve this is via WMI
gwmi -Class SMS_SupSyncStatus -Namespace "root\sms\site_$SiteCode" | select LastSyncErrorCode, LastSyncState4 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.4 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!3 votes
This would make it easier to remove multiple packages with similar names.3 votes
It would be very handy to have the AD powershell module that's included in Windows Server and RSAT as an optional component for boot images. I've been including this manually in my boot image as per this article [https://social.technet.microsoft.com/wiki/contents/articles/24413.add-powershell-active-directory-module-in-windows-pe.aspx], but of course with SCCM now being updated so frequently, I have to constantly re-embed this powershell module in the boot WIM. Querying AD during OSD seems like a fairly common requirement, so this ought be quite an easy feature to justify, and relatively trivial to implement.3 votes
it would be good if the Invoke-CMReport gives us the option to pass parameters to the report. today it only open the report and that's it, you need to manually. another parameter that could be added would be to automatically export, so you don't actually need to open the report, just export the data2 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
In previous command Set-CMDeploymentType is was possible to set reboot behavior but in the new Set-CMScriptDeploymentTYpe and SetCMMSIDeploymentType it is not an option.1 voteplanned · AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
Thanks for the feedback. We’ll look into getting this added for 1706.
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?