Discussion:
Force XP to keep patching with windows updates until complete
(too old to reply)
Jordan
2010-04-16 15:53:50 UTC
Permalink
I use RIS server to deploy Windows XP workstations. I use Group Policies
and Active Directory to deploy almost all my software including Office,
Visual Studio, etc. I also use WSUS 3.0 to update the workstations and I
use Group Policies to set the schedule to download the updates and install
them at 3:00 AM which works well.

When I setup a new computer using RIS and deploy all the software using AD
GPOs it takes about 4 or 5 nights to fully patch XP, Office, Visual Studio,
and the patches to upgrade to IE 8. If I want it done quicker I can just
login and run wuauclt.exe /detectnow and apply the patches faster.

Is there some script or something that I can run where Windows XP will
automatically check for the updates after it finishes booting (without
logging in) and check for and install all the updates and reboot if needed?
I would like to add this to Windows' startup script so when I build a new
computer it will just keep patching away until complete.
Florian Frommherz
2010-04-17 10:48:37 UTC
Permalink
Howdie!
Post by Jordan
Is there some script or something that I can run where Windows XP will
automatically check for the updates after it finishes booting (without
logging in) and check for and install all the updates and reboot if needed?
I would like to add this to Windows' startup script so when I build a new
computer it will just keep patching away until complete.
Since you already are on RIS, there are a few options to this:
(1) use a Windows XP SP3 (current SP) CD to create your RIS "image".
(2) use a Windows XP master installion, sysprep it and use that with RIS
to deploy the machines. Like that, you have the updates backed in the image
(3) have the updates as .exe files and call a batch file after correct
installtion (RunOnce) that would install those updates one by one.

Cheers,
Florian
Jordan
2010-04-19 00:14:08 UTC
Permalink
That will not work because I would have to know which computer gets what
list of updates. some computers have Office, some just viewers. Some have
Visual Studio, some do not. There are just to many variables which is why I
am using WSUS. Plus, there is still the problem of the reboots.
Post by Florian Frommherz
Howdie!
Post by Jordan
Is there some script or something that I can run where Windows XP will
automatically check for the updates after it finishes booting (without
logging in) and check for and install all the updates and reboot if needed?
I would like to add this to Windows' startup script so when I build a new
computer it will just keep patching away until complete.
(1) use a Windows XP SP3 (current SP) CD to create your RIS "image".
(2) use a Windows XP master installion, sysprep it and use that with RIS
to deploy the machines. Like that, you have the updates backed in the image
(3) have the updates as .exe files and call a batch file after correct
installtion (RunOnce) that would install those updates one by one.
Cheers,
Florian
kj [SBS MVP]
2010-04-21 22:24:17 UTC
Permalink
See Lawrence's answer in the update_services group.
Post by Jordan
That will not work because I would have to know which computer gets
what list of updates. some computers have Office, some just viewers.
Some have Visual Studio, some do not. There are just to many
variables which is why I am using WSUS. Plus, there is still the
problem of the reboots.
Post by Florian Frommherz
Howdie!
Post by Jordan
Is there some script or something that I can run where Windows XP
will automatically check for the updates after it finishes booting
(without logging in) and check for and install all the updates and
reboot if needed?
I would like to add this to Windows' startup script so when I build
a new computer it will just keep patching away until complete.
(1) use a Windows XP SP3 (current SP) CD to create your RIS "image".
(2) use a Windows XP master installion, sysprep it and use that with
RIS to deploy the machines. Like that, you have the updates backed
in the image
(3) have the updates as .exe files and call a batch file after
correct installtion (RunOnce) that would install those updates one
by one. Cheers,
Florian
--
/kj
Loading...