+ Reply to Thread
Results 1 to 3 of 3

Thread: How to deploy XP SP3 using Group Policy

  1. #1
    dcadler is offline Getting Started on GPanswers.com
    Join Date
    Dec 1969
    Posts
    3

    Default

    I am looking for input on deploying XP SP3 using Group Policy Software Installation. I realize that I can use WSUS, and perhaps that would be the best option, but I would like to know if it can be done using GP and if there are any issues or problems. Is it as simple as extracting the msi from the XP SP3 Network Install package and puting it on a network share, then pointing the GPO at the msi?

    Any input would be gretly appreciated.

    Thanks,

    Dave

  2. #2
    RTHJr is offline 10+ Helpful Posts 15+ Helpful Posts
    Join Date
    Dec 1969
    Posts
    17

    Default

    You would have to setup a pristine machine with XP SP1 or SP2 on it, run a SysDiff tool, install SP3 manually, then run SysDiff again, and take that difference file and convert it with an MSI packager tool. That is the gist of the process as there are a variety of MSI packaging tools out there. WinInstallLE is the most popular:

    http://www.scalable.com/WinINSTALL_LE.aspx

    Doing this on a virtual machine is ideal because after making an MSI package you can roll back the virtual machine to the pristine state and make another MSI package for another application all over again.

  3. #3
    nathang is offline Getting Started on GPanswers.com
    Join Date
    Dec 1969
    Posts
    7

    Default

    RTHJr's procedure is correct for capturing legacy application installers into a MSI so that you can GPO-deploy them, however MS recommend against taking this approach to deployment of security updates and service packs. Its unlikely that you'll be able to get a working deployment of SP3 via this process in any case, but even if you did, you'll proably find yourself in a position where the desktops that you deploy this frankenstein'd SP3 upon may no longer be entitled to MS support. In other words.... here be dragons, enter at your own risk.

    The main reason that this is the way that it is, is that Windows File Protection will be enabled on most of the DLLs etc that SP3 will update. MSIEXEC is not designed to handle this, whereas UPDATE.exe is.

    Good luck with your deployment.

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Search Engine Friendly URLs by vBSEO