Reinstalling OEM on 30 machines

  • Thread starter Thread starter Doug Lowe
  • Start date Start date
D

Doug Lowe

We've sold 30 older computers to our employees and need to format &
reinstall Windows before sending them out.

I'll be using the newest OEM CD I have, which includes SP2. But there's
still about 45 minutes of Windows updates to be done with multiple reboots.

I don't have the budget to use Ghost for these machines, but I'd like to
send the employees home with a fully patched system. Any suggestions on how
to streamline this process?
 
Doug said:
We've sold 30 older computers to our employees and need to format &
reinstall Windows before sending them out.

I'll be using the newest OEM CD I have, which includes SP2. But
there's still about 45 minutes of Windows updates to be done with
multiple reboots.
I don't have the budget to use Ghost for these machines, but I'd
like to send the employees home with a fully patched system. Any
suggestions on how to streamline this process?

Integrate the post SP2 patches as well.
 
That's what I'm asking...how? The only way I know how to do this is to
install Windows from the OEM CD (SP2), then use Windows Update to apply the
patches. Is there a way to create an install CD that has the patches
integrated into it?

--Doug
`
 
Shenan Stanley wrote:

That's what I'm asking...how? The only way I know how to do this is
to install Windows from the OEM CD (SP2), then use Windows Update
to apply the patches. Is there a way to create an install CD that
has the patches integrated into it?

That's what I said.
A simple google search would have gotten you what you needed.

You likely want Windows XP 32bit SP2 versions of the patch. Some will not
have that option - only "Windows XP" or "Windows XP SP1 or SP2" etc..
Get the one that seems most correct and you likely do not have the 64bit
version. Install in the order given and you should be fine. The first
link,
separated out - is the 270+MB SP2 patch.

http://www.microsoft.com/downloads/...BE-3B8E-4F30-8245-9E368D3CDB5A&displaylang=en

http://support.microsoft.com/kb/834707
http://support.microsoft.com/kb/873333
http://support.microsoft.com/kb/873339
http://support.microsoft.com/kb/883939
http://support.microsoft.com/kb/885222
http://support.microsoft.com/kb/885250
http://support.microsoft.com/kb/885626
http://support.microsoft.com/kb/885836
http://support.microsoft.com/kb/885894
http://support.microsoft.com/kb/886185
http://support.microsoft.com/kb/886677
http://support.microsoft.com/kb/886716
http://support.microsoft.com/kb/887472
http://support.microsoft.com/kb/887742
http://support.microsoft.com/kb/887797
http://support.microsoft.com/kb/888113
http://support.microsoft.com/kb/888240
http://support.microsoft.com/kb/888302
http://support.microsoft.com/kb/890046
http://support.microsoft.com/kb/890047
http://support.microsoft.com/kb/890175
http://support.microsoft.com/kb/890831
http://support.microsoft.com/kb/890859
http://support.microsoft.com/kb/890923
http://support.microsoft.com/kb/891781
http://support.microsoft.com/kb/893066
http://support.microsoft.com/kb/893086
http://support.microsoft.com/kb/893756
http://support.microsoft.com/kb/893803
http://support.microsoft.com/kb/894391
http://support.microsoft.com/kb/896344
http://support.microsoft.com/kb/896358
http://support.microsoft.com/kb/896422
http://support.microsoft.com/kb/896423
http://support.microsoft.com/kb/896424
http://support.microsoft.com/kb/896428
http://support.microsoft.com/kb/896688
http://support.microsoft.com/kb/896727
http://support.microsoft.com/kb/898458
http://support.microsoft.com/kb/898461
http://support.microsoft.com/kb/899587
http://support.microsoft.com/kb/899588
http://support.microsoft.com/kb/899589
http://support.microsoft.com/kb/899591
http://support.microsoft.com/kb/900725
http://support.microsoft.com/kb/900930
http://support.microsoft.com/kb/901017
http://support.microsoft.com/kb/901190
http://support.microsoft.com/kb/901214
http://support.microsoft.com/kb/902400
http://support.microsoft.com/kb/903235
http://support.microsoft.com/kb/904706
http://support.microsoft.com/kb/905414
http://support.microsoft.com/kb/905749
http://support.microsoft.com/kb/905915
http://support.microsoft.com/kb/908519
http://support.microsoft.com/kb/909520
http://support.microsoft.com/kb/910437
http://support.microsoft.com/kb/911927
http://support.microsoft.com/kb/912919
http://support.microsoft.com/kb/913446

You can also integrate them into your install media in most cases.

Rather than give you just a little information - I will tell you how to get
the updates, how to integrate them into your own CD, etc.. That way you are
better informed about your options when it comes to the Windows Updates.

Direct Download of Service Pack 2 (SP2) for Windows XP
http://snipurl.com/8bqy

What to Know Before You Download and Install Windows XP Service Pack 2
http://www.microsoft.com/windowsxp/sp2/sp2_whattoknow.mspx

You can download all updates and burn them to CD..

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.
 
So then you have 30 oem windows xp licenses' to go with those machines
.....right
 
Doug Lowe said:
We've sold 30 older computers to our employees and need to format &
reinstall Windows before sending them out.

I'll be using the newest OEM CD I have, which includes SP2. But there's
still about 45 minutes of Windows updates to be done with multiple reboots.

I don't have the budget to use Ghost for these machines, but I'd like to
send the employees home with a fully patched system. Any suggestions on how
to streamline this process?

Get nLite (free) from www.nliteos.com/download.html and use it to
build a new installation CD with the post-SP2 updates slipstreamed
into it.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
So then you have 30 oem windows xp licenses' to go with those machines
....right

Absolutely. I understand the ins and outs of OEM vs. Retail vs. MOLP
licensing. We bought the computers 3 years ago with OEM Windows XP & saved
all the media, and all the machines have product key stickers on the back.
We're sending the media home with the users who bought the computers.

I'm just trying to figure out how to save the time of connecting to Windows
Update for each computer. What I'd like to do is build an install CD that's
totally current. Looks like Shenan's previous post has links for doing that,
but at first glance it doesn't look easy :(

--Doug
 
You know what I liked best about nliteos? It helped me get through the
process the first time.

I used it to build a CD that worked pretty well, but I missed a half-dozen
or so updates. Then I read on the nliteos forum that its license agreement
prohibits commercial use, and I'm using it at work. But having gone through
the process once with nliteos, I decided it wouldn't be too big of a step to
do the next CD "manually" using Microsoft's tools. So I downloaded the
updates I was missing and wrote a batch file to call each one with the
/integrate switch, then used setupmgr.exe to create defaults (I don't want
it totally unattended) and the second CD worked like a charm. I feel like
I've learned a lot in the process, though clearly there's much more to it I
don't know about yet.

Well, almost. I can't get one of the updates to integrate, but that's OK. I
don't mind running Windows Update to get just one critical update. Before I
did this, Windows Update was taking about 45 minutes.

The one thing that bugs me is that getting all of the updates together is
such as manual & haphazard process. It's to bad Microsoft doesn't just
publish a single download that has all of the critical updates for Windows
XP Professional since SP2, and update it once a month on Patch Tuesday.
Seems to me that would save a lot of people a lot of work.

--Doug
 
I agree, but that's one reason I pay for the TechNet+ Subscription . They
send me all those updates and stuff on DVD every month.
I have been using Microsoft's OEM Pre-install system , But it's not as easy
for the 1st timers

talk to ya later ....Dennis
 
Back
Top