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.126 votesstarted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, System Center 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.
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"12 votesstarted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, System Center 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.
Additional context can be found:
https://www.reddit.com/r/SCCM/comments/a0lgdt/powershell_system_discovery_container_account/7 votesstarted · AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, System Center Configuration Manager) responded
This functionality is in Technical Preview 1901.
The current 1806 implementation of CMPivot is using the cmdlet GEt-Eventlog read event log entries. The PowerShell command is:
$events = get-eventlog -LogName $logName -Newest 50 -ErrorAction Stop
This limits the logs to be read from to logs like Application, Security, System and only some others. On my client (Get-EventLog -List).Count has only 12 logs.
The better command would be Get-WinEvent. Where I can access all logs. The command (Get-WinEvent -ListLog *).Count returns 463 logs.7 votes
This is available in #ConfigMgr 1902 TP.
- Don't see your idea?