|
If you read Friday's newsletter, you now know that you can't deploy the new GPPEs
with Group Policy. (Trust me, I'm as aghast as you are.)
That's because the GPPEs ship as patches (.EXEs and .MSUs) and not as MSIs.
To that end, you can use Group Policy Start-Up Scripts to install the GPPEs on your clients -- if you know what you're doing.
Here's what our script can do for you:
- Developed to be used as a Startup Script (or login script with admin rights)
- Checks if the CSEs are installed already, using local WMI call (and won't double-install them)
-Check OS Version (Windows XP, Windows Server 2003, Windows Vista), using local WMI call
- Check OS Architecture (32 or 64 bit), just checking for a folder as WMI call was kinda strange
- Check OS Service Pack Level, using local WMI call
- Check for GPPE CSE Pre-requisite (XMLlite) on XP/2003 systems, using local WMI call
- Installation of GPPE CSE Pre-reqs on XP/2003 systems
- Handles install on Windows XP SP2/SP3 32-bit (EXE file)
- Handles install on Windows XP 64-bit, any SP level (EXE file)
- Handles install on Windows Server 2003 SP1/SP2 32-bit (EXE file)
- Handles install on Windows Server 2003 64-bit, any SP level (EXE file)
- Handles install on Windows Vista RTM/SP1 32-bit (MSU package)
- Handles install on Windows Vista RTM/SP1 64-bit (MSU package)
Jakob Heidelberg who does a lot of work for us at GPanswers.com wrote this script.
Thanks Jakob !
Want the script? Click here.
Use at your own risk! (And send some feedback if you use it !)
|
