Windows Server 2003 doesn't have Win32_Products CLass by default

I'm in the process of writing a prerequisite checking script to deploy PowerShell to all our server and I came across a little annoying error that prevented me from using the Win32_Product Class to check if the .NET Framework was installed on remote machine.

After coming across this Windows Management Infrastructure Blog I discovered an additional gotcha where the Win32_Product class must be added to Windows Server 2003. This can be achieved by adding the "WMI Windows Installer Provider" Windows component under Management and Monitoring tools in Add/Remove Windows Components.

Thanks to Steve Paruszkiewicz [MSFT] for pointing this one out.

get-scripting Blog

I'm always on the look out for more information and blogs/how-to articles around PowerShell and I happen to come accross the get-scripting blog.

The two Presenters post every couple of months some tips, ideas and experiences they come across, and upload a podcast which can be subscribed to via iTunes, so if you a newby looking at PS for the first time or are looking to expand your knowledge, add this blog and podcast to your reading list.

get-scripting Blog