Saturday, March 01, 2008

How to install GPP CSEs using a Startup Script

When you have the Group Policy Preference (GPP) Client Side Extensions (CSE) downloaded you'll notice that they are not (yet) in the .MSI format - so using Group Policy Software Installation (GPSI) is not possible. Bummer, right!?
We have .EXE files for Windows XP/2003 and .MSU files for Windows Vista... But that's not the only thing we need to think about. Before "deploying" these things to the clients on the network we need to know the OS version (XP/2003/Vista), the OS architecture (32 or 64 bit), the Service Pack Level, and whether or not the Group Policy Preference Pre-requisites (WmlLite - http://support.microsoft.com/kb/914783/en-us) are installed.
To make all this pretty easy I've created a "demo" script for deploying the GPP CSEs using Startup Script - or a manual launch (in admin context). My good friend Jeremy Moskowitz asked me to do this - so, a couple of hours later the "demo" - or "beta" - script is public (download below)...
Note: I haven't been able to test in all scenarios yet, but I *think* they are all covered pretty well by now. Please report back if you find any problems - any feedback is welcome!
Download the VBS script right here!
NB! You might need other language version for the XmlLite GPP CSE Pre-requisites, so watch out!
Running the script in your production network is on your own risk. The code is delivered "As Is" - totally free of any charge. No strings attached.

I hope this works out nicely for you!
.

16 Comments:

SeanRinVA said...

I didn't see in your script when you define "strBasePath". Should we DIM that ourselves?

Jakob H. Heidelberg said...

You should have the line:
"Dim strBasePath : strBasePath = "\\SERVER\SHARE\" 'NB! with trailing backslash!"
in the script (one of the first real script lines, if not please re-download.

Let me know how it works out for you!

Tom said...

Works great, thanks very much for this.

Randall said...

I was just about to start testing this at least. Then I realized that a lot of our XP machines will have SP3 installed by the time they get to this further down the road. I checked the script again and I see that you accounted for that, so thanks.

I'll let you know how it goes.

Josh Elson said...

Or better yet, use the following line:

Dim strBasePath : strBasePath = Replace(Wscript.ScriptFullName, "\" & Wscript.ScriptName, "") & "\"

XY said...

The link the script doesn't work - can anyone post a new link to the script for me? I could really do with this and don't want to reinvent the wheel... thanks!

Jakob H. Heidelberg said...

Well, I would think this works "out of the box" by now, but I'm not 100% sure. Unfortunately I can't help you at the moment.

nsumner said...

Indeed the DL link doesn't work. Can you update the DL link?

Jakob H. Heidelberg said...

Hi nsumner,
I don't think it should be necessary to use a script to deploy CSS anymore, and I can't find the script I made anymore, sorry.

Banan said...

Unfortunatelly it is not possible to download Your script? Could You please repair the file access :)

Banan said...

It is necessary because CSE is not installed during windows update cycle. It is an optional update can You update the link?

Jakob H. Heidelberg said...

Hi Banan,

I'll try to find the script at work tomorrow, but it has been a long time since i wrote it. It "got lost" during a switch of webhotel.

Best regards
Jakob

Kojios said...

the link is broken :(

Jakob H. Heidelberg said...

Yes, the link is broken - I'll try to find the script and post it here again, sorry.

Jakob H. Heidelberg said...

Quick and dirty:
http://www.heidelbergit.dk/2011/10/installgppcse-cleartext.html

/Jakob

Ross Berryman said...

Thanks For the Script saved me allot of time.