/build/static/layout/Breadcrumb_cap_w.png
10/29/2018 150 views
Hello, i have installed the kace agent on three of the above and they have installed the agent fine, However each server has not appeared in the SMA.
I have had a look in the ProgramData\Quest\KACE\user folder at each of the log files but there is no indication of why this is.
Also i have opned amp.conf and this just lists host=sma and nothing else.

Any ideas of why this is getting blocked or any other log files i an view to determine the issue?
I can ping the sam fine from each server
Thanks
0 Comments   [ + ] Show comments

Comments



Community Chosen Answer

2
in the amp.conf you see the host-option.
Is this the correct server?
If yes: check the logs in the same place
if no: you have the most obvious reason.

Keep in mind: W2k8R2 is EOL sind 2013 (5 years!) so you should not use it anymore for security reasons!
The latest agent, which supporst this outdated and EOL OS is 7.1, so no newer one is tested (but could work still)
Answered 10/29/2018 by: Nico_K
Red Belt

All Answers

1
Do you know which version you have?

As per the 9.0 release notes, agents only support Server 2012 and 2016, not 2008.

https://support.quest.com/technical-documents/kace-systems-management-appliance/9.0%20common%20documents/technical-specifications-for-virtual-appliances#TOPIC-969370

It seems 8.1 is the same:

https://support.quest.com/technical-documents/kace-systems-management-appliance/8.1%20common%20documents/technical-specifications-for-virtual-appliances#TOPIC-889577


It seems version 7.1 is the last version where 2008 appeared as a supported OS:

https://support.quest.com/technical-documents/kace-systems-management-appliance/7.1/technical-specifications-for-virtual-appliances#TOPIC-709602


Anyway, Do you see an Inventory.xml file being created and with contents on it? (check the KACE agent folder).

Do a telnet test from that 2008 server, against your KACE SMA FQDN, via ports 80 and 443.

Answered 10/29/2018 by: Channeler
Red Belt