/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Import WDS Image into K2000

10/15/2013 3678 views

Is there an easy way to import my existing WDS WIM image into the K2000?  We are currently running version:  3.5.80613

   
Answer Summary:
0 Comments   [ + ] Show comments

Comments


All Answers

2

You can try casting it to a machine with WDS and do not automatically reboot the machine.

Manually reboot into kace pxe menu and capture the image.  The image should still be in the sysprep'd state. 

Answered 10/15/2013 by: SMal.tmcc
Red Belt

2

I was hoping to avoid that option as these images are all hardware specific and casting the images takes time as these are all heavy weight imges.

Answered 10/15/2013 by: choristersys
Orange Senior Belt

  • You can cast to any machine as long as you do not reboot, you are only using the win PE OS not the image OS. All you are really doing is using the HDD as the mid transfer point.

    Another trick you can do is store them externally and remap to that share to cast them with a preinstall task.

    such as:
    start /wait net use t: /delete
    start /wait net use t: \\dr-main.tmccadmn.tmcc.edu\images Password? /user:tmccadmn\user
    start /wait net use w: /delete
    start /wait net use w: \\dr-main.tmccadmn.tmcc.edu\images Password? /user:tmccadmn\user


    http://www.itninja.com/blog/view/wim-storage-freeing-up-space-on-your-k2000-if-you-are-using-wim-s

    http://www.itninja.com/blog/view/do-you-want-to-store-your-wim-s-externally-with-k2000-v3-5-like-we-did-with-3-4
2

hmm, that could work.  I'm currently trying using the HDD as the transfer point so we'll see if that works for now.  I like the idea of using the WIM images externally as they are currently being stored on the WDS Server.  I'll have to give that a try when this capture with the K2000 is finished.

Answered 10/15/2013 by: choristersys
Orange Senior Belt

  • I have found using windows shares I can push 3-4 classrooms at the same time 90-120 machines form 1 k2000 and that takes about 2.5 hrs doing 120 vers 35 min on a single machine. I also have shares at each site to have the bulk of imaging to be on the local network not over the wan
  • I'm not familiar with WDS, but if it stores the WIM where you have access to it and you're still using placeholder images from the 3.4 KNIT, you really don't need to do anything but adjust your apply-wim.vbs parameters to reflect the image name. I wholeheartedly attest to SMal's method for storing WIMs externally.
1

Hi Nheyne, I just got off the phone with Kace 1st and 2nd level support after an hour and 15 minutes.  Their technician imported the placeholder images from the 3.4 knit for me, rebuilt a new kbe boot environment (as the existing one didn't work for some reason), walked me through setting up an Imagestore directory within petemp, migrated my wim image over from wds to kace, deployed it and it worked flawlessly.

I saw the knit tool but wasn't sure if I was able to use it as I am running version 3.5 but apparently the scripts still work just the same. 

Answered 10/15/2013 by: choristersys
Orange Senior Belt

  • just watch your disk space storing the wims on the k2000
  • We still use the placeholder images from the KNIT every day, it's great for storing images offboard.
1

We'll eventually be migrating to a storage array for all of our images

Answered 10/15/2013 by: choristersys
Orange Senior Belt

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