Before upgrading
Before you Begin:
You must enable the “Enhanced Security” before upgrading BigFix Platform to Version 11 as described in V11 Overview.
Perform these steps before upgrading the BigFix components:
- Ensure that the BigFix WebUI service is stopped before starting to upgrade the BigFix components, and do not start it again until the overall upgrade procedure completes successfully.
- Close all BigFix consoles.
- Back up your BigFix server and database as described in Server Backup.
- Back up your
license.pvk
,license.crt
, andmasthead.afxm
to a separate location on the BigFix server or to a USB key. - Ensure that you have enough free space for the BigFix database. The free space projection involves a number of factors: the row counts of specific tables, the density of the data pages storing the tables and indexes, and specific database options for log management and table compression.
- If your server is configured in a DSA environment, increase the replication interval to prevent the replication from failing repeatedly during the upgrade. For more information, see Changing the replication interval on Linux systems.
- Upgrade the BigFix components in the
following order:
- Servers and consoles. The console and the server must have the same version and must be upgraded at the same time.
- Relays
- Clients
Note: Existing BigFix proxy configurations are automatically migrated to the V10.0 proxy configuration settings and behavior. For more information about BigFix V11.0 proxy configuration settings, see Setting up a proxy connection. - In a DSA environment run the BigFix Server upgrade on the primary server first. Then upgrade the secondary servers.
Note:
- For large deployments, the server upgrade might take several minutes.
- After upgrading, you might initially experience a slower deployment. The upgrade downtime might create a backlog of client reports and it might take several hours for the BigFix server to process this backlog after the upgrade completed.
- Check your password characters. After the upgrade, passwords containing non-ASCII characters are corrupted and users cannot log in anymore. In this case, before using the product, you must reset this type of password to either the same password or a new password without non-ASCII characters.