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

Ever here of slipstreaming? [google.com]

Re:Slipstreaming

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.

Not just for servicepacks I might add

Most of the pages you will get when you google "slipstreaming" will talk about slipstreaming service packs, but you can also slipstream individual hotfixes into windows installations. Also not that Microsoft makes avaiable for download [microsoft.com] ISO Images containing every windows critical and security update. If you really want to make a slimpstreamed install of Windows with every single hotfix possible, this will save you time searching and download the iduvidual updates.

The ISO files don't help you at all.

My understanding is that the ISO files don't help you at all. They are huge because they include all languages. Each ISO file includes only the critical updates for ONE month. I know of no way to integrate them into a single CD image containing Windows XP SP2 and all the critical updates.

It is possible to download all the separate critical updates, and run them from a batch file. But that's a hassle; Microsoft does not make that easy. This is another way that Microsoft is adversarial towards customers; they waste the time of some of the best-educated people in the world.

Re:Slipstreaming

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:Slipstreaming

now go fix/explain American political "rhetoric" please.

Public rhetoric in American politics has two parts:

1. Cynical politicians pushing wedge issues to raise money for 527 / 501c4 organizations, and
2. Cynical talking heads on 24-hour news stations yelling at each other about wedge issues to raise money for 527 / 501c4 organizations.

Most of the public face of politics looks like a Jerry Springer show (and is about as real as the Jerry Springer show was) because our politicians find it immensely profitable. Divisive policies (like gay marriage or abortion) and divisive nominations (like Alito) are pushed by both sides because they're very successful fund raising mechanisms, not for ideological reasons.

But frankly, I think we have to worry a lot more about the parts we don't see. The part of the iceberg above the water didn't sink the Titanic.

Google is your friend

http://www.google.com/search?sourceid=navclient&ie =UTF-8&rls=GGLD,GGLD:2005-09,GGLD:en&q=windows+ins tallation+cd+with+recent+updates [google.com]

It's called Slipstreaming

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.

Yep

Two ways to make it easy I would think. One, use microfot's WSUS. Two, download the updates to a disc and read the documentation, you can create your own "slipped streamed" instalation media for reinstalling. I prefer the first option, use ghost to throw an image on a PC, let it sit for a day on the network, and if the GPO are configured properly, you can come in the moring to a completely updated computer.

Are the systems identical?

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.

Re:Are the systems identical?

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.

Re:Are the systems identical?

Welcome to the world of site licenses and concurrent use licenses.

Re:Are the systems identical?

"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."

Got sysprep [microsoft.com]?

Re:Are the systems identical?

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.

MSFN's Unattended Windows Install CD

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.

Slipstream and SMS

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...

GIYF

This [google.com] and this [microsoft.com] should get you started.

The essence of what you're looking for here is an unattended windows * install with hotfixes and updates streamlined. You can even go a bit further and build in additional drivers and software(JRE or AV, anyone?). In my experience as a tech, XP is the OS I find myself reload most often. One can also do unattended reloads of W98/ME/2k as well. All involve similar google searches.

Pretty much sums it up...

This is pretty much what you asked for: http://www.vorck.com/hfslip.html/ [vorck.com]

From the site:

This process details how to create a CDROM of Windows XP or 2003 that slipstreams a Service Pack and the post-SP patches...

Use something like Acronis

Even if you could get a clean (totally up to date) install of Windows, you still need to install all those other apps... I've found it so much easier to just image a base system I like with Acronis and then restore that image onto the new system. If I'm a little behind on Windows updates, it will catch up that first night when it runs update automatically at 3am.

Nlite

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

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.

This Worked Very well

This Website [nu2.nu] was very well done. It explains how to make a bootcd, and how to get the ServicePack in as well. Very quick and easy. As long as you follow a few steps. This will work for Win2k.xp..prolly 2003 as well. Hope it helps. This also works for BIOS updates et al.

You don't

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

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

NLite

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.

unattendend.msfn.org

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.

Google is your friend

Fingers broken? Why not Google the answer instead of subjecting yourself to ridicule on Slashdot?

Images

As has been pointed out earlier in this story, the best you can do is http://unattended.msfn.org/ [msfn.org]

Having said that, if you are doing this often enough why do you not have an image? Imaging spares you this work and you also get all of your applications as well. Your more likey to mess something up the more manual rebuilds you do, especially if you have a non trivial configuration. Better yet, with a little work with sysprep you can add drivers for multiple models. Bâshrat the Sneaky's DriverPacks [driverpacks.net] works for most hardware and takes minimal effort. I currently use the same image for about 15 different models of laptops. Having one image for all of my on site hardware makes updates a snap.

SGT Gruhn
BCT1, 101 ABN DIV(AASLT)

Autopatcher

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

Just ghost it if it's the same computer...

The amount of time you spend tracking down and integrating every security fix will far exceed the amount of time it takes to run Windows Update 3 times. Not to mention the fact your super duper Windows disk will be out of date by the next month anyway.

unattended.sourceforge.net

For a completely different, Free Software suggestion,
try unattended at http://unattended.sourceforge.net/ [sourceforge.net] Haven't used this at work but uses a Linux or windows server, a boot disk and you write the Perl scripts. Seems like a neat project, installs programs and does all the rebooting for you.

The university I work at recieves them from Dell with images, apps included we just do the 3 or so non-critical fixes since the image was sent to Dell.

Use VMPlayer and a WinXP VM with all the updates

Just do a virtual machine of windows XP which has the latest updates and other software installed, ( and follow the licensing issues) and then make a snapshot or a clone. This simple directory structure can be booted as a VM (virtual machine) on any Intel/AMD system, under either simple windoes or better yet, simple Linux install. this way also you can "reload" your users to the initial snapshot, and therefore a fresh but up todate Winxp install, without all the windows bureaucratic overhead. so it they keep their files on network stores for example, then they can reset the snapshot on a dialy basis and avoid Windows normal decay/corruption processes. And VMPlayer is free, as is a decent Linux, like Open SuSE.

hfnetchkpro

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

Disk images with Linux instead of Norton Ghost

For identical hardware, the best solution is disk imaging. This will also get you all the software installs and configurations, which is much more work than the basic Windows install + updates.

If you don't have Norton Ghost and/or don't want to pay for it, you can use a Linux Live CD and ntfsclone. I use a script on a USB drive based on these disk imaging instructions [alma.ch].

For different hardware, the slipstreamed install disks suggested in previous comments seem to be a good starting point.

Why we can't slipstream

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.

Use the downloaded Windows Update files.

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'.

Automated Deployment Services + Slipstream

If you haven't very demanding third-party driver support, install Automated Deployment Services [microsoft.com] (the successor to RIS) and slipstream your source. Stop wasting CDs and ISO burn time and do it in a truly manageable way. Even involved driver dependencies can be integrated, but you have to actually learn about what you're doing to make that happen. But when you need to deploy a lot of windows servers at once or the same kind over and over, this is the most straightforward way to get a consistent build and keep the patches current.

RIS & SMS

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.

A couple of options

• One, as mentioned, is slipstreaming SP2 + the hotfixes. Pretty much a PITA, since you'd have to continually update your CD as new patches come up.
• Two, is AutoPatcher [autopatcher.com]. Slipstream SP2 and run AutoPatcher after install, and you'll get 90% of the updates. Update AutoPatcher as needed.
• Three, is to hack your own. There's a couple of options for this. You can go the Unattended [sourceforge.net] way and batch/Perl script it, but you still have to download the updates. But, if you do it from a network drive, at least you don't have to reburn a CD.
• The better way, IMHO, is to use the Windows Update API [microsoft.com] to force the client to run Windows Update, download, install, reboot and repeat until no new updates are returned. I hacked a .NET program together to do just that, but it seems to have issues installing SP2. I haven't had time to delve into the problem yet though. That, and you need the .NET framework installed first - but a bootstrapping installer can take care of that.

Skillz

As a computer technician, I'd never hire you.

WSUS

Windows Server Update Services.
Instead of building a CD, I took into account that new updates will come out all of the time. Working in an environment of 150+ pcs, this also turns out to be a bandwidth hog. So, i turned to WSUS.

Think of WSUS as a local MSUpdate repo. I tell the server what upates I want, it downloads them, and then distributes them. The only other thing i had to do was to adjust every computers group policy to look for updates from my server at midnight every night. Doing this under active directory is REALLY easy.

Windows Update Server?

Maybe you could just run a SUS in house to save on external bandwith.

autopatcher

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.

Oh boy

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

Proof that it is legal

And if you really need proof that what I told you is legal. Here is a page on Microsoft's Support site that TELLS YOU: "How to integrate software updates into your Windows installation source files [microsoft.com]".

NEVER reload... use sysprep instead

Microsoft sysprep for XP [microsoft.com] allows you to create a "MASTER" image and from that master, to automagically regenerate the identical config onto a new hard drive again and again (assuming you have legit license keys, of course).

The beauty is that you can re-load not just one machine, but quite literally *thousands* from your original hard drive, reboot once, put in the license key, reboot again, and you have a fully working machine, patched to the most recent level of your MASTER.

I've used this technique since Windows 2000, and I simply do not reload Windows manually anymore.

Reading between the lines..

The OP works for a repair shop, not an IS department, so can't use a Enterprise or volume licence agreement, or add the PC to their domain (XP Home anyone?). I deploy/build images for a multinational, and in your situation I think you're out of luck - MS do not make it any easier for you than to hook the PC up to an ADSL line (install firewall, AV first) behind a hardware firewall and run WIndows Update till the PC stops bleating. It's a pain, but on the bright side you don't have to watch it the whole time. An internal WSUS server might save a bit of time/bandwidth if you can be bothered to reconfigure every PC, then change it back to standard when you're done.

Obligatory...

Get your install CD solution here [ubuntulinux.org].

Roll your own unattended install

http://unattended.msfn.org/unattended.xp/ [msfn.org] plus a convenient list of patches from http://www.kuku.co.il/windows_xp_sp2_patches.htm [kuku.co.il] , the data from your XP install CD and http://www.nliteos.com [nliteos.com] should get you a long way on the road to slipstreamed glory.

Re:Ever hear of Terminal Server?

You need to clean your shift key more.

Re:Ever hear of Terminal Server?

If you're that upset by being negatively modded, then don't post on slashdot.

Re:Ever hear of Terminal Server?

Doesnt work too well for all apps, and youre keeping all your eggs in one basket there. Performance becomes an issue fast. Not to mention upgrading or restoring from backups becomes impossible without disrupting everyone's desktops settings and other files.

Solutions like yours exist already. There are terminal client versions of XP and other companies including sun were selling real cheap graphic terminal thin clients a while ago. Not a smashing success.

And yelling and screaming on slashdot doesnt convince anyone at all.

Re:I pity those serviced by this computer technici

Well, every technician starts somewhere, don't be such a curmudgeon. While I agree that slipstream is a valuable (and basic) skill for any tech nowadays, I'm surprised at how many I've met that have never done it or knew it could be done!
That said, I've picked up a couple of links in this thread that were new to me. I was satisfied with the MS tools and method (they did the job) but now I'm interested in trying out some new tools.

You learn by doing. You learn by asking. Just don't stop learning.

Re:Terminal Server?

Install Cross-Over Office or WINE if you need to and your Windows applications work..
No more issues. Yeah, sure looks like you've tried it...

Re:Hmmm...

We are not allowed to slipstream for legal reasons. We have to use the customers original Windows CD. Ask Microsoft.

Re:A solution for recovery CDs

You are SOL. You don't have a "full" copy of Windows, just a restore disc. You can't even legally borrow a friends disc to do it.

Re:A healthy solution

I know you got modded ``off topic" for your comment, but this was pretty much my response to the 100s of complicated, time-consuming, and ultimately inadequate solutions too. (Well, not exactly; I didn't think of slack specifically, but I did have the ``why not run *BSD or GNU/Linux?"

Re:Norton Ghost

If Norton Ghost would work, so would a Linux boot CD, probably more flexibly, too. Unless Norton Ghost has a way to get around the indigestion Windows gets when you change the IDE chipset out from under it.

Re:That's odd

I agree that you can always save an installation, but look at it from the point of view of a shop. We could do that, but then we would need to test every aspect of Windows, all the installed apps, and hope future updates won't break. After a massive virus/spyware infection, it can be hard to make Windows perfect again, even after doing a refresh install.

On top of that, we never charge more than a certain amount of labour (because PCs are so cheap, it's pointless trying to charge more than the cost of a new one in most cases). So, sometimes, it's better just to do a fresh install, and not have to worry about the customer comming back because something doesn't work in a weeks time.

Re:That's odd

What's the longest amount of time you've ever taken to fiddle a Windows back to health?

What's your hourly rate?

There is a point where FORMAT C: is the only sensible fix.