Upgrading the server

  1. Copy the BigFix installable image to the BigFix server computer and extract it to a folder.
  2. On the BigFix server computer, run the BigFix server upgrade script:
    ./install.sh -upgrade [-opt BES_LICENSE_PVK=<path+license.pvk>] 
                 [-opt BES_LICENSE_PVK_PWD=<password>]
    where:
    -opt BES_LICENSE_PVK=<path+license.pvk>
    Specifies the private key file (filename.pvk). This private key file and its password are required to update the product license and perform the required SHA-256 signature updates in the BigFix database.
    Note: The notation <path+license.pvk> used in the command syntax stands for path_to_license_file/license.pvk.
    -opt BES_LICENSE_PVK_PWD=<password>
    Specifies the password associated to the private key file (filename.pvk).

    The use of the optional parameters BES_LICENSE_PVK and BES_LICENSE_PVK_PWD depends on the current release or patch level that the installer is upgrading and, in the event the upgrade procedure requires to sign again the database, they are explicitly asked for during the upgrade process. As an alternative, you can specify them anyway and, if they are not required, they are ignored by the upgrade process.

    The install.sh server script upgrades all the components it detects on the local server.

    If a Web UI instance previously installed with a Fixlet is detected, also the Web UI component is upgraded.

    Note: Before starting to upgrade, the upgrade procedure runs a set of prerequisite checks. If any of them fails, you can do the required corrective actions and then rerun the upgrade procedure. For more information, see Upgrade prerequisite checks.
  3. Run the Administration Tool (./BESAdmin.sh on Linux) to distribute the updated license:
    /opt/BESServer/bin/BESAdmin.sh -syncmastheadandlicense -sitePvkLocation=<path+license.pvk>
    	                   -sitePvkPassword=<password> 
Note:
  1. For troubleshooting information see /var/log/BESInstall.log and /var/log/BESAdminDebugOut.txt files.
  2. After upgrading the server to Version 9.5.5, due to data movement in the database, the Web UI must select and get new data. This might temporarily prevent the FillDB process from processing the client reports.