Tagged: WMI

0

CIM vs. WMI CmdLets – Speed comparison

In one of my last posts I mentioned that for me the CIM CmdLets have been faster than the WMI CmdLets. I referred mainly to my personal impression working with these CmdLets for quite some time on a pretty large array of different servers and tasks and supported this statement...

2

PowerShell CIM CmdLets – Working with lazy properties

In my last post, I explained how to solve one of the stumbling blocks when working with the PowerShell CIM CmdLets. The second problem, which was both pretty nasty as it basically prevented me from using the CIM CmdLets properly for SCCM and pretty time consuming, as it was hard...

2

CIM vs. WMI CmdLets – The top reasons I changed over

Some time ago I moved most of my WMI related work from the “deprecated” PowerShell WMI CmdLets (Get-WMIObject, Invoke-WMIMethod, etc.) over to the “new” CIM CmdLets (Get-CimInstance, Invoke-CimMethod, etc …). It wasn’t really because they are “deprecated”. Microsoft might treat them this way, but they will for sure be around...

3

Start, Cancel or Delete a SCCM Client Operation

In my last post, I demonstrated how to call the InitiateClientOperation method from the SMS_ClientOperation WMI class to run a SCEP Full Scan. However, this call itself is pretty limited for daily administration, as it requires “internal” information like the CollectionID, ResourceID or some TypeID for the Operation itself. Probably...

1

Initiate SCEP Full Scan by script using SCCM Client Operations

Lets assume you have a security device that detects computers possibly infected by some malware. Wouldn’t it be nice to automatically initiate some immediate action for remediation? I recently had such a requirement where we wanted to automatically start a definition download and full scan on those computers. It’s pretty...