How to manually install individual components of the Symantec Management Agent for Unix, Linux and Macintosh

Products

• IT Management Suite

Issue/Introduction

Question
On occasion, it may be necessary to install the Symantec Management Agent for Unix, Linux and Macintosh using the native package files rather than the aex-bootstrap binary. This article describes how to accomplish this.

Environment

ITMS 8.5, 8.6, 8.7

Resolution

Answer
 

There are two files attached.

If you don't want to use the script, you can manually run each command found in the script or create your own script. It's a simple script in that it downloads the native package files using wget and runs pre-existing scripts that are part of that installation package. Example:
wget -P /tmp http://yourSMPserver.yourdomain.com/Altiris/NS/NSCap/Bin/Unix/AgentInstall/Linux/x86/aex-bootstrap-linux
chmod u+x /tmp/aex-bootstrap-linux
/tmp/aex-bootstrap-linux

If you do not have or use 'wget', you can substitute any other method to copy the files to the client computer, then run the agent-upgrade script, as shown in the sample script.

Note that the paths used in the script to download the installation package will need to be modified for each platform. On the NS itself, the default path is: \program files\altiris\notification server\nscap\bin\UNIX\Agent\'. Within this directory are unique packages for each Unix, Linux and Macintosh platform. Note that IIS maps '<servername>/Altiris/NS' to \program files\altiris\notification server'.

Note: As mentioned above, ULM agent is a little bit different in having 64x and 86x versions on its installers (the Altiris Agent (Symantec Management Agent) has only one installation file: AeXNSC.exe (under ...:\Program Files\Altiris\Notification Server\NSCap\bin\Win32\X86\NS Client Package) that handles both bit versions). We have both binaries for Linux:  http://NS-SERVER-NAME/Altiris/NS/NSCap/Bin/Unix/AgentInstall/Linux/x86/aex-bootstrap-linux http://NS-SERVER-NAME/Altiris/NS/NSCap/Bin/Unix/AgentInstall/Linux/x64/aex-bootstrap-linux The installer does not detect bitness of the system. It can only detect Linux<->Linux Debian flavor. The bitness is preserved during the compile time. Also, the "push" logic on the SMP Server can detect the bitness and choose the right installer.

 

The order of execution is important. For example, the Software Management Framework agent is dependent on the Inventory rule agent.

The aex-agent-install-config.xml.txt is a sample only. You will need to create your own later. 

1. Copy the manual_agent_install.sh.txt file to an empty, temporary directory on the suse/linux client.
2. Run "mv manual_agent_install.sh.txt manual_agent_install.sh' to rename the file.
3. Use any appropriate method to modify the NS server name in the wget statements in the script.
    
4. Run 'chmod 755 manual_agent_install.sh' to make the script executable.
5. Create a copy of an .aex-agent-install-config.xml file from your own system. In the console, browse to:
       - Settings, All Settings, Agents/Plug-ins, Altiris Agent, Settings, Altiris Agent Install. 
       - Click on the 'Install Altiris Agent for UNIX, Linux and Mac' tab. 
       - If no entries exist in the computer list, add one (even a dummy ip address will suffice for this purpose). 
       - Highlight an entry in the list of computers. 
       - Click on the 'Installation settings' button. A new window will appear. 
       - Click on the 'Install XML' tab. 
       - Click on the 'Save as file...' button and save the file. 
       - Copy the file to the same empty, temporary directory on the suse/linux client. Be sure it preserves the recommended name including the initial '.'. This file must have read permissions on the client.
6. Run "./manual_agent_install.sh". The agent should install normally.

 

 

 

* The .aex-agent-install-config.xml file is important as support was not successful in configuring the ctagent to communicate with the proper NS server after installation. It 'may' be possible to install the aex-nsclt agent (the NS agent itself), then configure the NS agent to communicate with the proper NS, then install the remaining subagents. This article will be updated when support completes additional testing scenarios.