KACE Product Support

The primary reason we moved away from MDT over to the K2000 is the Remote Site Appliance capability. We have 80 sites with bandwidth down to 256Kbps, so being able to slowly trickle OS deployments out for local deployment at each site is extremely important. If you only have one site or all of your PC builds are done at one site, then the RSA capability would not matter to you.

Well in a K-12 environment are you repeatedly pushing out images to the same machines (as in daily)? If so combining the functionality of the K1000 systems management appliance (with its Agent on every machine) with the K2000 systems deployment appliance would give you the ability to force a reboot-to-PXE and push a fresh image to machines with quite a bit of control as to which machines/when/which images, and both Post-Installation tasks on the K2000 as well as Managed Installations (MI packages) from the K1000 give you a lot of control as to what beyond your base image gets installed on your client machines.

If you are configuring your machines to boot to PXE first (before the HDD) and using both the K1000 and K2000 then you've got a lot of the zero-touch functionality the much pricier (and harder to master) Microsoft SCCM would give you.

Eric

Another huge reason is that K-12 districts are tired of maintaining a huge array of district images, and what license goes on what. Some will use the K1000 as ericwalrod stated, or use the k2000 to create a basic image, and then stack your software as post installation tasks on top of it. The overhead of disk space to do this on the K2000 is minimal.