In my previous post, I ran through a quick and dirty overview of Group Policy Preferences in Windows 2008. One little tidbit of information to note is that in order to take advantage of Group Policy Preferences in your Windows 2008 domain, you need to have the Group Policy Preferences Client Side Extensions installed on your PCs and Servers. The Client Side Extensions are installed on Windows 2008 systems by default, but they must be deployed to your XP, Vista, and 2003 devices in order to take advantage of Group Policy Preferences.
Like virtually everything in IT – there is more than one way to skin a cat. The GPP Client Side Extensions are available as an update for Windows (KB 943729). So if you have a method for centralized deployment of updates, you can push this update out to all of your machines. If you’re using WSUS – 943729 is classified as a Feature Pack – so you will need to be synchronizing all Feature Pack updates in order to deploy this via WSUS.
If you don’t have an automated method for deploying updates, or if you’re just a bit sick & twisted like I am, we can configure our SBS 2008 domain so that all machines get the update installed automatically via a GPO startup script. I personally like this approach for a few reasons. First – once it’s set up, we don’t have to do anything special. If we add a new machine to the domain, it will get the Client Side Extensions installed automatically at startup. And considering the few reboots that happen when joining a PC to the domain via http://connect – the CSE will almost always be installed before the user logs in for the first time. This is beneficial to relying on WSUS – because even if we have the update approved for installation, when the PC is first joined to the domain it has to check in with WSUS, and depending on our patching schedule, it could take several days until the CSE actually gets installed. If we’re relying on Group Policy Preferences to handle our drive mappings, printer installations, etc. – it’s obviously preferable to have the CSE installed as soon as possible.
So, I’ve put together a little vbscript to handle the installation of the Group Policy Preferences Client Side Extensions. This script can be used in a number of fashions – from running it manually on a device, to using your favorite Remote Monitoring & Management product (Level Platforms, Kaseya, etc.) to deploy it, or by using it as a startup script in a domain Group Policy Object.
A few details regarding the script:
- The script assumes that the CSE installers are present on the LAN. Therefore you will want to make sure each of the six variations of the CSE installer (both x86 & x64 for Vista, XP & 2003) are downloaded to a share on your network.
- You will need to edit the paths to the installers in the script. The defined paths can be found on lines 47 – 52. Note that these paths must be UNC paths to work.
- If you are going to use the script as a domain startup script, remember that startup scripts execute under the computer account’s security context – so you will need to make sure that your Domain Computers security group has read access to the share where the script and the CSE installers reside.
I’ve tested the script on a number of systems, and it has worked flawlessly on each. However, as usual I make no warranties of any kind, and if you choose to use this script in a production environment, you do so at your own risk