/build/static/layout/Breadcrumb_cap_w.png

After update 11 kace doesn't see some machines in the park

Hi ninjas, 

how are you doing ?

after updating the server and clients to version 11, some machines are not communicating with the server, some machines have upgraded to version 11 of the agent and some are not, I have already checked the traffic on my firewall and I have no blockages, I have already checked my antivirus and no I have locks

I verified that in the server \ system the agent version is in 10 and \ admin is on 11 do you know what it can be? below some prints


h86x21jL27DZQAAAABJRU5ErkJggg==

(\admin)


wOJoQCdwD+QIgAAAABJRU5ErkJggg==

UAcHPUWrtFYAAAAASUVORK5CYII=

wFmE4hSN9IYFAAAAABJRU5ErkJggg==


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Nico_K 1 month ago
Red Belt
1

in the log I see some potential issues:
1. quarantine, the clients may be quarantined, since it could be something with the token (had this also on one linux machine when I updated), so go to Inventory | Quarantine and check if the machines there. If yes, approve them.
2. http 501 which can be nearly everything but also linked to 1. But the Runtime Exception does not sound nice
3. BAD_MAC_IP means that the appliance does not recognize the KUID together with this IP.

I suggest to analyze it as follows if the system is not quarantined or cannot be seen after approval
1. reboot the client
2. force inventory on it from the Agent Status Icon (if you have enabled it) or calling c:\program files (x86)\quest\kace\runkbot 4 0 as admin from the cli and wait for 10min
3. run a KAT (or simply read the logs in c:\programdata\quest\kace\users\, but if you stuck and need to open a SR with KACE support the KAT is always a good idea to have it handy directly after the issue) https://go.kace.com/to/k1000-kat-kb

Posted by: joaobastos 1 month ago
White Belt
0

thank you for your test indications, all and still not working, what I noticed is that the services that run on the machine like konea kswmeter client locator offiline amp scheduler are not starting with windows, and in services 


GsYFc1t0cO0AAAAASUVORK5CYII=SrLVrwAAAABJRU5ErkJggg==

Don't be a Stranger!

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

Sign up! or login

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