Sysprep'd Vista SP2 machine locks up on first reboot.

[woody.cool]

Hi all,

I'm in the process of making a Vista SP2 image of my laptop, which is a Dell Latitude D610.

I've installed the updates and SP2, then ran SYSPREP with OOBE selected and Generalize ticked.

Upon first reboot (after Sysprep has run and after I've taken my image), the machine just stays on the 'Please wait while Windows continues setting up your computer.' screen

After about 30 minutes, I got bored and powered down the machine.

I tried it again, for a second time, but I got exactly the same thing.

If I don't tick Generalize, it works fine, but I want the Generalize option ticked so that it clears up the crap left behind and makes it 'unique' (I can then use the same image on other simialr machines of the same type/hardware config)

Any ideas?

Cheers

woody.cool

[cluberti]

You probably want to access that HD from a boot disc or another system and get the Panther and CBS log files to review what happened during sysprep.

[woody.cool]

.... get the Panther and CBS log files to review what happened during sysprep.

Where do these logs live? Are they in C:\WINDOWS\SYSTEM32\SYSPREP\ ???

[Tripredacus]

.... get the Panther and CBS log files to review what happened during sysprep.

Where do these logs live? Are they in C:\WINDOWS\SYSTEM32\SYSPREP\ ???

yes that and c:\windows\panther

[woody.cool]

.... get the Panther and CBS log files to review what happened during sysprep.

Where do these logs live? Are they in C:\WINDOWS\SYSTEM32\SYSPREP\ ???

yes that and c:\windows\panther

Cheers!

Didn't get chance to do this last night, but will give it a shot tonight if I get chance.

[woody.cool]

I tried it again, only this time, there was no problem ..... although it took an age to complete the step mentioned above.

[Tripredacus]

I tried it again, only this time, there was no problem ..... although it took an age to complete the step mentioned above.

Even though it completed, the log files should show where the lag happened. I've seen some systems take a long time detecting the display adapter and cause this issue.