Agent 12.0.38 not connecting unless I manually run and inventory

Just moved to a new company and I am implementing a new version 12.0.149 of the K1000.  I am rolling out agent 12.0.38 by both manual install and typical GPO deployment.

The installs and the GPO deployments are installing without error on Win 10, 11, and also Windows server 2012 R2 and 2022.  However not one of the computers has checked in on its own.

In order to get the computer to first check into the K1000, I had to run an Inventory on the local computer (both runkbot 4 0 and using the systray Kace icon work). Even after a successful manual inventory run, none of the computers are running automatic inventories on their own even though I have them set for every 6 hours.  Even if I run "Force Inventory" from the console, the computers will not run and Inventory.

All the computers show connected.  

0 Comments   [ + ] Show comments

Answers (2)

Posted by: tbatchelder 1 week ago
White Belt

I am having a similar issue but with KACE agent 12.1.52. I am installing it with our SDA and using both the HOST and TOKEN options in the command line install (Install KACE Agent for Windows (kacecloud.com)). However, the computer will not populate in SMA inventory until I run a manual inventory ("runkbot.exe 4 0" K1000 RUNKBOT.EXE Command Switches (147398) (quest.com)) on the computer itself. This was not an issue when we installed the previous version of the KACE agent without the HOST and TOKEN command line options - the computer would automatically populate in SMA inventory without any intervention. Oddly enough, it wasn't an issue when we were pushing the new agent with SMA, but still installed the old version with SDA. Thinking it has to do with fresh installs of agent 12.1.52, but hoping someone else has had similar issues. I did check that the agent is active on the fresh install using kstatus.exe. I also checked the amp.conf file and it matches what I have on my computer.

Posted by: RandomITdude24 1 month ago
Black Belt

I have seen this happening, have you tried maybe on one of those machines to perform a restart or maybe just restart the agent and see if after that the agent kicks in? also... one useful command that I run after deploying the agent is kstatus.exe to know if the agent is actually working

  • Not sure if this is a KACE issue or a firewall issue yet, but the K1000 did not seem to like being in my DMZ. My internal network is a 10.x.x.x and I created a 172.x.x.x DMZ. I setup a 1 to 1 NAT on the security appliance so my external IP X.X.X.X would forward into the DMZ IP of the K1000.

    Clients showed as Connected and every one of them could login to the K1000 interface over HTTPS without issue. Just the Inventory upload was being blocked. No idea why yet.

    At first I thought it might be an issue with clients hair-pinning back in to the DMZ, but it does not seem to be a problem having the ports forward to my internal network. Also, external clients would not be hair-pinning so I can't see that being an issue.

    Just strange to see all the clients being able to connect and also login to the web interface, but no Inventory updates. - JordanNolan 1 month ago
    • From what I know.... Kace don't like to be listened or touch in any way by ssl inspectors, load balancers, or any other security software that would get in the middle (avoiding man in the middle attacks) have you checked any of that maybe? Also you can go to admin > support > diagnostic utilities > from the drop down run "services" and check that everything is fine there - RandomITdude24 1 month ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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