Installing the UNIX Agent on Remote Computers

In most cases, you install the UNIX agent locally on a computer using the install.sh script interactively. You can install the UNIX agent on remote computers using the install.sh script and a configuration file or using virtually any software distribution or package installer program. This chapter provides an overview of these alternatives for installing the agent on UNIX or Linux computers.

Installing the Agent Silently using a Configuration File

You can automate agent installation by running the install.sh script in non-interactive mode:

install.sh -n

In this mode, the script uses configuration details specified in the centrifyda-install.cfg file. If this file is not found, the install.sh script uses its built-in default values.

To specify configuration values, edit the sample centrifyda-install.cfg file in its default location, or create a new text file with the same name, and then run the install.sh script.

In the file, INSTALL=Y installs the agent, and INSTALL=U upgrades the agent.

By default, the script returns an exit code of 0 if the operation is successful. To return exit codes that provide more detailed information about the result, use:

install.sh -n --custom_rc

This return code Indicates
CODE_SIN=0 Successful install
CODE_SUP=0 Successful upgrade
CODE_SUN=0 Successful uninstall
CODE_NIN=24 Did nothing during install
CODE_NUN=25 Did nothing during uninstall
CODE_EIN=26 Error during install
CODE_EUP=27 Error during upgrade
CODE_EUN=28 Error during uninstall
CODE_ESU=29 Error during setup; for example, unsupported operating environment or invalid arguments

Using Other Programs to Install the UNIX Agent

Auditing-related files are bundled with the core Delinea Agent files into a platform-specific software package. You must install the Delinea Agent on the audited computer before you enable the auditing service.

To install auditing using a native installation mechanism:

  1. Log on as a user with root privileges.

  2. If you want to install from a CD and the drive is not mounted automatically, use the OS-specific command to mount the cdrom device.

  3. Copy the appropriate package to a local directory.

    For Solaris 10:

    cp /cdrom/cdrom0/Unix/centrifyda-n.n.n-sol10-sparc-local.tgz .

    For Red Hat Enterprise Linux:

    cp /mnt/cdrom/Unix/centrifyda-n.n.n-rhel5-x86_64.rpm .

    For SuSE Linux:

    cp /mnt/cdrom/Unix/centrifyda-n.n.n-suse11-x86_64.rpm .

  4. If the software package is a compressed file, unzip and extract the contents. For example, on Solaris:

    gunzip -d centrifyda-n.n.n-sol10-local.tgz
    tar -xf centrifyda-n.n.n-sol10-sparc-local.tar

  5. Run the installation command appropriate to the operating environment.

    For Red Hat Linux, you can use:

    rpm –ivh centrifyda-n.n.n-rhel5-x86_64.rpm

    For SuSE Linux, you can use:

    rpm –ivh centrifyda-n.n.n-suse11-x86_64.rpm

    For Solaris, you can use:

    pkgadd –d CentrifyDA -a admin

    You can also use other programs, such as SMIT or YAST, to install the agent package.

  6. If you are using an installation with a name other than DefaultInstallation, you need to configure it with dacontrol or using group policy.

    If there is an installation with the name DefaultInstallation the UNIX agent uses it by default. For more information about specifying the installation, see Configuring the installation for an agent.

  7. After installing the package, use dainfo to verify that auditing is installed and running. You should see output similar to the following:

    Pinging adclient: adclient is available Daemon status: Online Current collector: DC2008r2-LG.pistolas.org: 5063:HOST/dc2008r2-lg@PISTOLAS.ORG Session offline store size: 0.00 Bytes Session despool rate: 0.00 Bytes/second Audit trail offline store size: 0.00 Bytes Audit trail despool rate: 0.00 Bytes/second Getting offline database information: Size on disk: 52.00 KB Database filesystem use: 3.06 GB used, 15.52 GB total, 12.45 GB free DirectAudit NSS module: Active User (root) audited status: Yes DirectAudit is not configured for per-command auditing.