KACE K2000: Are there additional steps when deploying KBOX client on a PC image

  • Summary: Customer is capturing system images on the K2000 and is noticing problems with dupilcate KUID's showing up when the system inventories into the kbox. 
  • Symptoms: Customer creates a system image with the client installed on it and notices issues with duplicate systems
  • Cause: The KUID is pulled from the original system image causing duplicates
  • Steps to resolve issue:

First, lets start by saying this is **NOT RECOMMENDED PRACTICE** for creating images.  When creating images you want to strip what is unique about it, therefore you should leverage our Post Installation tasks to install the agent so that a unique KUID is given to the machine.

However, if you must...

When installing the K1000 client on a reference PC for image, for example by creating a GHOST image, you must clear some entries that need to be unique on each PC.

If you already have it installed on your reference PC you will need to correct the entries that already exist manually.

To do this manually:

  • stop the KBOX SMMP management service by typing "net stop AMPAgent" into command window opened with administrative rights.
  • remove the following registry settings from the image in order for each PC to be uniquely identified by the K1000 appliance:

For x86 Windows systems:



For x64 Windows systems:



  • Shutdown the PC.  It is ready for imaging.  Note: If you restart the PC then the KBOX SMMP service will restart and get a new id and you have to do this procedure again!

    Alternatively, if there is no client installed yet on the reference PC you want to create an image on you can install it with 'kinstallersetup.exe -clone_prep'. That will install the client without the ID registry settings.  You can then create your image.

    If using the 5.3 agent, use the following syntax to install the client without the registry settings.


  • msiexec /qn /i ampagent-5.2.32941-x86.msi HOST=K1000.kace.com CLONEPREP=1

Macintosh OS X

You will need to do the following:

sudo /Library/Application Support/Dell/Kace/bin/kagentctl stop
sudo rm /var/kace/kagentd/kuid.txt
sudo /Library/Application Support/Dell/Kace/data/kagentctl start 

If you image Windows PCs without removing these registry settings, the PCs will override each others machine records in the K1000console, instead of each having its own unique record.

In order to correct these machines you need to remove those keys so that they will get new unique ID's the next time they check in. You can do this automatically with a script by rolling it out to the machines you know are duplicates.There is a built in script on the K1000 named Reset KUID which can perform this task.

It will take some time for the script to be downloaded by the clients and applied.


  • Note that with 5.4 x64 clients, the reg key is now HKLM\Software\Wow6432Node\Dell\KACE. - joncutler 9 years ago
This post is locked
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