Backing up Windows Updates for later use

[Parasitic]

Ok, I reformat my computers and reinstall Windows fairly periodically, and having to run Windows Update every time on each computer gets annoying very quickly...is it possible for me to just find the executables M$ downloaded, back them up on a blank CD-R, then use for install on another computer? If so, where are the downloaded WU files?

Thanks.

 

[TG2]

What I did is build a OS install (2000, XP or 2003), then go to windows update with the PC, once it gives me a list of available updates, I can click on the 'Details' link in the updates description, then there should be a link to download the file in the pop up window that comes up, its like 2 or 3 clicks in to get to the actual file.

Download the file to a folder on your file server, or local PC.

QChain.exe has to be in the folder with the downloaded updates and you need to create a CMD file like the following :>

"\\Server\Share\WindowsXP-KB913580-x86-ENU.exe" -Z -Q -M
"\\Server\Share\Qchain.exe"

Just add more lines like line1 for all the updates (change the name of course to match the downloaded filename), the file is named, UpdateXP.CMD.

Then next time I can just open the updatexp folder and 2click UpdateXP.CMD and all the updates will be ran, with only 1 click.

 

[jlbenedict]

Well, if you have a machine that you can keep intact for a long period of time, I recommend WSUS.
Of course, this runs on Windows 2000 & 2003 Server.
Also, the latest version of WSUS has support now for updating machines running Windows Vista.

 

[MrChad]

I'm not sure why you "reformat and reinstall Windows fairly periodically", but nonetheless, you can slipstream hotfixes fairly easily.

Check http://unattended.msfn.org/unattended.xp/view/web/26/ and the MSFN forums for more info. One member of that forum, RyanVM, has an updater pack that he maintains to make the process even easier.

 

[JDMnAR1]

Why not just download the monthly ISOs that Microsoft releases?

 

[Smilin]

If you spell it MS instead of M$ I might tell you the answer

 

[corkyg]

Originally posted by: Smilin
If you spell it MS instead of M$ I might tell you the answer

LOL! But, Smilin' that's how we can tell the difference between Microsoft and Multiple Sclerosis.

 

[networkman]

I find that Symantec Ghost or Acronis TrueImage (in concert with Sysprep) is very handy indeed. Just install Windows (whatever version), patch it, install whatever apps, run Sysprep, take an image - problem solved.

When Windows gets messed up, blow it away, restore from the image file and proceed.

Rinse & Repeat as needed.

 

[Parasitic]

The problem is that each computer runs a different version of OS (1 Win2k Pro, 2 XP Home, 1 XP Pro) and I don't really want to go through the trouble of slipstreaming 3 different CD's but instead want to just put all the updates together on a CD.

 

[Genx87]

I'd download SP2 for XP, SP4 for 2K. Then after updating that just run windowsupdate or turn on automatic updates.

Slipstreaming is probably a pita for the amount of machines you have. And if you had a lot more machines I would suggest WSUS.

 

[networkman]

Originally posted by: Parasitic
The problem is that each computer runs a different version of OS (1 Win2k Pro, 2 XP Home, 1 XP Pro) and I don't really want to go through the trouble of slipstreaming 3 different CD's but instead want to just put all the updates together on a CD.

I didn't say anything about slipstreaming, so I have no idea how that gets into the equation. :roll:

My suggestion(and it's only a suggestion) also save a tremendous amount of time for every subsequent Windows restore. Now perhaps you like to re-install Windows and each of the corresponding patch files that goes along with each version, but I don't, and I find it to be a colossal waste of time to do so.

Oh well - to each his own.

 

[jlbenedict]

Originally posted by: networkman
I find that Symantec Ghost or Acronis TrueImage (in concert with Sysprep) is very handy indeed. Just install Windows (whatever version), patch it, install whatever apps, run Sysprep, take an image - problem solved.

When Windows gets messed up, blow it away, restore from the image file and proceed.

Rinse & Repeat as needed.

:thumbsup:

 

[TG2]

The process I described works for that OS version, XP updates work on Home and Pro, 2000 works on Pro and Server.
You can also put them on a CD, but the CMD file you make would have to point to the CD drive letter, which would have to be the same on all machines.

 

[br0adband]

Originally posted by: networkman
I find that Symantec Ghost or Acronis TrueImage (in concert with Sysprep) is very handy indeed. Just install Windows (whatever version), patch it, install whatever apps, run Sysprep, take an image - problem solved.

When Windows gets messed up, blow it away, restore from the image file and proceed.

Rinse & Repeat as needed.

QFT. Acronis True Image... the lifesaver to end all lifesavers...

bb

 

[Whitecloak]

use MBSA to get the updates.

 

[jlbenedict]

Originally posted by: Whitecloak
use MBSA to get the updates.

From what I understand, that only analyzes your system and thenr reports back what updates you should/need to install. You would still have to manually download each and every update through the source links that are provided.

 

[Whitecloak]

Originally posted by: jlbenedict

Originally posted by: Whitecloak
use MBSA to get the updates.

From what I understand, that only analyzes your system and thenr reports back what updates you should/need to install. You would still have to manually download each and every update through the source links that are provided.

no. you can d/l the updates.

 

[nweaver]

Originally posted by: TG2
The process I described works for that OS version, XP updates work on Home and Pro, 2000 works on Pro and Server.
You can also put them on a CD, but the CMD file you make would have to point to the CD drive letter, which would have to be the same on all machines.

%currentdrive% ftw


Now for the million doller question(s): Why are you reinstalling so often?

I run a S/W test lab, and we have to have fresh machines MUCH more often then most other places. ususally there are 2 parts to this:
1. Imaging, you need a good imaging program, because I can restore a fully loaded XP Pro image (SP2, most updates) to 250 machines in about an hour. If there are any critical security patches, or it's been a while, then we download it to one machine, update it, push the image back up to the server before distributing it to the multiple clients. (we use Altiris 6.5)

2. Secure/know your enviroment: We will run without some patches (even some critical ones) because we know what's happening on our network, and we can minimize risk. We don't need the 2 critical IE/OE patches if we arn't using either app. Lock down your network, don't go using apps missing patches till you have them patched.

 

[Nothinman]

The problem is that each computer runs a different version of OS (1 Win2k Pro, 2 XP Home, 1 XP Pro) and I don't really want to go through the trouble of slipstreaming 3 different CD's but instead want to just put all the updates together on a CD.

So you're willing to waste hours upon hours reloading the boxes periodically, but you're not willing to spend a little time to make CDs to speed up the process?

 

[imported_shader]

you may want to look into autopatcher - http://www.autopatcher.com/