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 Microsoft Endpoint Configuration Manager, though we can’t promise to reply to all posts.
If you require assisted support, please see https://aka.ms/cmcbsupport for more details.
-
ConfigurationManager PowerShell module should register itself as an Env Variable
Today, when you install the CM Console, the PowerShell module will be placed under the %CMInstallDirectory%\AdminConsole\Bin\ConfigurationManager.psd1
This makes sense given where the user is choosing to install the console, and that's fine. But placing it here off the beaten path means that it is not importable using PowerShell's module autodiscovery features. For instance, if a module is found in any of the standard user or system paths (or registered under the $ENV:PsModulePath) the user can easily import the module without having to specify the full path, a big user quality of life win. This is the way that SQL Server…
88 votes -
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!
64 votesstarted ·AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Thanks for your feedback and suggestions, updating status to started.
We added these CmdLets in our 1910 release:
New-CMDuplicateHardwareIdGuid
New-CMDuplicateHardwareIdMacAddress
Remove-CMDuplicateHardwareIdGuid
Remove-CMDuplicateHardwareIdMacAddressMore details here:
https://docs.microsoft.com/en-us/powershell/sccm/1910-release-notes?view=sccm-psPlease try them out and share any feedback you may have, then I’ll likely close this item with our 2002 release.
-
add a powershell possibility to add repair command to a deploymenttype of an application
add a powershell possibility to add repair command to a deploymenttype of an application
55 votesunder review ·AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We have added new parameters for 2002 for Add/Set-MsiDeploymentType:
-RepairCommand/-RepairProgram (mutually exclusive)
-RepairWorkingDirectory/-RepairStartIn (mutually exclusive)These changes should be in the latest TPs.
-
Add the ability to add and edit Install Behavior for Application Deployment types with PowerShell cmdlets
Add the ability to add and edit Install Behavior for Application Deployment types with PowerShell cmdlets
52 votes -
Improve folder support in cmdlets
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?
37 votesNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Thank you for your feedback. Folder support is something that is very limited in the cmdlet library today and something that’s in our backlog to improve in a future release. In my opinion, I think the way things should work is if you’re in a collection folder in the cmdlet drive provider, it should just create the collection in the right place.
I’ve linked this feedback to our internal work item to improve folder support so this doesn’t get lost.
Thanks!
-
"Provision this application for all users on the device" cmdlet
In release (1810) an option was added to the "User Experience" tab for APPX deployments.
With the available cmdlets you can automate your deployments, but there is no option to set this outside of the UI.
Please add a "Provision this application for all users on the device" parameter to the "Add-CMWindowsAppxDeploymentType" cmdlet.
24 votes -
Allow Deadline with Start-CMApplicationDeployment using UpdateSupersedence
When using the PoSh Cmdlet Start-CMApplicationDeployment with Parameter -UpdateSupersedence et to $true the DeadlineDateTime Parameter it ignored if the Application is deployed as Available - I actually states it in a Warning as well.
But with UpdateSupersedence set to true we need the Deadline Parameter again, to not enforce the updates immediately.23 votesunder review ·AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Support was added in the 2007 TP and will ship in 2010 CB.
-
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.
22 votes -
Missing cmdlet: Set-CMApplicationGroupDeployment
We need the ability to deploy application groups with PowerShell.
Similar to Set-CMApplicationDeployment - but for groups.
22 votesunder review ·AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Cmdlets for creating, modifying, and removing application group deployments are in the 2010 TP and should be in the 2010 CB release.
-
Add a vendor parameter to Get-CMSoftwareUpdate
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.
18 votesunder review ·AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Vendor support will be in 2010 CB and is available in technical previews starting with 2004.
-
Get driver by category with Get-CMDriver
Get-CMDriver does not provide on option to get drivers by category.
14 votesNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Thank you for your feedback. We have added this to our backlog.
-
Update CM cmdlet documentation and downloadable help file
Running update-help pulls down a help file to an older version of the cmdlets. For instance, do a clean install of the console and cmdlets.
Type:Get-Help Add-CMApplicationCatalogWebsitePoint
On a machine that has not had the help file updated, you will see 6 parameter sets under Syntax. Run update-help and then try again. You will now see 2 parameter sets under Syntax. In addition, there is no detailed information for the new cmdlets added.
13 votes -
PowerShell Cmdlet to display the required software updates for a device
I would like to have a cmdlet to display all required updates for a device, or all devices. I have made a SQL query to do this, so I know it's possible. The query is based on the "Software Updates - A Compliance" reports, but only lists required updates, not installed. This is very useful for finding any missed updates that may be important or critical.
13 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) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Thank you for reporting this. Does the same thing reproduce when downloading software updates through the console?
-
Allow "uninstall content settings" to be modified using PowerShell
Monthly updating of applications like FlashPlayer, Java, Chrome, Reader DC, Office 365 Client, etc. are repetitive and tedious, so I like to automate monthly applications updates as much as possible. When creating a new application using powershell, I cannot set the "Uninstall content setting" located under the Deployment Type and the Content tab. This allows me to save on downloading large sets of files to uninstall when either an "MSIEXEC /X {GUID}" handles it with no files required, or something like Office 365 Client where 1.5 GB is needed to install, but only 5MB or so to uninstall.
The command…
11 votes -
Commandlet to get the cmsitebackupstatus
We have get-cmsoftwareupdatesync command to get the Software update synchronization status.
Like the same, if we have get-cmsitebackupstatus command it will be easy to get the last backup info.10 votes -
Need Get-CMDetectionClause cmdlet
Could we have a get-cmdetectionclause command? I'd like to be able to get an existing detection clause for a deployment which would be useful for not only managing existing detection clauses but being able to explore and re-using them for other applications.
As it is right now I use get-cmapplication | get-cmdeploymenttype | select SDMPackageXML in order to view the detection method as XML.
10 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.…
9 votes -
Need cmdlets to support creating apps from Windows Store for Business
Create application from PowerShell from the 'Licence for Store Apps'
8 votes -
Add a cmdlet to delete (or at least disable) a Client Settings deployment (cmclientsettingsdeployment)
There is currently no cmdlet to delete or disable a deployment of Client Settings. You can create a deployment by using the Start-CMClientSettingDeployment cmdlet but there is absolutely no way of stopping, deleting, or disabling the deployment. If you run a Get-CMDeployment against a collection, it only returns all deployments except a Client Setting.
7 votes
- Don't see your idea?