How long should it take to image a machine?
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 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.