Description: This is an overview of the methods of installing the Linux and Unix agents for 9.0 SP3 and 9.5 versions of LANDesk.
Note: A 32-bit agent may work if installed on a 64-bit platform. However, the correct dependant libraries will need to be located in the /lib folder instead of the /lib64 folder. Also, this configuration is not tested and therefore is not supported.
Note: Installing both agents (32-bit and 64-bit) on the same machine are not supported. Please use linuxuinstall.sh which is included on the core in the linuxuninstall.tar.gz file to remove both agents before installing a new agent.
Method 1: Standard Push (Both 32-bit and 64-bit Agents)
This method works similar to a push method for Windows based systems however the "root" user credentials on each client system will need to be added to the Global Scheduler on the core (Configure - Services - Scheduler). Troubleshooting of the install is the same as well. A log of the task is created in the Log folder underneath ManagementSuite. The log will help with errors and determining required libraries that may be needed on the client for the install to complete. The log may generate a certificate message but it can be ignored. This push method should work for all currently supported Linux/Unix OS's. The agent push is going to attempt a remote execute on the client so SSH will need to be open as well.
Method 2: Manual Agent Install (Both 32-bit and 64-bit Agents)
1- Four files are needed for a manual agent install on Linux or Unix. The files for each agent are listed below.
PLEASE NOTE: The shell script for installation is configured when you save the agent so make sure that the desired bit level is selected before saving the agent configuration. If the correct bit level isn't selected than the script will call the incorrect tar files.
32-bit:
C:\Program Files\LANDesk\ManagementSuite\ldlogon\unix\linux\baseclient.tar.gz
C:\Program Files\LANDesk\ManagementSuite\ldlogon\unix\linux\vulscan.tar.gz
C:\Program Files\LANDesk\ManagementSuite\ldlogon\hash.0 (Note: The files isn't named hash.0 but will instead include the unique key combination of the core server in question. This is the public certificate for the core that needs to be included with the agent)
C:\Program Files\LANDesk\ManagementSuite\ldlogon\AgentName.sh (Note: This file will be named after the agent name you provided when creating the Linux/Unix agent)
64-bit:
C:\Program Files\LANDesk\ManagementSuite\ldlogon\unix\linux\baseclient64.tar.gz
C:\Program Files\LANDesk\ManagementSuite\ldlogon\unix\linux\vulscan64.tar.gz
C:\Program Files\LANDesk\ManagementSuite\ldlogon\hash.0 (See above...same note as the 32-bit agent hash file)
C:\Program Files\LANDesk\ManagementSuite\ldlogon\AgentName.sh (See above...same note as the 32-bit agent)
2- Make sure you are logged into the Linux/Unix machine as "root" or elevate your priviledges with the command "sudo sh".
3- Copy the files listed above to a temporary folder.
4- If logged in as root you can probably skip this step. Otherwise make the AgentName.sh file executable with the following command: "chmod +x AgentName.sh".
5- Execute the shell script. This is assuming you are in the directory containing the files: "./AgentName.sh" (Note: That is a period and a slash at the beginning of the command which makes it execute the command from the current directory)
During install several errors may occur. The most common would be a dependancy to a certain library. How to install each dependancy is going to vary by each OS distribution. You will need to install the library either from the install CD or through the update utility employed by the OS. If you're not sure which library to install then perform a general search on the internet for the files referenced in the install log.