Having trouble capturing image

[MikeAtTrs]

I have been trying to capture an image from one laptop of a batch of 36. I would like the image to have all drivers retained and software, so that I can push to the other 35 - surely this is childs play to WDS/MDT2012, but I can't seem to find the right command line for sysprep to execute. They are Win 7 64 bit. I don't want to use the '/generalize' tab, as this apparently strips the drivers. I understand that it also needs to run in order to strip other things like IDs etc. So is there a way to capture my image as-is, so I can have it ready for the other identical laptops? BTW, I wasn't able to run the basic PE install from WDS/MDT for various reasons, otherwise I would have tried the capture process to create it for me (haven't tried that yet however on any image).

 

I've read articles regarding using 'unattend.xml', but how does that prepare the volume for capture? :-( Any thoughts...?

[SYNACK]

You need to generalize but you need to use an xml config file to tell it to leave the drivers:

http://www.edugeek.net/forums/windows-7/59501-sysprep-nearly-working-but-drivers-going.html

 

We use the "PersistAllDevicesInstalls" tag in an XML file. Works wonders when you want a universal curriculum image with multiple drivers from different types and brands of workstation.

 

   
       
           [b]true[/b]
       
       
           1
       
   

 

 

To make the process easier, I copy a batch file across to run and that picks up the sysprep.xml I saved from the code above. The "SkipRearm" stops the machine resetting the operating systems and counting down 5 rearms limit rule. Our XML code that's applied to the image itself changes the product code if we need to use MAK instead of KMS.

 

sysprep /quiet /generalize /oobe /shutdown /unattend:sysprep.xml

 

 

Hope this helps anyone trying to do this in future. This has worked since the early days of deploying Vista.

 

Customizing Windows 7 unattend.xml « PC LOAD LETTER

 

 

You'll want to use the Windows AIK to make your own XML though that targets x64.

Edited October 22, 2012 by SYNACK

[MikeAtTrs]

Thanks Synack - have just been doing some more reading and I think I have mis-understood the 'true' line - I thought it had something to do with disabling the Digitally Signed Driver issue on 64 bit OS - oh well, something else new I have learnt today...will try the command line as suggested.