Windows 7 Image - Customize in Audit Mode with Sysprep

Maybe you should be looking here for more Macrium info: Imaging with free Macrium
There are two link there for a WinPE iso to avoid the big WAIK download.

I've been a bit preoccupied as told here, not having time to read all your posts. I have some time now, give me an hour or so to read what you have posted and I'll reply.

nkaufman said:

Hello,

Faced following issue while following this tutorial.

First, Macrium Free seems to hang up at about two-thirds of the way, while installing along with other software. clicking on cancel button, I got a dialog box asking if I really wanted to close install...
...

I am not qualified to advice in Macrium issues. I can only say I have never had any issues in installing it.

nkaufman said:

Another issue,

came to last step to let Sysprep (Step 11), did everything and see "Sysprep is working" dialog but behind it another dialog box has opened "Uninstall Drivers" that says - "To proceed with the uninstallation, first close all applications, then click the Ok button below." And sysprep has been running for a long time.

Is this due to the fact that I installed custom drivers as well while installing applications?

Thanks,

nkaufman said:

Google search suggests that the answer file needs to be modified if using custom drivers. This is a very important of information.

The whole idea of this tutorial is to create a hardware independent system image, which can then be deployed (installed) on any PC capable of running Windows 7. The Generalize switch used with Sysprep command removes all traces of hardware drivers. Hence, it's quite obvious you should absolutely not include any custom drivers (not install them) in this image, they will only cause problems and will in any case be removed when the image is sysprepped.

nkaufman said:

Hello Kari,

Just to confirm that there is no oversight, the last screenshot in Part 5, closes theSysprep tool instead of setting it to Audit Mode. Is that correct?

Thanks,

Closing the dialog by clicking the Cancel button closes Sysprep process, it's totally unimportant what boot option is selected.

Each subsequent boot will in any case return to Audit Mode if the system has not been especially told to boot to OOBE.

ignatzatsonic said:

I've never bothered with Sysprep and not sure why you are involved with it.

I am quite surprised to see a statement as the above, especially coming from a senior geek who most certainly has above average Windows knowledge.

I will answer that on behalf of Nkaufman: Sysprep is the most versatile, amazing tool to customize and work with Windows images. The fact that you do not know it is no reason to say something like that; reading between the lines you are saying "I don't bother with Sysprep, therefore you shouldn't bother with it".

Kari

nkaufman said:

Kari said:

The whole idea of this tutorial is to create a hardware independent system image, which can then be deployed (installed) on any PC capable of running Windows 7. The Generalize switch used with Sysprep command removes all traces of hardware drivers. Hence, it's quite obvious you should absolutely not include any custom drivers (not install) in this image, they will only cause problems and will in any case be removed when the image is sysprepped.

But wouldn't this constraint be a drawback to the approach? When systems are built with customized drivers, it would help to perhaps modify the answer file and see what happens. That is what I plan on doing as an experiment and will post my findings here.

Looks I need to go a bit deeper, explain more in-depth.

Personally, my interest in deploying (installing) Windows is predominantly based on one general idea: to create a "perfect" hardware independent image to be used in all installs, be it new or re-install, to save my time and efforts. This simply because of my own home network, I have too many Windows computers and do too many installs and re-installs that I would be lost with normal fresh installs or hardware specific images for each respective computer and hardware setup.

My home network, only an iPad and iMac which both were not connected at the time of the screenshot missing from this, to show what I mean:

This, my egocentric need to bring customization to a level where it benefits me and saves my time and efforts has made me to compose several Sysprep related tutorials, to show not the correct way but my way to do stuff. The idea behind each tut is the same: how to do various "Do it once and forget" stuff using Sysprep. As in this tutorial, following these instructions I need an hour and a half (unedited length of video 1, Part Two) to create an image which contains all customizations and software I need and want it to contain, and then each new or re-install will be simple: restore the image in under 15 minutes, then just install hw drivers to that specific system.

OK, I can already feel the first counter argument: "But I only have one PC and need this image only for that". Wrong attitude, I would answer if that argument was ever posted here; you never know it with computers, it can be that your $2,000 custom built rig burns down the very next day you got it, or that you'll win in lottery a week after and decide to change the motherboard and processor to those you really wanted to begin with but could not afford.

All work with a custom HW image would then be for nothing and you'd had to start from beginning.

That all being said I am absolutely totally not interest in creating images containing custom drivers. That comes from my own personal opinion, and I have no time nor interest in writing tutorials about something I have no interest for, or to include all possible and according to me not interesting or needed options to them. I will gladly welcome other geeks to write those tuts, I will not do it.

Very sincere,

Kari