Does GPO Deployment of XP SP2 make a local cached copy on clients?
From: Alex Turner (tuvix_at_optonline.net)
Date: 08/13/04
- Next message: jerry: "missing .dll files"
- Previous message: c witt: "Re: missing or corrupt: System32\Drivers\Ntfs.sys"
- Messages sorted by: [ date ] [ thread ]
Date: 13 Aug 2004 00:44:58 -0700
In the Guide for Instaling and Deploying Microsoft Windows XP Service
Pack 2 guide on Microsoft's site (
http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/spdeploy.mspx#XSLTsection126121120120
), they mention 4 ways to deploy the service pack. The first two
scenarios use XPSP2.exe but differ in whether they end up leaving a
local cache of the source files on the client machines afterwards so
they can repair themselves later independently of the server. The way
we'd really rather deploy the service pack is through Group Policy,
using Update.msi, which is scenario 4 there. The thing they don't
mention, however, is whether the GPO method will leave the client
machines with the equivalent of a client-side cache of the install
files or not. Some of the machines we are updating are laptops and
I'd rather not tether them to the server for system files they may
need to reinstall in the future.
Does the GPO deployment of XP SP2 provide for a client-side cache of
the new system files, or should I just not bother myself with this and
wait for Automatic Updates to wash over all my machines individually
in a week?
- Next message: jerry: "missing .dll files"
- Previous message: c witt: "Re: missing or corrupt: System32\Drivers\Ntfs.sys"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
