How do I install the Migrating Wmi To Cim skill?

Run npx skillmds@latest add microsoft/migrating-wmi-to-cim in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Migrating Wmi To Cim safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Migrating Wmi To Cim?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Migrating Wmi To Cim free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Migrating Wmi To Cim?

Microsoft (@microsoft) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Migrating Wmi To Cim by microsoft — Agent Skill

Name: Migrating Wmi To Cim
Author: Microsoft

Migrating Wmi To Cim

Migrate removed WMI cmdlets and type accelerators to CIM in PowerShell 7.x: Get-WmiObject → Get-CimInstance, Invoke-WmiMethod → Invoke-CimMethod, Remove-WmiObject → Remove-CimInstance, Register-WmiEvent → Register-CimIndicationEvent, and [wmi]/[wmiclass]/[wmisearcher] accelerators. Use during the powershell-5.1-to-7-upgrade scenario for the WMI blocker bucket.

Microsoft 344ae21 2.8 KB Updated Sep 17, 2026 2.7k repo stars

File contents

WMI → CIM Migration (PowerShell 7.x)

All *-WmiObject/*-Wmi* cmdlets and the [wmi*] type accelerators are removed in PowerShell 7. Migrate to the CIM cmdlets (CimCmdlets module, shipped in-box).

Cmdlet mapping

Windows PowerShell 5.1	PowerShell 7.x
`Get-WmiObject -Class X`	`Get-CimInstance -ClassName X`
`Get-WmiObject -Query "..."`	`Get-CimInstance -Query "..."`
`Invoke-WmiMethod`	`Invoke-CimMethod`
`Set-WmiInstance`	`Set-CimInstance` / `New-CimInstance`
`Remove-WmiObject`	`Remove-CimInstance`
`Register-WmiEvent`	`Register-CimIndicationEvent`
`[wmi]"path"`	`Get-CimInstance` by key
`[wmiclass]"class"`	`Get-CimClass` / `Invoke-CimMethod`
`[wmisearcher]"query"`	`Get-CimInstance -Query`

Key differences (do not do a blind rename)

-Class → -ClassName. The parameter name changed.
Return type differs. CIM returns Microsoft.Management.Infrastructure.CimInstance, not System.Management.ManagementObject. Downstream property access usually works, but:
- Method invocation changes: $obj.SomeMethod($a) (WMI) → Invoke-CimMethod -InputObject $obj -MethodName SomeMethod -Arguments @{ Param = $a }.
- DateTime and some enums render differently — verify consumers.

Remote access. -ComputerName on WMI used DCOM. CIM defaults to WSMan; for DCOM-only targets create a session:

$opt = New-CimSessionOption -Protocol Dcom
$s = New-CimSession -ComputerName $c -SessionOption $opt
Get-CimInstance Win32_Service -CimSession $s

Filtering. -Filter "Name='x'" works on both; prefer it over client-side Where-Object for performance.

Example

# 5.1
$svc = Get-WmiObject -Class Win32_Service -Filter "Name='Spooler'"
$svc.StopService()

# 7.x
$svc = Get-CimInstance -ClassName Win32_Service -Filter "Name='Spooler'"
Invoke-CimMethod -InputObject $svc -MethodName StopService

Validation (Rung 4b)

WMI→CIM is read-mostly and best validated by diffing the selected properties actually consumed, not raw objects:

$old = Get-WmiObject Win32_LogicalDisk | Select DeviceID,FreeSpace   # on a 5.1 box
$new = Get-CimInstance Win32_LogicalDisk | Select DeviceID,FreeSpace # on pwsh 7
Compare-Object $old $new -Property DeviceID,FreeSpace

Record read-only-diff-clean when the consumed properties match.

---name: migrating-wmi-to-cimdescription: Migrate removed WMI cmdlets and type accelerators to CIM in PowerShell 7.x: Get-WmiObject → Get-CimInstance, Invoke-WmiMethod → Invoke-CimMethod, Remove-WmiObject → Remove-CimInstance, Register-WmiEvent → Register-CimIndicationEvent, and [wmi]/[wmiclass]/[wmisearcher] accelerators. Use during the powershell-5.1-to-7-upgrade scenario for the WMI blocker bucket.---# WMI → CIM Migration (PowerShell 7.x)All `*-WmiObject`/`*-Wmi*` cmdlets and the `[wmi*]` type accelerators are**removed** in PowerShell 7. Migrate to the CIM cmdlets (`CimCmdlets` module,shipped in-box).## Cmdlet mapping| Windows PowerShell 5.1 | PowerShell 7.x ||---|---|| `Get-WmiObject -Class X` | `Get-CimInstance -ClassName X` || `Get-WmiObject -Query "..."` | `Get-CimInstance -Query "..."` || `Invoke-WmiMethod` | `Invoke-CimMethod` || `Set-WmiInstance` | `Set-CimInstance` / `New-CimInstance` || `Remove-WmiObject` | `Remove-CimInstance` || `Register-WmiEvent` | `Register-CimIndicationEvent` || `[wmi]"path"` | `Get-CimInstance` by key || `[wmiclass]"class"` | `Get-CimClass` / `Invoke-CimMethod` || `[wmisearcher]"query"` | `Get-CimInstance -Query` |## Key differences (do not do a blind rename)1. **`-Class` → `-ClassName`.** The parameter name changed.2. **Return type differs.** CIM returns `Microsoft.Management.Infrastructure.CimInstance`, not `System.Management.ManagementObject`. Downstream property access usually works, but: - Method invocation changes: `$obj.SomeMethod($a)` (WMI) → `Invoke-CimMethod -InputObject $obj -MethodName SomeMethod -Arguments @{ Param = $a }`. - `DateTime` and some enums render differently — verify consumers.3. **Remote access.** `-ComputerName` on WMI used DCOM. CIM defaults to **WSMan**; for DCOM-only targets create a session: ```powershell $opt = New-CimSessionOption -Protocol Dcom $s = New-CimSession -ComputerName $c -SessionOption $opt Get-CimInstance Win32_Service -CimSession $s ```4. **Filtering.** `-Filter "Name='x'"` works on both; prefer it over client-side `Where-Object` for performance.## Example```powershell# 5.1$svc = Get-WmiObject -Class Win32_Service -Filter "Name='Spooler'"$svc.StopService()# 7.x$svc = Get-CimInstance -ClassName Win32_Service -Filter "Name='Spooler'"Invoke-CimMethod -InputObject $svc -MethodName StopService```## Validation (Rung 4b)WMI→CIM is read-mostly and best validated by diffing the **selected propertiesactually consumed**, not raw objects:```powershell$old = Get-WmiObject Win32_LogicalDisk | Select DeviceID,FreeSpace # on a 5.1 box$new = Get-CimInstance Win32_LogicalDisk | Select DeviceID,FreeSpace # on pwsh 7Compare-Object $old $new -Property DeviceID,FreeSpace```Record `read-only-diff-clean` when the consumed properties match.

Frequently asked questions