New to the KACE boxes, but becoming more familiar with the fast curve.  I was basically thrown the manual with little direction, so can anyone just share a few tips (from hands on) regarding:
  • Basic Image Creation (e.g., using win10 iso, which we have)
  • Uploading the Created Image
  • Proper way to Create Boot Enviro
  • Tools that work best (e.g., K200 Media Mngr?, ADK?)
My goal is to at least have a standard image template for Win10 with the typical MS Office suite & Adobe Reader DC for starters. Having clarity on first things first with the base image Win10 load helps. The rest should be easy with app uploading to test in the standard image along with the scripts.

This is a short list just to kick things off correctly. I hate nit-picking instructions that tend to go down a rabbit trail.

Any advice is appreciated.
2 Comments   [ - ] Hide Comments


  • Nico, many thanks. Your response is helpful, I'll check out the links and create a test enviro. Since I inherited the whole kit and caboodle with very little help, I'll have to ask if the jumpstart was obtained and hidden somewhere by the previous administrator. As I go through the various pieces of the Kbox's I'm trying to document specific steps that are not as ambiguous as the admin guide.
  • Here's a Win10 imaging guide from Dell:
    • Thanks, Jason. Greatly appreciated, I'll check it out.
Please log in to comment

Answer this question or Comment on this question for clarity


Best practices for Image creation:
The Image can be captured when booting the device into the KBE and choose the step.

Creation of a KBE (boot image)
You need the ADK/AIK depending on the OS you want to have in the KBE (the newer ones enable you also to deploy previous OS so if you use the W10 ADK and build a KBE with that (don't forget the KBE 10 driver package) you can also deploy W7 or W8.1 (if supported, since Caby Lake CPU don't support W81 or older)

All these questions are discussed and configured with you in the jump start (if you brought one, if not, I suggest to contact Quest Sales to buy one since this training shows you how to setup such things after best practices.

Answered 02/03/2017 by: Nico_K
Red Belt

Please log in to comment
Here are some video resources:
Latest server version (only 4 videos currently):

BTW in our environment we're using "Scripted Installations" instead of "Imaging" since we found it more stable and easier to maintain.
Answered 02/03/2017 by: JasonEgg
Red Belt

  • Sure...understood. I'm using Scripted Installations also. So we're on the same thought pattern. Now the kicker for me (which is an additional concern) is how the heck are images added to the "Scripted Installation Name" field? Small pieces like this have my curiosity so that I know exactly where to find the proper parameters.
    • which field do you mean? On the K2 web ui or the boot menu or?
    • If I understand the question correctly, I think you're conflating "System Images" and "Source Media". Scripted Installs are created from (or based on) Source Media instead of images.
Please log in to comment