KNOWN ISSUE: Unix, Linux and Macintosh computers are not registering the CTA agent when redirected from one NS7 server to another NS7 server
Last Updated April 15, 2010
When directing Unix, Linux and Macintosh clients, that already have the NS7 Agent installed, to a new NS7 server, the Client Task Agent (CTA agent) remains registered with the previous NS7 server.
The clients were directed to a new NS7 server by browsing in the NS6 console to Settings, All Settings, Agents/Plug-ins, Settings, Altiris Agent Settings - Targeted, All Linux/Mac workstations, Advanced tab, Alternate URL for accessing NS.
After applying these settings, the agent on the client computer(s) begins communicating with the new NS7 server but the CTA agent remains registered to the previous NS7 server.
'aex-helper query ns' returns the name of the new NS7 server
'aex-cta ts' return the name of the previous NS7 server
The cause of this is being researched at this time.
There is a known, manual workaround. Permanent resolutions to avoid this issue and to resolve existing occurrences are being researched.
The manual workaround is:
On each affected client machine:
1. 'cd' to the /opt/altiris/notification/ctagent/var directory 2. delete the following files: cta-runtime.cache & servers.xml 3. restart the altiris agent on the client: '/etc/init.d/altiris restart' or '/opt/altiris/notification/nsagent/bin/rcscript restart' 4. run 'aex-refreshpolicies' 5. run 'aex-cta register' 6. The Client Task Agent should now be registered with the new NS7 server. Run 'aex-cta ts' to verify.
Applies To Symantec Management Platform SP3 7.0.7270 Altiris Agent for Unix, Linux and Mac SP3 7.0.7270
Note: this may apply to any 7.0.x installation.
ID: ETK 1952255
Etrack (Symantec) database
Imported Document ID: TECH122039
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe