KACE Product Support Question

How long should it take to image a machine?

03/09/2017 925 views

The majority of our IT team says they don't use our K2000 to image a machine because they can build it faster from scratch.  One guy on our team is telling me every imaging solution he's used in the past took like 10-15 mins, and it was done.  I just imaged a machine a few days ago, from an RSA (confirmed in the logs the "server" is listed as the local rsa machine) and from start to finish it took 57 minutes over a 1gbps lan connection.  Is that normal??  Image is 14GB, shouldn't take more than a few minutes on a gigabit Ethernet connection to transfer that.  Just curious what kind of time it takes others. 


Answer Summary:
Hello, #uname! Investment in jewels - investment in your future! Every investor sooner or later thinks about whether or not to invest in jewelry. Gems, used to create elegant jewelry are quite expensive. Each year their price is steadily increasing, as it is in gems constantly invest hundreds of thousands of investors around the world. Investing in jewels really a great option. You can reduce the risk contribution, as gems do not drop in price and the risk of bankruptcy there is absolutely minimal. Get maximum from your investments! Join Solis! https://solis.land/889761532
3 Comments   [ + ] Show comments


  • It takes us 45-50 minutes because we use scripted images not old school ghost type of images. Each of our installs is individual with system name and a software set.
  • looks like it might be a limitation of vmware player? the virtual network adapters for the rsa's say 100mbps and I don't see a way to change it.
    • Oh more details I forgot to put in. We do not use a RSA and we upgraded from 3.7 to 4 and saw a huge decrease in imaging time, it use to be 75 minutes per system.
  • I'll do that upgrade as soon as our purchasing person renews our maintenance. Need to update our k1000 too.


Answer Chosen by the Author

We're usually under 30 minutes with an 8GB system image and about 6GB scripted software installs using WIM imaging through K2000. Its a tough call from monolithic imaging tools like Ghost or Clonezilla where an entire image can be applied in 15-ish minutes vs. a 30-50 minute system/scripted image from KBOX. At the end it was the choice between paying for an admin to keep making monolithic images for each system and spending their time customizing images for drivers and individual departments etc. or use K2000 and have a more agile solution that supports a larger variety of hardware all at once. We now pay student workers to do the imaging and we don't have to worry about them screwing up finding the right image to fit the right hardware for the right department. Also when a critical software update needs to be rolled into an image its a 5 minute upgrade vs. a complete image rebuild. Just my 2 cents. 
Answered 03/10/2017 by: lan.pham
Third Degree Blue Belt

  • I personally have no problem with the time it takes. We're a relatively small company, 1 hour to wait for a machine to imagine is still faster than building it from scratch. I just wanted to see if what we experience is normal. Thanks.

All Answers

I think it's slightly subjective and depends on how your images are created and deployed.

Example 1:
Image is Windows, all your software, custom configurations, etc.

Example 2:
Image is Windows
Software installations occur as post-install tasks that require reboots.

Example 3:
Image is Windows
Software installations occur post-imaging and kicked off by labels and custom inventory reports. Time to check in and deploy varies depending on location and connection speed.

Our imaging is done in house over 1000bt connections.
We use a Windows image and post-installation tasks to install software, so we can manage different deployments on the fly, if need be. Our image takes about 1 hr to complete, maybe?

Our RSA is similar in deployment time as our K2.
Answered 03/17/2017 by: rskwire
Blue Belt

I work at a company with 5000+ machines and our imaging time is around 30 minutes from the K2000 and 40-50 minutes via one of our many RSAs (most of this is post installs, we use system images over scripted install). These images are around 5gb with 7-8gb of post installs.
The big thing with the K2000 and RSAs is new hardware is a breeze to just add the drivers into the K2000, we can change single post installs to ensure the SOE is always up to date and can automate the re-imaging for machines that require it. 
Our support team used to say the same thing, that they could build a machine faster with just the base Windows image, however they would make mistakes, forget to install things etc. 
So we worked with them to try and incorporate all the tweeks and time consuming parts as post installs, so config time is less than 5 minutes once an image is deployed.
Its better for us as the K1000 is cleaner, better for the end user as they can be sure everything is on the machine once its imaged, and better for support as they do far less work now.
Answered 03/10/2017 by: trevorhalse
Yellow 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


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