Before upgrading

Perform these steps before upgrading the BigFix components:

  1. Close all BigFix consoles.
  2. Back up your BigFix server and database.
  3. Back up your license.pvk, license.crt, and masthead.afxm to a separate location on the BigFix server or to a USB key.
  4. If your server is configured in a DSA environment, increase the replication interval to prevent the replication from failing repeatedly during the upgrade. For additional information, see Changing the replication interval on Linux systems.
  5. Upgrade the BigFix components according to the following order:
    1. Servers and consoles (console and server must have the same version and must be upgraded at the same time.
    2. Relays
    3. Clients
    Servers, relays, and clients do not need to match versions and the upgrade of these components can occur at different times. Older clients can continue to report to newer relays or servers, but they might not have all the functions of the new release.
    Note: Existing BigFix proxy configurations are automatically migrated to the V9.2 proxy configuration settings and behavior. For more information about BigFix V9.2 proxy configuration settings, see Setting up a proxy connection.
  6. For DSA servers, upgrade first one DSA server to ensure the upgrade is successful and then the other DSA servers.
Note:
  • For large deployments, the server upgrade might take several minutes.
  • After an upgrade your deployment might be slow because the upgrade downtime can create a backlog of client reports, and it can take several hours for the IBM BigFix server to process this backlog after the upgrade has completed.