Just wondering if anyone else has noticed how slow deploying WIM images via USB is. I have a 7GB Win 7 X64 WIM captured via the KBE. It contains no Post Installation tasks other than the WIM deployment. Currenty I can deploy this over our 100MB network in about 15 minutes.

If I setup this to deply via USB using the KACE isntructions it takes around 35 minutes.

The USB stick is not the bottleneck. If I use the same stick to capture and deploy the same image, using a different sector based imaging software Active Disk Image, it only takes around 7 minutes to deploy.

I would have thought at the very least I would get the same performance from the USB as we get rom our 100MB network. We have 700 PCs to image this coming December and at the moment it looks as though the K2000 will be sitting in the corner wasting power.

0 Comments   [ + ] Show Comments


Please log in to comment



have you tried placing the Wim on a windows share? I use that method and it is a fast as using MS imaging solutions


Answered 11/13/2012 by: SMal.tmcc
Red Belt

  • Unfortunately that is not an option. Almost half of our fleet are spread across various remote locations. Deploying via USB is the quickest and easiest approach. We have used this method as far back as I can remember, traditionally with Ghost, then Active Disk Image. I thought KACE USB deployment would suit our needs perfectly but it is but at 5 times to times to deploy vs other methods it is not going to work.

    BTW I'd just like to say thanks for all the information you have contributed regarding the KACE devices. It has helped greatly.
  • The usb device is probally trying to reach the k2000 for tasks and this will bottleneck you. I would recommend if you are using a WIM on a USB put all the commands you need in the answer file and stage any support files on the image that you may need to run as post tasks. When I was playing with the usb boot I edited the startnet.cmd in the boot.wim pe file and removed the references back to the kbox and also added imagex and a batch file to start the imaging using fdisk and imagex. My PE env booted and opened a command window
  • OK I did some more testing and it appears it was the USB stick. This time around I grabbed a 1TB mechanical USB drive and made that the boot device with the WIM on it. Doing it this way it only took around 10 Minutes to copy the WIM image.

    I would guess it has something to do with the file based format of WIM vs Sector based format of Active Image. Cheap USB flash storage is not the greatest at handling high IO ops but handles large file copies quite well. The mechanical drive however handles the high IO of the WIM copy far better.

    Thanks for your help.
  • Agree, I only have used portable HD's due to image sizes. I am testing with a SSD drive now and noticed about a 15-20% speed imporvement over a standard external drive.
    you could also improve your thru-put if the machines have usb 3.0 ports, use a 3.0 drive and add the drivers to your PE env.
Please log in to comment
Answer this question or Comment on this question for clarity
Five Easy Steps to Smarter Systems Imaging
With traditional methods for systems imaging, each image captures a particular hardware and software configuration at a specific moment in time—static, unchanging, unmanageable.