For on-site techs, performing clean installs?

[LABFE]

Currently, when I determine that I need to perform a clean install I take the PC with me and deliver it in the following day or two because it takes approx. 5 hours with a regular Wiindows w/SP ISO, Snappy Driver Installer, and WSUS Offline. I'm wondering how other on-site techs do clean installs? Do you do the same thing as myself or I've read here on Technibble about creating current Windows images to use for installations; thereby, eliminating the need to wait on updates to download/install each time. Other on-site techs maintain current Windows images for clean installs? I've learned that a clean install can be performed in less than 1 hour with a current Windows image this way; which would allow the clean install to be performed on-site. How are you creating and keeping your images updated? Just looking for the best practice for clean installs.

*By the way, this thread isn't for a debate about when a clean install should be performed; there are other threads for that.

 

[MichaelBits]

I use imagex and create install images.
I then just plug in my drive with winpe and my images and apply the image needed.

I can generally have a system loaded and ready to go with drivers and current updates in less than 30min (depends on speed of system). If I need to do client data as well, extra time depends on how much data they have.

I update my images whenever I have a slow day or several updates have come out to warrant updating them.

I plan to play with using pxe boot and something like cruciblewds to apply images. Hope to test that setup sometime this month if I have time.

 

[LABFE]

Good info, thanks for that.

Anyone using any other methods for creating, maintaining, and installing 'current' Windows images for clean installs?

 

[Mainstay]

I can generally have a system loaded and ready to go with drivers and current updates in less than 30min

Woah.

I think I need to spend some time and review your technique.

I use ISO's off of a Zalman 300, Snappy Driver off of a 16 GB thumb drive (kept up-to-date), and Windows updates are done as needed (i.e., I prove to myself that they are running and that the system is safe, and then leave them to naturally install).

But 30 minutes.... no.

In fairness, I usually do a TON of personalization, making the system as close to their original as possible.

So I am working away at file transfers and setup of programs while drivers are updating in the background.

 

[Slaters Kustum Machines]

Woah.
In fairness, I usually do a TON of personalization, making the system as close to their original as possible.

Fab's is quite good at helping in this area, granted it can't do everything, but copying data back and some personalization, all while being automated is a big help.

 

[cypress]

Yeah Fabs does an excellent job. Backing up the data, then nuking and paving and restoring it back, the data goes right back where it was and the client can never tell the difference. They just want to know their Word Documents are in the same spot they were last time.

Generally I do Nuke and Paves In Shop, just because I want to do a deep diagnosis and run a backup clone.

 

[MichaelBits]

Using imagex and a wim file for applying windows installs is simple and quick. You keep your wim file (image) up to date with current updates and you never have to install updates after applying the image. You can also include flash, java, whatever you put in your general installs. Just don't include any Anti-Virus in a wim (image).
Applying the image usually takes 5-10 min.
I then use snappy driver, then fabs if I had to save data from an old install or other system.

 

[jmitservices]

Using imagex and a wim file for applying windows installs is simple and quick. You keep your wim file (image) up to date with current updates and you never have to install updates after applying the image. You can also include flash, java, whatever you put in your general installs. Just don't include any Anti-Virus in a wim (image).
Applying the image usually takes 5-10 min.
I then use snappy driver, then fabs if I had to save data from an old install or other system.

Exactly how I do it with WDS. Its super quick!

 

[HFultzjr]

Anybody up to doing a DETAILED process to be added to our resource section?
I'm obviously lacking in this area.
I only do in shop and taking much longer.....most of the time just waiting for things.
I'm currently doing it along the lines of Mainstay.
Thanks.

 

[MichaelBits]

There was a posting with lots of info about it (using imagex) somewhere on this site... a little busy now to find it...
Microsoft actually has a few good articles on it as well.

If I have time, I may try to write up a quicky example later.

 

[allanc]

There was a posting with lots of info about it (using imagex) somewhere on this site... a little busy now to find it...
Microsoft actually has a few good articles on it as well.

If I have time, I may try to write up a quicky example later.

I would also appreciate that very much!

 

[OaksLabs]

If you but ToDo Backup Advanced Server, the whole disk backup option gives you a "universal restore" option that will do a very similar option to the sysprep/imagex/wim dance, and it is PXE bootable (just hit a tick box on the server). It removes both drivers and Windows activation on restore. I prefer this method, just so user account specific settings (like branded desktop wallpaper) are already done (whereas with sysprep you create the user account each time).

 

[CLC]

Anybody up to doing a DETAILED process to be added to our resource section?
I'm obviously lacking in this area.
I only do in shop and taking much longer.....most of the time just waiting for things.
I'm currently doing it along the lines of Mainstay.
Thanks.

Yes Please!

 

[trevm999]

Once again, I'll be the stick in the mud pointing out that technically you need imaging rights in order to use this method to load Windows. Imaging rights comes with volume licensing. You are supposed to reload using the OEM restore image otherwise.

It is a lot faster though

 

[ChrisTech]

Yes Please!

+1 !

 

[Diggs]

I won't do a N & P at a residential customer and only clean installs if there is a total hard drive failure with no life in the old drive and a new drive is being installed. Travel time in my area is minimal so almost all installs are done on the bench in our shop. At the same time it gives adequate time for identifying and cloning customer files and data off the old and in the case of failing/failed drives we can drop the drive in a dock and let a server run forensic recovery overnight(s). Yes, more hassle on our part but I have customers that fear the "big box" techs whose every answer is N & P as fast as possible. We get a large amount of business because of this. And, providing the customer with their files they thought they lost is very billable. (Be careful, sometimes those files are supposed to be lost - heh...)

 

[CLC]

Once again, I'll be the stick in the mud pointing out that technically you need imaging rights in order to use this method to load Windows. Imaging rights comes with volume licensing. You are supposed to reload using the OEM restore image otherwise.

It is a lot faster though

You shush

 

[KurtisK]

Once again, I'll be the stick in the mud pointing out that technically you need imaging rights in order to use this method to load Windows. Imaging rights comes with volume licensing. You are supposed to reload using the OEM restore image otherwise.

It is a lot faster though

I've always wondered about that myself. You see lots of recommendations on this site to use .wim or PXE methods to speed up Windows installations. Maybe I'm not doing something properly, but 95% of the machines that come through our shop are OEM installations and I have not been able to get the product key on the COA to authenticate using those methods.

 

[pcpete]

Imagine a life where every reload of a hosed recovery partition started with ordering oem media. **Shudder**

 

[chelax]

A detailed work flow would be genius, if anyone has the time to type something up.