Client Task Agent troubleshooting on Unix, Linux and Macintosh clients
Article ID: 179673
Updated On:
Products
Issue/Introduction
How to troubleshoot the Client Task Agent on Unix, Linux and Macintosh clients
Environment
ITMS 8..x
Resolution
Prerequisites:
- After the Unix, Linux or Macintosh (ULM) client sends basic inventory, the NS must update membership and the client must refresh policies in order for the task agent on the client to register. This process will happen normally over time, depending on the NS and client configuration. (It can be forced by running 'aex-cta register' on the client.)
- The CTAgent requires name resolution to the task server. This name may be a shortname or an FQDN, depending on the NS.
How to find the task server assigned to a given client
The following url can be used to determine which task server the agent will register with and the name for that task server:
- This can be run from any browser on any machine that can reach the NS/SMP server as long as the correct client resource guid is entered in the URL.
- Change <Client's NS Server Name> to the name of the ns server the client computer in question reports to and change <client-resource-guid> to the resource guid of the cllient computer in question.
- If needed, the NS server name the client is reporting to can be found on the client by running "aex-helper query ns".
- The client's resource guid can be found in 1) Resource Manager, 2) in the client computer's /opt/altiris/notification/nsagent/etc/host.GUID file, and 3) by running "aex-helper info resource" on the client.
Location of related files on the client:
/opt/altiris/notification/ctagent/var/servers.xml - this file contains the name of the Task Server returned by the above URL. This name must be resolvable.
/opt/altiris/notification/ctagent/var/cta-runtime.cache - This file contains the 'last_server' that the client was registered with.
Feedback
