/build/static/layout/Breadcrumb_cap_w.png

Windows OOBE running after Sysprep

I am having an issue with Sysprep, or with the K2000...not sure which. I have an answer file setup, and run it on a machine before capture. Running with /generalize /oobe /shutdown /unattend (pointing to my XML file). Sysprep runs fine, and shuts the computer down.

Immediately boot it up into KBE and perform the capture.

However when I load that capture image onto another reference PC, it runs the OOBE after the image is finished and the PC restarts. I get asked for language settings, location, etc....all items that were in the Sysprep unattend file.

I am pretty sure the answer file works ok. I took the machine the image was captured from, and let it boot up (after image capture). It runs through a normal setup, but does NOT run the OOBE. All the settings I put in, are there.

Any help would be great. It is probably something I am missing...just not sure what. For the K2000 we are running version 3.3.43982.

Image Creation - Windows 7 Pro with SP1. Running KMS.

0 Comments   [ + ] Show comments

Answers (2)

Posted by: cblake 12 years ago
Red Belt
0
That used to happen in XP with OEM installs that had been patched to SP3 rather than slipstreamed; not sure it's related, but I'd check my media based on past behaviors...
Posted by: hutcha4113 12 years ago
Second Degree Blue Belt
0
Thanks for the response. However this is not slipstreamed image. CD based imaged was downloaded direct from Microsoft, so came with SP1.

Update: I sysprep'd it again, and uploaded. This time it worked. Strange.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ