Installing Trellix Agent 5.8.x on Ubuntu using a third-party tool

Prev Next

You can generate a Debian package and install Trellix Agent 5.8.x on Ubuntu systems using a third-party deployment tool such as YUM.

  1. Create Trellix Agent installation package.

    1. On the ePO - On-prem console, select Menu Systems System Tree, then select New Systems.

    2. Select Create and download agent installation package.

    3. Select the appropriate Trellix Agent version for Ubuntu (Linux) from the list.

    4. Click OK. The agentPackages.zip installation package containing installdeb.sh file is created.

    5. Save the file.

  2. Open Terminal, enter the path where you have saved the installdeb.sh file.

  3. Generate the maprovision.deb file from install.sh using the option (-p). Run the following command by giving root credentials.

    ./install.sh -p

    The maprovision.deb file is generated.

  4. Create mfema.deb and mfert.deb files by executing one of the following:

    1. Create files using install.sh file.

      1. Copy the install.sh file to Ubuntu systems.

      2. Open Terminal, enter the path where you have saved the install.sh file.

      3. Run the following command to extract the installation package.

        unzip install.sh
      4. The following installation files are extracted. Agent 5.6.6 and above includes version information in the filename.

        • MFEma-<build_number>.i686.deb

        • MFEma-<build_number>.x86_64.deb

        • MFEma-<build_number>.i686.deb

        Note

        Use an appropriate MFEma installation package based on the operating systems used.

        • MFEma-<build_number>.x86_64.deb for a 64-bit operating system

        • MFEma-<build_number>.i686.deb for a 32-bit operating system.

    2. Create files from the ePO - On-prem Main Repository.

      The files are available in the selected repository path. If the files are checked in to the current branch of the ePO - On-prem software repository,

      • For ePO - On-prem 5.10.0 Service Pack 1 or later, the default location of the installation package file is: C:\Program Files\Trellix\ePolicy Orchestrator\DB\Software\Current\EPOAGENT3700LYNX\Install\0409.

      • For ePO - On-prem 5.10.0 or earlier, the default location of this installation package file is: C:\Program Files\McAfee\ePolicy Orchestrator\DB\Software\Current\EPOAGENT3700LYNX\Install\0409.

      You can change the file path based on the branch selected.

  5. Create the MFEdx-ma-<build_number>.deb file:

    1. Save the DXL.zip file to an Ubuntu system.

      The DXL.zip file is available in the selected repository path. If the files are checked in to the current branch of ePO - On-prem the software repository, the path of the required files is,

      • For ePO - On-prem 5.10.0 Service Pack 1 or later, the default location of the installation package file is: C:\Program Files\Trellix\ePolicy Orchestrator\DB\Software\Current\EPOAGENT3700LYNX\Install\0409.

      • For ePO - On-prem 5.10.0 or earlier, the default location of this installation package file is: C:\Program Files\McAfee\ePolicy Orchestrator\DB\Software\Current\EPOAGENT3700LYNX\Install\0409.

      You can change the file path based on the branch selected.

    2. Open Terminal, enter the path where you have saved the DXL.zip file.

    3. Run the following command to extract the installation package.

      unzip DXL.zip
    4. The following installation files are extracted.

      • MFEdx-ma-<build_number>.x86_64.deb

      • MFEdx-ma-<build_number>.i686.deb

      Note

      Use an appropriate MFEdx-ma-<build_number> package based on the operating systems used.

      • MFEdx-ma-<build_number>.x86_64.deb for a 64-bit operating system

      • MFEdx-ma-<build_number>.i686.deb for a 32-bit operating system.

  6. Check in the MAProvision.rpm, MFEma.rpm, MFErt.rpm, and MFEdx-ma-<build_number>.rpm files into the third-party deployment tool (such as YUM) repository.

  7. Check in the mfema-<build_number>.i686.deb, mfema-<build_number>.x86_64.deb, mfert-<build_number>.i686.deb, and mfedx-ma-<build_number>.deb files into the third-party deployment tool (such as apt-get) repository.