/build/static/layout/Breadcrumb_cap_w.png

Capturing win7 .wim file 64bit

Morning,

this topic is taken from another part of the forum but falls under the 2000 box.

Here is a link to the old topic.

http://itninja.com/question/sequence-question16

Basically, I have a preinstallation task that will run on a 64 bit win7 workstation that has been syspreped. This will capture the .wim file to be uploaded to kace as part of a scripted installation. I have done this successfully for 32bit win7 no problem. I created the deployment tasks just the same but when I go to run the installation task it takes about 3 seconds - creates a 8mb .wim file and says all is good. If anybody is doing this type of capturing have they run across this scenario.

Thanks

0 Comments   [ + ] Show comments

Answers (3)

Posted by: pjackson 13 years ago
Senior Yellow Belt
0
Hi Corey,

The image file is being saved to the kace petemp folder.

I could try from the command line and see if I get the same result.

Thanks
Patrick
Posted by: dchristian 13 years ago
Red Belt
0
hmm...

I wonder does this machine have 2 partitions?

Maybe the "C" drive is really that hidden windows partition.

That might explain why the imagex capture is so small.
Posted by: pjackson 13 years ago
Senior Yellow Belt
0
Thanks.

That's exactly what the issue was - Win 7 system partition. I just changed the capture to d: and everything worked just fine.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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