Installing Powershell 2.0 using GPO companywide

Hi All,

I'd like to know how or what is the fastest way to deploy Powershell 2.0 from: company wide using GPO ?

at the moment my GPO is consist of manually drag n drop of computer object into:
Windows XP, Vista and 7 (all version 32 bit and 64 bit) --> Workstations OU
Windows Server 2003 and 2008 (all version 32 bit and 64 bit non DC) --> Servers OU

that's it only those simple categorization and I wonder how to install the correct binary into the target machine ? there are so many different installation files for each version of OS.

Who is Participating?
mcsweenSr. Network AdministratorCommented:
Are you running WSUS?  If so all you have to do is approve the update in the WSUS admin console.
Joseph DalyCommented:
Best way of doing this is to create your group policies for each individual installation (xp, vista,7,etc). You can then apply all of these group policies to the same ou. If you just left it like this all versions would try to install on all machines. However if you were to use WMI filtering you can create a WMI filter so that each version will only run on the correct operating system.

There are a bunch of different options you can use WMI to filter against but in your case you can probaby use the system version. An example of a WMI filter would be like below.

SELECT Version FROM Win32_OperatingSystem WHERE Version LIKE "5.1%"

I use this to make sure I am only targeting windows xp machines.

A good tool for testing and validating your WMI filters can be found here. This will let you pick a computer and test your installation against it. If it validates to true then the GPO will apply, false it wont.
Joseph DalyCommented:
and if you do end up going the WMI filtering route a very handy tool Ive found helps me in building my WMI queries is the WMI code creator. This will easily let you open and view the WMI repositories and see what data they contain and it has an execute command that allows you to pull data on the local machine or a remote machine.

And as fas as finding the difference between a 32 bit and 64 bit machine you could probably use Win32_Computersystem and pull the SystemType variable. On my 32 bit machine it returns "X86-based PC".

You may need to do a little more digging on this one but im sure its very possible. Any questions let me know.
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

jjozAuthor Commented:
@mcsween: thanks mate, from memory I only auto approve the critical and security update only, that's why i couldn't find the WMF install, OK i shall then include the additional thing for auto approve.
@xxdcmast: wow that's good thing to know mate, I'll try to implement the WMI filtering and see how it goes.
Joseph DalyCommented:
If you have WSUS already implemented thats probably the easiest way to go. But as far as future tasks WMI filtering is a huge tool to have in your IT arsenal. Basically since you can pretty much get any infomation you want about a computer from WMI you can very granularly target GPO application using it.

Good luck and let us know how this goes.
jjozAuthor Commented:
ah yes i do have WSUS, I've just added the auto approve for the KB968930 in the WSUS and it is now on queue with the asterisk symbol in front of it.

I guess it's only a matter of time before it is all installed in all machine.

Thanks mate !
jjozAuthor Commented:
thanks for the response mate !
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.