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.152 votesstarted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Changing status back to “Started” as there’s more work to do here. We plan to simplify adding requirements to DTs as well as complete the missing scenarios for detection methods in a future release. Stay tuned for more updates.
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!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:
Please try them out and share any feedback you may have, then I’ll likely close this item with our 2002 release.
Create cmdlets for the new in console Powershell scripts. Some good ones would be new Script Deployment and get script results.
New-CMPSScriptDeployment -Name "Script Name" -CollectionName "Collection Name"9 votesstarted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
1806 will have New-CMScript, Invoke-CMScript, Approve-CMScript, Deny-CMScript, and Remove-CMScript. These cmdlets are not complete but we plan to flesh them out more for future releases.
- Don't see your idea?