Monthly Archive


CIM cmdlets and remote access

When you used the WMI cmdlets

Get-WmiObject -Class Win32_logicalDisk -ComputerName RSLAPTOP01

You were using DCOM to access the remote machine. Even if you accessed the local machine you were using DCOM.

This changes in PowerShell v3 when using the CIM cmdlets.

If you don’t use a computername

Get-CimInstance -ClassName Win32_logicalDisk

You use DCOM to access the local machine.

If you use –computername

Get-CimInstance -ClassName Win32_logicalDisk -ComputerName RSLAPTOP01

You use WSMAN to access the machine named – irrespective of if it is local or remote

A further complication is that the named machine has to be running WSMAN 3.0 i.e. PowerShell v3 is installed.

If you try to access a PowerShell v2 (WSMAN 2.0) machine with the CIM cmdlets you will get an error. The way round that is to create a CIMsession using DCOM as the transport protocol. If you want to learn how to do that you’ll have to wait until after my session at the PowerShell Summit in April or buy a copy of PowerShell and WMI from

I saw a number of people using the CIM cmdlets in the scripting games without thought to connectivity issues like this.

One Response to CIM cmdlets and remote access

  • John says:

    Hi Richard,

    I’m still very much a beginner so don’t completly understand all of your blog post, but I have a question, actually 2.

    None of the servers we use have PS v3 installed but I have PS v3 running on my desktop. Rather than using a work around would I be better to just use PS v2? If this is correct, if I want to still use PS v3 is it possible to have PS v3 & v2 installed on my desktop?

    If I’ve copletely misunderstood your blog post please accept my apologies.



Leave a Reply