Systems Management

Can you check the KAgent.log file for any errors on the machine where agent is not checking in? - AbhayR 8 years ago

I did a search for the word error in the log and nothing turned up. Good idea though. - AFCUjstrick 8 years ago

Have you tried stopping and starting konea? We've been having a similar (same?) issue where everything is installed, can manually run a check-in (runkbot 4 0), and the service is running, but it won't inventory on its own until the service manually restarted. - troyr 8 years ago

I just ran kinventory and inventory and then restarted the service but still no connection to the server. - AFCUjstrick 8 years ago

check the logs under:
C:\ProgramData\Dell\KACE\user
The K1000 7.0 always connects to port 443 (the linked error message should be seen in the logs) instead of 443 or 80.
So if you blocked this port no agent can connect.
If you have trouble analyzing the logs contact support or copy the nessesary logs here. - Nico_K 8 years ago

So I put in a ticket with Dell > quest's support team. They said they are aware of the situation and they plan on having it fixed in the next release. Until then it's advised to remove the the Agent and use a GPO to install an old version. Here's the link to the old agent;

https://support.software.dell.com/download-install-detail/6066621

EDIT:: So i realize that the link provided is the kbin file. This file needs to be uploaded and applied to the k1 in order to get the 6.4 msi. To do this go to the k1 > settings > provisioning > update agents > manually upload agent bundle. Before doing this i recomend saving the 7.0 agent from \\k1000\client\agent_provisioning\windows_platform\ampagent*.msi just in case. I wish i had done this prior to downgrading to Agent 6.4. You can try provisioning an uninstall as an MI and use a GPO to deploy the 6.4 agent.

I'm still in the process of this downgrade so this is all the advice I can offer right now. If anyone went through this same issue and fixed it, please share your process. - robcalewar 8 years ago

Sound pretty typical for DELL or whoever they are now. So many issues with this system! - hf13207 7 years ago

can you use the 6.4 agent with the 7.0 kace version? let's say i upgrade to 7.0 but not the agent. - rdroste@obdnoordwest.nl 7 years ago

Can you tell us the exact version number of the agent that has this problem? Version 7.0.763 is available now but I don't know if it has the bug you described, or if it's the "next version" where it's fixed. - adamglass 7 years ago

I just tried the method of downgrading a few to see before deploying to my whole fleet, and it's still not checking in with 6.4.522 agent... I'm at a loss.. - Teknosha 7 years ago

UPDATE: Contacted Quest and have applied a hotfix to the Kace server to address this. Waiting to see. Will follow up once I see results... (older) -We are seeing the same. Clients, both 6.4 and 7.0 are not connecting at all. Have tried starting and stopping service and uninstalling and reverting back to 6.4 on a test batch with no results. - ECUPir8 7 years ago

I am experiencing the same issue. Most of the clients will check in, but the inventory process (if it works) takes a ridiculous amount of time. I do have a couple of clients that will not check in period. I called Quest will little help. They are researching. We are on server 7.1.149 and running agent 7.1.62. - tgrinnell 7 years ago