Dan said:
Have an older unit that is used to run a image system. Unit is not
and will not be hooked to net. Loaded XP -SP2 using a slipstream
diskette. Do I need to put in any other updates? -- and if so, how
do I do so? Thanks.
Do you *need* to? No idea - I have no way of knowing what will be running
on this system, if it will need .NET, etc.
You could just get things as you need.
If you really want to update everything - you can.
Download the updates individually, burn them to CD/DVD/thumb drive, etc and
get them to the machine in question.
Quick and Easy:
http://wud.jcarle.com/
You can download and save all updates for later use - including service
packs. You can even integrate those patches into your Windows XP
installation CD - so if you had to reinstall - you wold end up almost
fully-patched right fromthe beginning.
For service pack 2 in particlular:
Direct Download of Service Pack 2 (SP2) for Windows XP
http://snipurl.com/8bqy
Order Windows XP Service Pack 2 on CD
http://snipurl.com/d41v
You can download each update manually - based off the KB Article number,
etc. That way you can back it up/burn a CD of them in case you need them or
use them to keep a slipstream/integrated (updated) Windows XP CD.
How to use the Windows Update Catalog
http://support.microsoft.com/kb/323166
(In order to use the Windows Update Catalog, you must use IE to get the
patches..)
Windows Update Catalog
http://v4.windowsupdate.microsoft.com/catalog/en/default.asp
(In order to use the Windows Update Catalog, you must use IE to get the
patches..)
Creating an Integrated Installation
http://snipurl.com/el43
Integrate software updates into your Windows installation source files
http://support.microsoft.com/kb/828930
Really customize your CD..
http://unattended.msfn.org/
Produce an up-to-date XP Distibution CD
http://xpcreate.com/
AutoPatcher
http://www.autopatcher.com/
AutoStreamer
http://www.neowin.net/forum/index.php?showtopic=223562
You can see the critical (security and other) patches released for a given
month using the following:
http://www.microsoft.com/technet/security/bulletin/ms##-***.mspx
At the end of this line you see "ms##-***.mspx" .. If you simply replace ##
with the two-digit year and the *** with the three character month
abbreviation, you will see the list of "critical" and "important" patches
for that month (since it only happens once a month usually, if you check by
the second Tuesday (wait until afternoon) of each month - you should be
fine) - note that future months will not work.
As an example...
December 2004's patches..
http://www.microsoft.com/technet/security/bulletin/ms04-dec.mspx
March 2005's patches..
None released.. so that one will fail...
May 2005's patches..
http://www.microsoft.com/technet/security/bulletin/ms05-may.mspx
July 2005's patches..
http://www.microsoft.com/technet/security/bulletin/ms05-jul.mspx
Once you get on the page with each month's list of patches.. You can go to
the related KB articles and grab the appropriate files from there.