Hi SMall.tmcc, and anyone else of course,
     Can you clear up what the purpose of the 1.7kb shells is and how they tie in with the off board full image files?
 I'm eagerly working my way through your outstanding articles and instruction. I'm able to load a 1.7kb empty drive image and also just got the first capture to load successfully to an off board server. For new readers, see the link below. Great stuff.

I may have lost myself in the mix a bit and I'm not really sure what, where, when, how etc I'm doing with the shells along with the offboard stuff. Obviously the point of the empty shell is to save space, but if it's pulling from an off board img file that's complete anyway, why do we need the shell? 

I'm thinking the shells may be meant for storing various hardware or software configurations and they can pull from a master off board img. But I can't figure how that would work. My end goal is to be able to deploy 1 or 2 master images to 9 different hardware models of Latitude and Optiplex. I'd like to have the option to create a bunch of other images (configurations) that can handle different customizations of post install settings and installs so long as they aren't eating up space on the K2000.


Thanks again for the help.

0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


I figured it out...by reading your instructions more closely. You've got everything there, but I confused myself when I read 
"remap the W drive as my first preinstall task to the needed storage to access the WIM" and the screenshot below showed a T: drive mapping. I got the capture/deploy stuff crossed, but sorted it out.

Just needed to create the Post Install (mid-level) task to run the apply_wim.vbs script.

Thanks again

Answered 11/12/2014 by: murbot
Tenth Degree Black Belt

Please log in to comment