Video Screencast Help

[DS6.9 SP5] SysPrep does nothing

Created: 16 Oct 2012 • Updated: 17 Oct 2012 | 4 comments
This issue has been solved. See solution.

Hi all!

I built a brand new, from-scratch image today to reimage one of our computer labs. This image has Windows 7 x64 Professional installed. Once I got everything setup, I created a job to begin taking the image, being sure to enable "Prepare Using SysPrep". Once I assign the job to the computer, however, SysPrep starts running, and then does absolutely nothing - the Task Manager shows it as taking only 2MB of RAM, no CPU power, no HD activity, nothing. It just sits there indefinitely. If I reboot the computer after even ten minutes, it comes right back up to the login screen, still on the domain, as if SysPrep was never ran.

What might be causing this issue? Is there a way I could just manually run SysPrep but leave everything compatible with the SysPrep step in the image deployment job?

Joey

Comments 4 CommentsJump to latest comment

andykn101's picture

Check the various sysprep log files, I'm guessing there's something wrong with the unattend xml files being put down. There was a similar thread with the identical problem but DS 7.1 a few days ago.

You can certainly copy down your own unattend.xml then run a script to run sysprep manually calling your xml file.

Edit: the other thread is here, it has a few things you can look at but no answer:

http://www.symantec.com/connect/forums/71-prepare-...

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

Joey Hogan's picture

I managed to get this one working. What happened was that if I tried to run Sysprep manually, I'd get this error:

"Sysprep could not initialize. There are one or more windows updates that require a reboot.".

Since Altiris was running this in another session on the computer, the error wouldn't be visible so the task would just hang at that error message indefinitely. Running it manually though produced the error message.

To fix this, I simply went to "Programs and Features", installed Solitare, rebooted the computer, and then removed Solitare, That cleared the waiting for updates status, and allowed Sysprep to run without issue.

SOLUTION
andykn101's picture

Was there nothing in the log files saying this?

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

Joey Hogan's picture

Nothing as far as i could tell. The event viewer was empty as well. 

What I assume was happening was that since Sysprep was running in a seperate session (instead of the console session that I was interacting with), the error message appeared in this other session, so I couldn't see it, leaving it stuck there waiting for someone to click the OK button. 

As far as I could tell, and I'm assuming as far as DAgent could tell, Sysprep was still running, as the process was still there until someone clicked the OK button.