Upgrade to Traps 3.4

The Traps™ 3.4 release comprises the Endpoint Security Manager (ESM) Server, the ESM Console, and the Traps agent. Use the following workflow to upgrade the Traps components:
  1. Plan for the upgrade.
    • Prioritize the downtime for each ESM Server according to your environment and the requirements of the agents connected to the ESM Server. Identify the ESM Servers that serve the highest number of agents and plan to stop services on those ESM Servers last and upgrade them first.
    • Ensure that you have the credentials for the user who connects to the database before you begin the upgrade.
    Hint
    : Windows authentication uses a domain account and SQL authentication uses a local SQL account on the database server.
    • Review the Prerequisites for Traps components and adjust your configuration to meet those prerequisites as needed.
  2. Disable service protection on all server-side agents installed on ESM Servers and ESM Consoles.
    1. From the ESM Console, select
      Settings
      Agent
      Settings
      and then
      Add
      a
      Service Protection
      .
    2. Disable service protection
      .
    3. On the
      Objects
      tab, specify the servers to which the rule should apply.
    4. Apply
      the rule.
    5. Verify that each Traps agent received the new rule (on the Traps console, select
      Policy
      ). If needed,
      Check-in now
      to force Traps to request the latest security policy from the ESM Server.
  3. Stop services before upgrading the ESM Server software.
    The database can connect to only ESM components that are running the same release. To avoid conflicts during the upgrade process, ensure that services remain disabled until after you successfully upgrade all ESM components.
    If you use a third-party watchdog to monitor services, you may need to perform additional steps to ensure that the watchdog software does not attempt to restart the services.
    From the Services manager,
    Stop
    the
    Endpoint Security Manager
    service on all ESM Servers.
  4. (
    Multiple ESM Server deployments only
    ) Stop services before upgrading the ESM Console software.
    This step is not required for standalone deployments with only a single ESM Server and an ESM Console.
    Stop IIS services on the server on which the ESM Console is installed:
    Dedicated Server
    If the ESM Console is the only web application running on the ESM Console server, stop the
    World Wide Web Publishing Service
    . Alternatively, you can stop the service from a command prompt by issuing the
    IISreset /stop
    command.
    Shared Server
    If you run additional web applications on your ESM Console server (not recommended), stop the ESM Application Pool service (ESMAppPool) in the Internet Information Services (IIS) Manager to avoid affecting other applications.
    To stop the application pool:
    1. Open the IIS Manager.
    2. Expand the server and select
      Application Pools
      .
    3. Right-click
      ESMAppPool
      and
      Stop
      the service.
  5. Back up your database.
    To preserve all data in case the installation is unsuccessful, first ensure that services are down on relevant ESM components and then back up your database.
  6. Upgrade the ESM Server.
    In a deployment with multiple ESM Servers, choose one ESM Server on which to test the upgrade. Resolve any issues encountered during the upgrade before proceeding to upgrade the ESM Console and any additional ESM Servers.
    During the upgrade of the ESM Server, the installer updates the database according to the requirements of the database version. If there is no change between the database versions, the installer does not make any changes to the database.
    1. Launch the ESM Core installer file and click
      Next
      to begin the installation.
      To troubleshoot installation issues, use Msiexec to log verbose output to a file.
    2. Enter the username and password used to connect to the database and then
      Verify
      the connection:
      • Windows authentication, format:
        domain\username
      • SQL authentication format:
        sqlservername\username
    3. If the installer successfully verifies the database connection, click
      OK
      .
    4. Click
      Install
      .
    5. Click
      Finish
      .
  7. Upgrade the ESM Console.
    1. Launch the ESM Console installer file and click
      Next
      to begin the installation
      To troubleshoot installation issues, use Msiexec to log verbose output to a file.
    2. Enter the username and password to connect to the database and then
      Verify
      the connection.
      • Windows authentication format:
        domain\username
      • SQL authentication format:
        sqlservername\username
    3. If the installer successfully verifies the database connection, Click
      OK
      .
    4. Click
      Install
      .
    5. Click
      Finish
      .
    6. Restart the
      IIS Admin Service
      on the server on which the ESM Console is installed.
    7. Verify that you can log in to the ESM Console.
  8. Upgrade additional ESM Servers.
    For each additional ESM Server, verify the services are disabled (see 3) and then repeat 6 to upgrade the ESM Server software.
  9. Import the latest content update to take advantage of the latest recommended default policy.
  10. Upgrade the Traps agents.
    1. Select
      Settings
      Agent
      Actions
      and
      Add
      and agent.
    2. Select
      Agent Installation
      .
    3. Select
      Upgrade from path
      .
    4. Enter the
      Uninstall Password
      ,
      Browse
      to the installation file, and then
      Upload
      .
    5. Apply
      the rule.

Related Documentation