/build/static/layout/Breadcrumb_cap_w.png

Devices lost connection to Kace, how to get them back online.

We have quite a few devices that have lost connection to Kace, this happened at some point in May 2021.

We have only discovered this recently and started to find devices that are no longer communicating with Kace at our different sites, we have close to 350 sites and every site has its own server and domain so it's not easy to go on every sites server and try to find the missing devices. 

The problem is I can't do provisioning via Kace or AD cause I have to do a complete uninstall and reinstall to get the devices back online, just running the install doesn't seem to work for some reason. 

So is there any way i can locate all the running devices that lost connection to Kace and ended up archiving?


0 Comments   [ + ] Show comments

Answers (2)

Posted by: KevinG 1 month ago
Red Belt
0

Please post the following additional information.

SMA version.

Agent version.

OS of the device(s)

You can run the Kace Agent Toolkit to collect the logs from one or more devices.

https://support.quest.com/kace-systems-management-appliance/kb/263376/using-the-kace-agent-toolkit-kat-kapture

Troubleshooting KB.
https://support.quest.com/kb/195835/agent-troubleshooting-practices-agents-not-checking-in-or-not-running-inventory

The Agent log files to focus on are konea.log and KAgent.log for errors.

You may want to open a support ticket and include the log files from the Agent(s).


You can use this report to help identify which devices you may want to focus on to determine the root cause.

Computers that are MIA for 60 Days


Posted by: onecogmind 1 month ago
White Belt
0

Very important to check and make sure you didnt reach the maximum limit of licenses.  That would also cause the problem.

Assuming the devices have connected before you can just list all devices and sort them by the last time they talked to SMA.  Should give you some idea of which ones arent.

From any system that is not checking in you could run from Quest directory kstatus to see if its even talking to the SMA. Sometimes it talks but has an agent issue.  Can do: runkbot 5 0     that should update it. 

Don't be a Stranger!

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

Sign up! or login

View more:

Share

 
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