• Summary: The K1000 Client normally checks in using the "Run Interval" schedule specified in the K1000 appliance Settings/Client Options tab on the server. For debugging and testing purposes, KACE provides ways that can be used to force a check-in outside this normal schedule.
  • Symptoms: The client isn't inventorying correctly or running a script, managed installation, patch, or replication doesn't provide the desired results
  • Cause: An issue with what's being ran and we need to identify what's the cause
  • Steps to resolve issue:

From the server you can click on the computer in the inventory list and then press the button 'Force Inventory Update'.

To force a checkin on the 5.1 Windows client, either browse using explorer to c:\program files\kace\kbox and double-click on KBScriptRunner.exe or launch the program from the command line:

C:\> C:\program files\kace\kbox\kbscriptrunner.exe
OS X: /Library/KBOXAgent/Home/bin/runallkbots
Linux: /Library/KBOXAgent/Home/bin/runallkbots
Solaris: /KACE/bin/runallkbots

Note that the KBScriptRunner.exe only forces a check-in (bypassing the “Run Interval”) but does not force an inventory if you have a non-zero Inventory Interval set on the server. There is no way to override the Inventory Interval from the client side. You may want to change the inventory interval to zero on the server while debugging/testing package deployments.

On a 5.3 client you will want to open up a command prompt and do the following:

c:> c:\program files\dell\kace\runkbot 4 0

Another way to force an inventory is to manually delete the machine record on the server between tests and then use KBScriptRunner to force a checkin. Since the machine record will be new, an inventory will happen. This approach doesn’t work if you’re manually applying labels to your machines, since you’ll lose the labels on the test machine each time you delete it. But it works nicely with filter labels which are dynamically reapplied.