Prof. Powershell

Prof. PowerShell: COM-munication

Some COM objects work just fine in PowerShell -- maybe better.

Even though PowerShell is based on .NET Framework, it supports legacy approaches to systems management, including how it uses COM objects. If you've written VBScripts, you've used COM objects for things like the FileSystemObject, the Shell and Network. The good news is that you can use those objects in PowerShell, too. The best news is that you can work with the objects interactively without a script!

Open a PowerShell prompt and type:

PS C:\> $shell=new-object -COM 
"wscript.shell"

Now pipe $shell to Get-Member and you should see all of the methods and properties you were used to working with in VBScript. Try this:

PS C:\> $shell.specialfolders

You should see all the special Windows folders. Unfortunately, not all COM functionality translates properly to PowerShell. In VBScript I could use $shell.specialfolders("desktop") to retrieve just the desktop folder, but not in PowerShell. But you can execute methods:

PS C:\> 
$Shell.regread("HKLM\Soft 
ware\microsoft\Windows 
NT\CurrentVersion\Registere 
dOwner")
Admin
PS C:\> $Shell.regwrite("HKLM\Soft 
ware\microsoft\Windows 
NT\CurrentVersion\Registere 
dOwner","Jeff Hicks")
PS C:\> $Shell.regread("HKLM\Soft 
ware\microsoft\Windows 
NT\CurrentVersion\Registere 
dOwner")Jeff Hicks

Having access to these methods provides a transition to moving completely to PowerShell. But sometimes the older ways still work just fine:

PS C:\> $network=new-object -COM "wscript.net 
work"
PS C:\> $network.EnumNetworkDrives()
P:
\\pluto\files

Or the COM objects offer functionality that you don't have in PowerShell, or perhaps an easier approach:

PS C:\> $fso=new-object -com "scripting.filesyste
mobject"
PS C:\> $fso.drives | where {$_.drivetype -eq 2} | 
Select Path,AvailableSpace,FreeSpace,TotalSize

Path  AvailableSpace   FreeSpace   TotalSize
--    --------------   ---------   ---------
C:    136613888        136613888   4285337600
E:    256651264        256651264   1069253632

Remember we're still working with objects, so we can leverage the PowerShell pipeline and take advantage of the best of both worlds. You'll also discover that if you want to work with other apps -- such as Word, Excel or even Apple iTunes -- you can with PowerShell and its support for COM objects. Create a COM object, pipe it to Get-Member to discover its methods and properties and start using it immediately in PowerShell without writing a single line of script.

About the Author

Jeffery Hicks is a Microsoft MVP in Windows PowerShell, Microsoft Certified Trainer and an IT veteran with over 20 years of experience, much of it spent as an IT consultant specializing in Microsoft server technologies with an emphasis in automation and efficiency. He works today as an independent author, trainer and consultant. Jeff writes the popular Prof. PowerShell column for MPCMag.com and is a regular contributor to the Petri IT Knowledgebase and 4SysOps. If he isn't writing, then he's most likely recording training videos for companies like TrainSignal or hanging out in the forums at PowerShell.org. Jeff's latest books are Learn PowerShell 3 in a Month of Lunches, Learn PowerShell Toolmaking in a Month of Lunches and PowerShell in Depth: An Administrators Guide. You can keep up with Jeff at his blog http://jdhitsolutions.com/blog, on Twitter at twitter.com/jeffhicks and on Google Plus (http:/gplus.to/JeffHicks)

comments powered by Disqus

Reader Comments:

Add Your Comment Now:

Your Name:(optional)
Your Email:(optional)
Your Location:(optional)
Comment:
Please type the letters/numbers you see above

Redmond Tech Watch

Sign up for our newsletter.

I agree to this site's Privacy Policy.