Ideas
What features would you like to see?
All of the feedback that you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building System Center Configuration Manager, though we can’t promise to reply to all posts.
If you believe you have found a product bug, please use Feedback Hub. For more details, see: https://docs.microsoft.com/en-us/sccm/core/understand/find-help.
Standard Disclaimer – our lawyers made us put this here ;-) Please note that the System Center Configuration Manager feedback site is moderated and is a voluntary participation-based project. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos which you do not want to grant a license to Microsoft. See the “User Voice Terms of Service” link below for more information.
-
add a powershell possibility to add requirements to a deploymenttype of an application
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.
86 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.
For more details see: https://blogs.msdn.microsoft.com/ameltzer/2017/04/20/powershell-how-to-add-enhanced-detection-methods-to-deployment-types-1704-tp/
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.
-
Improve and speed up adding or removal processes of direct members to collections, optimize handling in backend
We need a quick way to quickly populate or empty collections. Targets should be imported as rules without triggering other processes in the background (eval/re-built). The same also applies to removal rules.
Please implement something like an cmdlet “Add-CollectionMemberRules” / “Remove-CollectionMemberRules” with fast adding rules method, without delays, without rebuilding the complete collection sets in the background. The cmdlet should support especially adding rules like "DirectMembers".
Note:
This will help to control and steer application (ramp-up / ramp-down) rollouts, depending on device target lists, created by internal IT or delivered by business partner. The lists could based on different information…63 votes -
Run Scripts: Ability to Edit Scripts
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.
46 votesNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
We have have several work items in our backlog to improve the experience here for future releases.
-
Run Scripts: Need ability to schedule execution
Since version 1707 it's now possible to run Powershell scripts for a collection, but these scripts cannot be scheduled. It would be of real value if these Powershell scripts could be scheduled.
36 votes -
Powershell cmdlet for adding global conditions as requirements
We are using PowerShell as a frontend for creating applications. As default we create multiple deployment type, each of them intented to run in certain environemts. These environemts are defined in some custom global conditions.
When creating the deployment type we can very easily identify which global contitions shold be set as requirement. But we miss a Powershell cmdlet to automize this task. Instead we rely on the application creator to remember to add these conditions.
So far I have found a PS-script that can add one of the build-in conditions, but it fails when trying to add a custom…
32 votesNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
Thanks for the suggestion. This is something we plan to address in a future release.
-
Create a PowerShell cmdlet too add/edit/remove duplicate hardware identifiers
New-CMDuplicateHardwareIdentifier
Set-CMDuplicateHardwareIdentifier
Remove-CMDuplicateHardwareIdentifierPlease 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!
24 votes -
Provide a Powershell PackageManagement Repository and perhaps management thereof
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.
16 votes -
Save-CMSoftwareUpdate error RPC server unavailable when connecting under a different account
My idea is to have the scenario described below supported.
When running Save-CMSoftwareUpdate command on a CMSite-PSDrive that connects to a ConfigMgr site in a different domain (used Get-Credential to pass credentials in New-PSDrive call) than the user account the PowerShell window is running as, I get error 'The RPC server is unavailable'.
I can successfully change location to the PS drive, and run other ConfigMgr PS cmdlets.
Commands:
New-PSDrive -Name <sitecode> -PSProvider 'CMSite' -Root <siteserverFQDN> -Credential (Get-Credential)
Set-Location <sitecode>:
Save-CMSoftwareUpdate -SoftwareUpdateName <name> -DeploymentPackageName <name> -VerboseVerbose output from Save-CMSoftwareUpdate call:
VERBOSE: Start: Execution of WQL query: Select * from…
12 votesNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
Thank you for reporting this. Does the same thing reproduce when downloading software updates through the console?
-
Run Scripts: Need folder support for feature
It would be nice to be able to make folders and apply security to each folder for the new scripts feature.
10 votes -
Create a PowerShell cmdlet or cmdlet parameter to add return codes to application deployment types
Add a PowerShell cmdlet or cmdlet parameter to add return codes to application deployment types.
9 votes -
Create application from Licence for Store Apps
Create application from PowerShell from the 'Licence for Store Apps'
7 votes -
Run Scripts: Do not preserve parameters when scripts are re-run, and log parameter usage in Monitoring
When using parameters, the last value used should be blanked out when run again. The value of parameters is the dynamics of it all. You can overwrite the value but seems it would be best servers to not retain the value after running. Would also be great if the parameter used was logged in the Script Status node for ease of tracking.
7 votes -
SCCM module cmdlet creation for folders
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 -
New-CMApplication rejects icons larger than 250x250
New-CMApplication rejects icons larger than 250x250 and returns the warning and error below, even though the SCCM console allows icons up to 500x500.
WARNING: The maximum size of an icon is 250px X 250px.
New-CMApplication : Validation of input parameters failed. Cannot continue.7 votes -
Set-CM<Type>DeploymentType fails with Invalid Property when updating Content Location
Since I updated to 1706, any of the Set-CM<Type>DeploymentType cmdlets fail with an error when I try to update the content path/location to another location. Based on the error message, it seems the cmdlets need to have extra parameters added to handle the separate Install and Uninstall content paths/locations. Perhaps you could add -UninstallContentLocation and a switch for -UninstallContentSameAsInstallContent.
Set-CMScriptDeploymentType : Invalid property: object Application(ScopeId_8C35D19A-F107-4878-83CC-9E26B213220D:Application_a463d8c5-c106-43ae-993b-f5bcb2f4ae4c:15) property
DeploymentTypes.DeploymentTypes[0].Installer.Installer.UninstallContent: Uninstall Content not found in Contents collection
At line:54 char:3
+ Set-CMScriptDeploymentType -ApplicationName $cmApplicationNa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Set-CMScriptDeploymentType], InvalidPropertyException
+ FullyQualifiedErrorId : Microsoft.ConfigurationManagement.ApplicationManagement.InvalidPropertyException,Microsoft.ConfigurationManagement.Cmdlets.AppMan.Commands.SetScriptDeploymentTypeCommand6 votesplanned ·AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
Thank you for this bug report. We will investigate this.
-
Powershell - Return TopConsoleUser
Get-CMTopConsoleUser -Computer MyPC
6 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 -
Run Scripts: Need cmdlets to support feature
Create cmdlets for the new in console Powershell scripts. Some good ones would be new Script Deployment and get script results.
EX:
New-CMPSScriptDeployment -Name "Script Name" -CollectionName "Collection Name"6 votes -
PowerShell cmdlet "Remove-CMMaintenanceWindow" should accept Window Time as parameter
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 -
Transaction support for PowerShell cmdlets
today when using powershell cmdlet the action is performed direct against the server, as example, if you want to create an application, add couple of deployment types and perform other small changes, you end up with lots of revisions (easily, 10). when you have lots of revisions, this start to impact the performance.
it would be nice if we can have the cmdlets transactional, in this case, you create the object and the changes does not apply to the database, you need to "save" the change.
on the application example, you could create the application, create the dt's, changes, etc.…
5 votes
- Don't see your idea?