Installing Windows with Recent Updates?

MoJo asks: "As a computer technician, I have to re-install Windows often. It takes three attempts to complete Windows Update (get latest update software, validate Windows, download updates). It seems like all this clicking could be scripted somehow, but I can find no-one who has found a way of reducing the whole painful affair to just one or two clicks." Is there a way to build a Windows installation CD that includes the most recent set of updates?

Slipstreaming

[ckswift]

Ever here of slipstreaming? [google.com]

It's called Slipstreaming

[Anonymous Coward]

A lot of people just use it to update with SPs, but you can use it for regular updates and drivers, too. If you need help, you can use a utility like AutoPatcher [neowin.net] or nLite [nliteos.com] to get you started.

Are the systems identical?

[eta526]

If all the hardware is the same, use Norton Ghost to create an image of the hard drive. Store this on an external drive or a network share and use this image on every computer. I did this for UMR (University of Missouri - Rolla) for the computer labs (over 900 computers), and it's really easy to pull down the old image, apply the new updates, and create a new "clean" image that can then be distributed to all the other systems.

We used BartPE or a bootable DOS disk (if the DOS network drivers were available) to boot the computer onto something besides the hard drive in order to create or restore an image.

If the hardware's different, you have to use Sysprep, but I haven't messed with that.

MSFN's Unattended Windows Install CD

[UnderScan]

Its not that hard to use google. Do you realy want it that bad but are unwilling to search for it?
MSFN's Unattended Windows : Introduction [msfn.org]

Have you ever wanted a Windows CD that would install Windows by automatically putting in your name, product key, timezone and regional settings? And have it merged with the latest Service Pack to save time? Followed by silently installing all your favourite applications along with DirectX 9.0c, .Net Framework 1.1 and then all the required hotfixes, updated drivers, registry tweaks, and a readily patched UXTheme.dll without any user interaction whatsoever? Then this guide will show you how you can do just that! Through the course of this guide, you will create a CD that does all the installing for you. The CD will be fully updated with the latest hotfixes, and install all your programs for you.

Re:Slipstreaming

[Stevyn]

I've slipstreamed service pack 2 onto the windows xp cd, but you still have to go through the process the poster is talking about. I don't know if you can slipstream individual patches, however, even if you could, you'd still have to do it a few times a month. I think the poster is asking about a general script that would do this without human intervention, whereas slipstreaming still takes time.

Slipstream and SMS

[Centurix]

If you manage a lot of desktops, Microsoft's System Management Server (SMS) is a good way to go. You get used to writing scripts for it after a while.

I'm pretty sure SMS is still an up to date product from Microsoft, unless they've developed something else in the last couple of years...

Comment removed

[account_deleted]

Comment removed based on user account deletion

Nlite

[October]

Nlite [nliteos.com] is a great tool designed exactly for this. I've used it for several installs, and have created a CD that will install XPSP2 with hotfixes and all my drivers, and none of the extra crap that gets installed by default. It starts up in my LCD's native res, includes all my critical apps (firefox, etc.) right on the CD, and is completely unattended.

RyanVM's update pack

[Mitchell Mebane]

As others have mentioned, it is fairly easy to slipstream SP2 into an XP CD. But if you want to integrate the more recent updates, there's really only one option. RyanVM's Windows XP Post-SP2 Update Pack [ryanvm.net] does exactly what you want and works like a charm. There are even third-party addon packs which let you add other interesting things to your XP install CD.

Re:Slipstreaming

[ajayrockrock]

Slipstreaming is great. The windows guy at work does it for a bunch of our servers and he also rolls in his own device drivers into the system as well so there's no searching for floppy disks to install the RAID/SCSI drivers. He got the idea from this Maximum PC article:

http://www.maximumpc.com/2005/01/how_to_slipstre.h tml [maximumpc.com]

--Ajay

mnb Re:Slipstreaming

[Anonymous Coward]

Why would you need to slipstream a few times a month?
Microsoft only releases patches the second Tuesday of the month.

You don't

[55555 Manbabies!]

You don't waste time installing the patches, you let WSUS do the work once you hook the computer on your domain.

You can also slipstream hotfixes and apps

[hillct]

While slipstreaming service packs is a common practice, you can also slipstream hotfixes. Hack when I was in IT support we used this great script [wisc.edu] to automate the process. Some of the other links I still had bookmarked may be of value to people who not only want to slipstream service packs/hotfixes but also build an unattended installation CD. In our case we installed all the apps common to our PC images (except for office) from one CD. We threw the CD in, booted from it and came back 2 1/2 hours later to find a fully installed desktop with all our standard apps. This method is superior to using Ghost or other imaging software when you have a heterogenius enviroment where PC hardware varies drastically from depertment to department or desktop to desktop.

http://www.nu2.nu/bootablecd/ [nu2.nu]
http://www.microsoft.com/technet/prodtechnol/ie/ie ak/default.mspx [microsoft.com]
http://unattended.msfn.org/unattended.xp/ [msfn.org]
http://www.appdeploy.com/packages/ [appdeploy.com]

This last link related to a commercial software distribution enviroment but but it includes an archive of the known switches accepted by various installers to make them silent. The technique we used was to use the unattended.txt file to add a RunOnce registry entry, to regedit (to marge a secondary gegistry file containing other RunOnce entries) to be executed on the second reboot to silently install our list of apps, where the installer commands used included the switches detailed on the appDeploy website (and many other palces across the web).

There are a relatively small number of installers out there that take a relitively well known set of switches to make the installation silent (accepting all the defaults). These methods saves us thousands of man-hours in PC deployment in the two years they was in use.

--CTH

Re:Are the systems identical?

[RESPAWN]

If the hardware's different, you have to use Sysprep, but I haven't messed with that.

Actually, it's always a good idea to sysprep on XP since if you don't you'll end up with multiple computers on the network with the same SID. That really becomes a problem with AD since that's how it uniquely identifies all of the computers in the domain.

NLite

[Timeburn]

For those with never enough time to be as nitpicky as they'd like:

Nlite [nliteos.com] is a wizard which will prep custom XP or 2003 install discs for you. It will slipstream service packs and hotfixes in, add drivers (including storage or net drivers for the initial installer), remove drivers and services, allows you to setup unattended install, plus has tons of other tweaks and adjustments. You can then install directly from the modified install folder, or have Nlite prep an ISO and burn a bootable CD.

I recently used it to strip XP down to run in under 64MB RAM on an older laptop. Runs like a charm, and needed no updates when installed.

Also perfect for preparing an initial install image for use with RIS and sysprep.

Of course, you still have to find and download the hotfixes, but I think some of the other posts in this discussion have pretty well covered that part.

Re:Are the systems identical?

[RESPAWN]

That doesn't sound very legal. Even if you do have a license for each computer, as far as I know, there's no way to change the registration number of a Windows install once it's been installed and a ghost image has been made.

You've never heard of a volume license key (VLK) or of Microsoft's volume license program? The VLP version of XP (like the OEM versions) requires no online activation and uses different licence keys from the standard versions of XP. The CD-Key itself isn't your actual license to use Windows. It's merely one way of ensuring that the media was obtained legally. In the corporate world, you buy the VLP version of XP, and Microsoft emails you a CD key to use for all of your computers.

Also, changing the CD key is trivial. You just run Sysprep (found on the Windows CD) and in the course of running it, Sysprep will ask you for a CD key. This is the same software that you should be running on the PC before you make your Ghost image of it if you plan to join it to a domain.

Not to mention you then legally need a legit copy of Norton Ghost and everything else you might decide to include with it for every computer you install the image to. Although I have done zero research on the subject (Except that You'd need many licenses for Ghost), so this is all just assumption here.

I'm a little hazy on the legalities of this as well. The way it's always been explained to me is that you need a licnece of Ghost to create an image. Also, if you're running the full-on Windows client, you will of course need a license for that. However, I've always been told that when restoring an image to a PC, it is legally permitted to use the DOS version of Ghost without a licence for that PC. Now whether or not that's true, I'm not sure. I've never bothered to read the licence documentation, instead trusting the word of my higher ups.

unattendend.msfn.org

[duffbeer703]

This project describes how to do what you are talking about.

If you use ghost images, just setup a baseline PC that uses automatic updates or WSUS. Everytime updates are released, run sysprep and ghost the machine.

Re:Nlite

[rhandir]

I've used nlite. It is free as in beer, and worked well for me.

Three good things the previous poster didn't mention:
1. Nlite is menu driven. You can configure almost every aspect of the install, including which services are set to run manual or automatic. No funny stuff with regedit, no hexediting etc.

2. You can bypass the check for adequate memory/hd space to install xp on systems that shouldn't be able to run it.

3. If you are comfortable editing install exe's (or trust other people's edits) you can slipstream in applications. (Though you'll need to have the cd keys on hand when the system first starts up.)

Con:
Nlite uses .NET ver 2.

Autopatcher

[Lord Kano]

I'm sure that there is a more elegant solution, but I use Autopatcher [autopatcher.com], when I need to bring a system up to date.

Slipstream SP2 into an install CD. When it's installed copy over and run Autopatcher.

If I had to do it more often, I'd probably look into a better way but the 4-5 times a year that I need to install XP doesn't make it worthwhile.

LK

hfnetchkpro

[Kris_J]

Google for hfnetchk, hfnetchkpro, shavlick or shavlik. Sorry I'm not on a real PC to make looking that up for you easier.

Re:Slipstreaming

[cowbutt]

Combine some selective slipstreaming with the unattended build facility, e.g. using http://unattended.sourceforge.net/>unattended. My colleagues slipstream service packs and critcial hotfixes (i.e. those that can result in ones machine being 0wn3d during the install) into the installation image, then have a manually-updated .CMD script that runs on the first boot to bring in the others.

Re:It's called Slipstreaming

[Anonymous Coward]

You might want to try the current version of AutoPatcher: AutoPatcher XP January 2006 [neowin.net]

It would be nice if Microsoft would make it easy to script the install onto one CD (or DVD). It is a sort of a drag to have to rely on a third-party for what Microsoft could do easily if they didn't want to sell MSCE and other worthless degrees by making sure Windows is (or seems) much more complicated than it can (or should) be. Case in point: here's [microsoft.com] how Microsoft expects you to "integrate software updates into your Windows installation source files" (please, read the document before you comment on how nice they were to make it easy for us).

Why we can't slipstream

[AmiMoJo]

Just spotted that /. posted my question, yay!

We can't use slipstreamed CDs. Microsoft says that it violated the terms of the licence agreement. To reinstall, we need the customers original CD and COA sticker. If they only have a restore CD which doesn't work, they are SOL and need to buy a new copy of Windows.

We have already been fined over this. We phoned up the Dixons group tech support line to see what they said, and they told us we should "borrow a friends CD". Luckily, we taped the conversation and sent a copy to Microsoft. Well, if we are gonna get screwed, at least everyone should be on a level playing field.

Re:Slipstreaming

[AmiMoJo]

Yes, I have.

Microsoft told us we couldn't do it. When a customer brings a PC in for repair. we have to use their original Windows CD and licence COA. We can't use ours. If they have recovery discs, they are SOL. If their disc is scratched, they can buy a replacement for £15.00, no CD-R backups allowed.

We even got fined over this. We used to have loads of slipstreamed CD-Rs. Instead, we pull a gig a day of updates from microsoft.com now.

Re:Why we can't slipstream

[AmiMoJo]

Microsoft like to "audit" small shops. Basically, if you don't like it, they don't give you the tools you need to do your job, or ask Trading Standards to take a look.

They also seem to be able to tell if you are not using your original install disk. I think maybe it has something to do with the licence codes. If you take a Compaq machine with a restore CD and install a fresh Windows from an OEM CD, it won't activate over the net. You have to call them. They ask you lots of questions, and then validate it anyway. But somehow they seem to know it was a Compaq copy of Windows (they as the machines brand to make sure the COA sticker wasn't transfered).

Technically, if you have a restore disc or OEM Windows and your mobo dies, you are supposed to buy a new copy of Windows.

RIS & SMS

[TheEvilOverlord]

It amazes me no-one has mentioned RIS [computerpe...ance.co.uk].

I'm no fan of MS, but the one place I've worked where it was used, it was invaluable.

Put the machine GUID into Active Directory, PXE boot the machine, select the OS image, it formats the drive and puts the image on. You can add whatever updates/drives you want to the image. The rest can be delivered by SMS (Systems Management Service), it can be very slow though.

The other excellent option I've seen is a custom linux partition on each drive that has a modified version of init, boots and checks the windows partition with an image on a remote network drive using rsync. Once done it reboots with the windows partition selected for default boot.

All the admin need do is update the image and reboot the terminals.

Use the downloaded Windows Update files.

[Anonymous Coward]

We build pc's for business and home use. Due to lack of time for building and maintaining a OEM installation server, my co-worker installs all machines from an installation cd.

Now and then, Windows Update downloads are pretty slow. Therefore i have copied everything Windows Update downloads to a fileserver and created a batchfile with which we can install the patches. Ofcourse this is a bit time-consuming and it still has to be maintained each month, but it's quicker than letting Windows Update download and install everything for every pc we build.

These are the steps to follow:

• Install Windows XP using the cd.
• When it's running, install the latest servicepack (SP2 at this time). This can be downloaded from Microsoft once, burned on a cd or copied onto a fileserver and installed manually.
• Open Windows Update and write down which updates it will download and install.
• Let the updates download and install.
• When it's downloading and installing, copy everything (folders and files) in C:\Windows\SoftwareDistribution\Download to another folder as it will delete the folders and files it had installed. These folders contain all the new patch files and an installation program.
• Open the folder in which the folders and files have been copied.
• Open each folder (every folder has a name consisting of 40 hexadecimal numbers) and look in the 'update' folder for a file (for example 'kb873339.cat'). This tells you the patch number.
• Rename all folders according to the KB number. I have called the example folder 'wu-kb873339'.
• Look at the files themselves (also consisting of 40 hexadecimal numbers). Some of these will be textfiles, which can be removed. One of the files might contain the Microsoft Windows Malicious Software Removal Tool, which can be placed in a subfolder and renamed to an EXE file (for example mrt200601.exe). This file will probably be updated every month.
• Create a batchfile and put the following command in it for each folder: start /wait WU-KB873339\update\update.exe /q /z . The flags /q /z will make the update install quietly without rebooting. This will install KB873339. Copy this line, paste it and change the number for the next patch, until all of them are in the batchfile. Save the batchfile.
• Add the Microsoft Windows Malicious Software Removal Tool exe file and add the flags /q /z for quiet installation without reboot (for example mrt200601\mrt200601.exe /q /z ).
• Copy everything to a fileserver which you can access from a freshly installed pc or burn it on a cd-rw (it will be about 150 - 200 Mb because every folder contains several files which are the same).

On a freshly installed pc, which has the same servicepack, you can now copy that folder to the pc, and run the batchfile to install all updated (or perhaps you can assign a driveletter to the share so you don't have to copy the files). If you burned everything to a cd, you can probably start the batchfile without copying everything, i never tried that myself.

Note that you should make a different folder like this for each windows version (pro, home and others).

Anyone who wants to try this should thoroughly test it. You can verify if the patches have been installed by looking at the list displayed in 'Add/Remove programs'.

use a router

[TheSHAD0W]

Just to go off on a tangent...

My colleagues slipstream service packs and critcial hotfixes (i.e. those that can result in ones machine being 0wn3d during the install) into the installation image...

I recommend doing all your installation behind a cheap cable/DSL router; this will block any incoming traffic from reaching the machine. Unless you decide to go surfing around on suspect web sites with the incompletely updated machine, you're pretty much guaranteed not to get 0wn3d.

Re:use a router

[DeanPentcheff]

Treat your internal network the same way you'd treat the Internet: plug in a cheap firewall box (or use a similarly set up Linux box to do the networking). Do your installs while you're NATed behind your own little firewall. Tighten up the boxes, and only then release them to be plugged into the Great Unwashed University Network.

autopatcher

[XO]

google for AutoPatcher.

Aw, heck, I guess I'll google it for you.

http://www.autopatcher.com/ [autopatcher.com]

  That'll hook up your new windows installation right quick.

Re:Slipstreaming

[m0ng0l]

Leaving aside the problems of customers and their CDs, or lack of...

Once way to avoid downloading gigs of data from Windows update, is to set up a server running Windows Server Update Services. This essentially brings the Windows updates to a PC on your network, from which client stations can grab updates. It does require you to setup a Group Policy pointing to the internal server, and only works for automaticly recieved updates, not when someone clicks on the "Windows Update" icon or link. But you can setup a cmd script to force the PC to check for updates, and could also export and import the GP settings, so that when you hand the PC back to the client, everything works the original way.

You can even tell the WSUS machine if you want it to download the updates and store them locally, or simply tell the client PCs what updates they can or cannot download, and let them get them from MS (which in your case would defeat the purpose) Also, WSUS can be downloaded and used for free from MS (frightening, isn't it?), although it does require either Windows 2000 or 2003 Server, and either SQL Server, or MSDE (if no SQL Server available)

Re:options Re:Slipstreaming

[skraps]

Most windows programs will accept both slashes and dashes.

Oh boy

[venuspcs]

I have been a computer tech for 11 years now. I have slipstreamed many a cd for purposes like this. Even before slipstreaming was a possibility from Microsoft I was doing it by hacking the iso and putting the newer files into it. With that said, a little creativity and Googling will do wonders for you in this case.

As far as it not being legal to use your own disk to install WindowsXP +SP2 +Updates is BULLSHIT! It is perfectly legal as long as your installation meets a couple requirements.
1.) The installed Operation System is the exact same one as originally came on the system when purchased from an OEM like Dell, Gateway, etc. Meaning if it an OEM system you are installing an OEM version of the OS. If it is a clone system that originally came with a RETAIL version of the OS you must install the RETAIL version of that OS. If it was built/purchased for a business with a VLK license you must install the VLK version of the OS.
2.) You must either return the comptuer to the user UNREGISTERED/ACTIVATED depending on which version of the OS was installed; or you can use a do one of the following:
a.) Use a customer supplied license key to register the OS for them.
b.) Sell the customer a new license key (which you can buy in bulk from Microsoft) and use that
license key to register/activate the Operating System.

With that said, it is possible to create a boot cd that will have every possible version (OEM, Retail, VLK) of WindowsXP/2003 with all the service packs/updates already included. Furthermore, it is possible to make each of those install unattended without entering registration/activation info during setup so that once the OS is installed it has all the updates but has not been activated or registered (doesn't have a licence key entered).

I have one of those CD's that has all three versions of XP SP2, all three versions of 2003 SP2 and all three versions of MCE 2005 SP2. It is perfectly legal to own and use as long as the proper license key is used before returning to the customer or you return it to the customer with no license key used.

To make one of those disks, you can follow a fairly easy process:
1.) Make a folder on your hard drive (in the root for ease) called TechCD
2.) In the folder TechCD create a folder for each OS you want on the disk, like:
a.) Windows XP SP2 (OEM) - Folder name: xpsp2oem
b.) Windows XP SP2 (Retail) - Folder name: xpsp2ret
c.) Windows XP SP2 (VLK) - Folder name: xpsp2vlk
d.) Windows 2003 SP2 (OEM) - Folder name: 2003sp2O
e.) Windows 2003 SP2 (Retail) - Folder name: 2003sp2R
f.) Windows 2003 SP2 (VLK) - Folder name: 2003xp2V
g.) Windows Media Center Edition 2005 SP2 (OEM) - Folder name: mce5sp2O
h.) Windows Media Center Edition 2005 SP2 (Retail) - Folder name: mce5sp2R
i.) Windows Media Center Edition 2005 SP2 (VLK) - Folder name: mce5sp2V
3.) Then copy all the files from each Install CD into the appropriate directory. Don't copy the non
required stuff like Tools, etc. as it will make the CD Image to large to fit on 1 CD.
4.) Now use slipstream the appropriate service packs and updates into each one. (Googling Required)
5.) Now create you a Boot Image with a menu to select which OS/Version to install. (Googling Required)
6.) Now use a tool like UltraISO Media Edition to create a Bootable ISO using the boot image
you made in step 5 and the various folders you created in steps 1-4. I suggest ULTRAISO because
it has a feature (which you have to turn on in setti