/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hi Everyone,

I am in the process of prepping a Windows 7 Image to load up to KBOX 2000. I am now on Image version 5 (as in 5 attempts) due to some issues with the Unattended file I was using.

I have cleared them all up, but cannot get rid of this last message that keeps happening: "Windows could not parse or process unattended answer file [Specialize]".

To give you an idea of what I am attempting I do the following:
1)Log into a fresh install of Windows 7, using crtl-shift-f3 to get into Audit mode.
2)Fully patch the OS.
3)Install software specific to our Agency
4)Setup the Administrator profile (local).
5)Copy the unattend file onto the C:\ and run sysprep /generalize /oobe /shutdown etc.

That part all works fine. No errors reported.

However on a reboot of the newly sysprep'd OS, it goes into a boot loop. It will generate the error message above first (after it finishes installing all devices, etc.), and restart. Then on restart it will advise that the OS restarted at a critical point, and is now damaged.

I think it has something to do with the CopyProfile=True setting but not 100% sure. I am going to try again, based this KB article from MS: http://support.microsoft.com/?id=973289, where it appears you must use full path to run sysprep...don't know why that would make a difference, but I have seen posts from other indicating the same.

On that note the MS article advises that the PC should be allowed to boot up (run sysprep with /reboot instead of /shutdown) to verify that the copyprofile worked. Does that not mess up the image to KBOX? Or if it works, do I sysprep it again?

Anyway...I am at a loss right now, so any help would be great.

Hutch
0 Comments   [ - ] Hide Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity

Answers

0
I found that taking the Windows key out of the "Specialize" part of the unattended XML script made things work for me when I got that same message.
Answered 09/07/2011 by: NHayes
Senior Yellow Belt

Please log in to comment