KACE Product Support

From my experience, this typically points to a duplicate KUID. Delete the KUID registry entries from HKLM\Software\KACE and restart the SMMP service on the client.

After I restarted the SMMP service, it added more registry entries.... but the machine is still not showing up under Inventory.

AMP is also at the mercy of client firewalls, network IPS, etc. Are there any other clients with the same issue or is this the only system with problems? Is a client firewall enabled?

This is the only one giving me problems.
So far, 225 clients have been added with no issues.
Firewall is not enabled.

Is it a Windows Vista/7 client? If so, UAC must be disabled. Also, you haven't maxed out your node count have you? Once you max node count in KBOX, it ignores new systems.

Nope, Win XP
Our Node count is 286

Take a look at this, and then submit a ticket to KACE support if you cannot resolve the issue.

Has the bootstrap process finished? I.e. do you have script 2 (2-xxxxxxxxxx.xml) and 3 in the c:\program files\kace\kbox\kbots_cache folder? Or does it only have script 1? or none?

If not then check the server tasks list as in this faq

If the only bootstrap tasks are old (e.g. the start time is 24 hours old) then delete them and run this on that PC "c:\program files\kace\kbox\runkbot.exe" 1 0

If it does have scripts 2 and 3 then it is done provisioning. If you do not see it in inventory then maybe you have a 1200 and it is checking into the wrong Organization? Or it is sharing a KUID with another machine?

Under C:\Program Files\KACE\KBOX\kbots_cache
there is only the following:

1-1123624800.xml
kbots.xml

I found the issue.
WMI on the client was corrupt.

I did the following:

For Windows XP Service Pack 2
Click Start, Run and type the following command:

rundll32 wbemupgd, UpgradeRepository

rebooted the machine, after a while, it showed up under the inventory tab.

Thank you guys for the help.

Here is the link to the page:
http://windowsxp.mvps.org/repairwmi.htm

I had nothing under C:\Program Files\KACE\KBOX\kbots_cache. I ran "c:\program files\kace\kbox\runkbot.exe" 1 0 and this worked. What does the 1 0 do?

WGM_Jeff,

runkbot 1 0 runs inventory.

The first parameter is the script number. The second parameter is the version of the script. 0 runs the most recent version.

The most recent version is found in:

C:\Program Files (x86)\KACE\KBOX\kbots_cache\kbots.xml

Thanks, I have had several machines that this has needed to be done on. What causes this hang up. Is there something I can do to prevent this when deploying the Agent?

runkbot 1 0 tells it to bootstrap which means go get me the default scripts and run them. Right now the defaults are only #2 (inventory) and #3 (script update).

To force an inventory on an agent that is already bootstrapped you can run "runkbot 2 0". which means...go get the latest inventory script (don't use local) and then run that script.

If those machines didn't have any scripts above #1 then they never bootstrapped. They might have been unable to bootstrap right away and were backed off to the 8 hour interval. To know we would need to start a troubleshooting process via a ticket.

I looked at the KBOX Agent tasks under Troubleshooting tools and it is showing several bootstrap tasks, but under the machine name it says "Text Missing". We are running this on a small amount machines right now, before deploying to the whole network. We are just figuring out what questions we have before calling into support.

Depending on the timestamps associated with those tasks they are either the by product of provisionings that have not yet completed -- technically the install completed but the agent has not initialized yet. OR something went wrong during that process and they will never complete -- the agent might have even gone on to complete it another way but the bootstrap task remains. If they are old you will not be able to determine which machine they were for. If they are new, then invesitage which machines you provisioned but are not showing up in inventory.

From what I can tell, I have let these sit a while and nothing ever seems to move forward unless I run runkbot.exe 1 0, or runkbot.exe 2 0. If I run either of those, it will move them into inventory, but then it will not check in again.

Make sure you're testing with the latest agent installed (http://www.kace.com/support/customer/downloads.php) 5.1.33668

If so then open a ticket with support

Thanks for all the help. After talking to support and running the debugger, turns out there was a proxy that was only supposed to be active for certain users that was blocking communication. It wasn't active for the current user, but it was for the local system. Really odd.

Excellent. That makes complete sense since when you manually run "runkbot.exe" you are executing it via the user you are logged in as but the KBOX would do it via the SYSTEM account.