Quantcast
Channel: Ivanti User Community : All Content - Linux and Unix
Viewing all articles
Browse latest Browse all 182

General information on deploying the Linux agent to various flavors of Linux.

$
0
0

Description

Basic inventory is supported on all Linux platforms as long as certain dependencies are met, such as compat-libstdc++. LANDesk has, however, created supports to deploy the Linux Agent to certain Linux Platforms using a Scheduled Agent Configuration.  SSH is used by the task.

 

In the LANDesk Help file, refer to the section titled

Configuring Linux and UNIX device agents found under LANDesk Management Suite | Configuring device agents

.

NOTE: Make sure name resolution back to the core works from the client. If it doesn't then the /etc/hosts file on the client can be edited with the correct resolution.

 

For information on troubleshooting the Linux Agent deployment, see the following document:

How to troubleshoot the Linux agent deployment?

 

Deploying the Linux Agent

To deploy the Linux agent to an unmanaged device, follow the steps below:

 

 

  1. Verify that SSH is running the Linux machine and that it is on the default TCP port 22 and that TCP port 22 is accessible from the Core Server.
  2. Install a supported version of Linux.  Include the RPMs that are listed as requirements.
  3. On the Core Server, add the root account to Configure | Services | Scheduler | Change Logon | Alternate Credentials. When configuring the alternate credentials to grant rights to the Linux machine, leave the domain field blank.
  4. Right-click on the Default Linux Configuration and select Schedule.
  5. Discover the linux device using Unmanaged Device Discovery (UDD).
  6. Drag the discovered Linux device from UDD to the scheduled Linux Agent Configuration task created earlier.
  7. Select Start NowNote: A link to /usr/LANDesk/common/ldiscan.sh is created in /etc/cron.daily, however cron tasks can be setup as desired.
To deploy a new Linux agent to a managed device, follow the steps below:
  1. Verify that SSH is running the Linux machine and that it is on the default TCP port 22 and that TCP port 22 is accessible from the Core Server.
  2. On the Core Server, add the root account to Configure | Services | Scheduler | Change Logon | Alternate Credentials.
  3. Right-click on the Default Linux Configuration and select Schedule.
  4. Drag the Linux device from All devices to the scheduled Default Linux Server Configuration task created earlier.
  5. Select Start now.
Also refer to How to troubleshoot the Linux Agent deployment?

 

 

Red Hat Enterprise 3

(Requirements tested with RH3U7 and a minimal installation.)

Required Configuration

 

  1. SSH must be enabled and running on the default TCP port 22.
  2. On the Core Server, the root account must be added to Configure | Services | Scheduler | Change Logon | Alternate Credentials.

 

Required Software

 

  1. For the LDMS only agent, no additional software was installed.

sysstat - (Server Manager agent only.) This is found on Disk 3 of the Red Hat Enterprise 3 CDs.

 

 

 

Note:

Red Hat 3 version prior to update 7 may or may not need additional RPMs installed.  I did not test them.</ol>

 

Red Hat Enterprise 4

(Requirements tested with update 4 and a minimal installation.)

 

Required Configuration

 

  1. SSH must be enabled and running on the default TCP port 22.
  2. On the Core Server, the root account must be added to Configure | Services | Scheduler | Change Logon | Alternate Credentials.

 

Required Software:

 

  1. compat-libstdc++ - (LDMS and Server Manager Agents) This is found on Disk 2 of the Red Hat Enterprise 4 CDs.
  2. sysstat - (Server Manager agent only.) This is found on Disk 4 of the Red Hat Enterprise 4 CDs.  Note: Red Hat 4 version prior to update 4 may or may not need additional RPMs installed.  I did not test them.

 

SUSE 10 and SUSE 11

 

Tested with SUSE 10 SP1

Tested with SUSE 10 SP3 x64

Tested with SUSE 11 SP2 x64


Required Configuration

 

  1. SSH must be enabled and running on the default TCP port 22.
  2. On the Core Server, the root account must be added to Configure | Services | Scheduler | Change Logon | Alternate Credentials.

 

Required Software

 

  1. After a default installation of SUSE 10/11, the workstation agent installs with no additional software.
  2. The Server Manager agent required the sysstat rpm.

 

 

Debian / Ubuntu

(Tested with Kubuntu 7.0.4 and the push wasn't working, will have to test again later)

Required Configuration:

 

  1. SSH must be enabled and running on the default TCP port 22.
  2. On the Core Server, the root account must be added to Configure | Services | Scheduler | Change Logon | Alternate Credentials.

 

Required Software

These two applications, xinetd and openssh-server, are not installed by the default Kubuntu 7.0.4 installation CD.  There may be other software that is required, but these are the only two items required after a default installation.

 

  1. xinetd can be installed using the following command:
    sudo apt-get install xinetd
  2. openssh can be installed using the following command:
    sudo apt-get install openssh-server

Viewing all articles
Browse latest Browse all 182

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>