1 Reply Latest reply on May 21, 2012 2:28 PM by tdavenport

    Caching OSD image


      I want/need to be able to cache my image and files the local hard drive.  Currently I have no partition on my drive etc.  I would like to cache image pc local hardrive (may have to create a partition, cache image and supporting files, vboot - reboot, and install OSD using files cached, remove partion with image files. reboot and let the image do it's thing.


      Is this currently possible?

        • 1. Re: Caching OSD image

          I've not done this but its technically possible. 


          1. Using provisioning or OSD, you'll need to tweak your diskpart commands to create a partition of sufficient size to hold the image(s).
          2. Set a drive letter of something like Z.
          3. Use diskpart again to create and format your C: drive and make it active.
          4. Copy your images down to the Z drive.
          5. Call on imagex or imagew to install your image from Z to C.
          6. Once the image is complete and before the reboot, you'll need to run dispart yet again to remove the Z drive.
          7. Here's where I'm a little fuzzy...you'll then need to run diskpart one final time to extend your C partition across the remaining disk. Alternately, you can call on diskinfo and run diskinfo extend_last_partition. Something like that. Diskpart and Diskinfo are already present in your WinPE image so you just need to run the commands - you don't need to add any utilities to your WinPE image. I'm pretty sure your file system needs to be NTFS for this to work..I could be wrong.
          8. Reboot and continue with the rest of your imaging process.


          In provisioning, this should be relatively straight forward. Provisioning will also give you a lot of options to easily test and change the disk preparation phase. In OSD, you'll be editing the OSD ini file directly (ldmain\scripts). Not as pretty and more work but it will do the same thing.


          I have not done this but it is very possible. I may be overlooking "where" the partitions reside (beginning or end of drive) but you'll figure it out.


          Here's a link to dispart commands: http://technet.microsoft.com/en-us/library/cc766465(v=ws.10).aspx


          Also look at a canned provisioning template to see how to prepare your disk - again, tweek for your needs. Sample templates can be found here: http://community.landesk.com/support/docs/DOC-23470 . Look in the Pre-OS installation phase of provisioning for disk preparation.


          Finally, look at an OSD ini file to see where the disk is partiitoned and extended. Here's a sample of what happens:

          REMEXEC24=diskpart /s X:\LDClient\wipeDisk0.txt

          REMEXEC25=cmd /c format /Y /FS:NTFS /Q /V:C-DRIVE c:


          Dispart can read a text file so wipedisk0.txt contains ALL of the diskpart commands. You can edit the text file but you'll also need to create a second diskpart command to wipe the Z drive after imaging.


          Good Luck.