K2000 scale and limitations?
Hi,
I'm wondering if anyone has been using the Kace 2000 for migrations from XP to Windows 7? I'm wondering if you encountered any limitations with the size of image files (my current ghost images range from 10gb to the largest 100gb). How many clients have you imaged in a sitting, I'd need to image 60 to 100 machine in my largest departments? Is it possible to boot the clients from the console ie send the pxe boot and force the machines to reimage remotely? I'm just curious as to the limitations of the box before I proceed with tests.
Answers (2)
If you are storing the wim's externally so some other server does the file I/O and the kace handles the orders you can get 120 going.
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
Comments:
-
if you have a k1000 and these machines are dells, you can run a script to tell the machines to change the bios to pxe boot first via the cctk and then run a shutdown -r to reboot. they will restart, If you have an action set when they check into the k2000 they will get their deployment and start imaging. then as a post command use the cctk to change the boot order back to hdd first. - SMal.tmcc 10 years ago
There is also built-in USMT functionality if you need it. If your images are really that big, definitely use SMal's links to implement server shares for your images.
