Before upgrading

Perform these steps before upgrading the BigFix components:

1. Close all BigFix consoles.
2. Back up your BigFix server and database.
3. Upgrade SQL Databases. SQL 2000 database is no longer supported.
4. Back up your license.pvk,license.crt, and masthead.afxm to a separate location on the BigFix server or to a USB key.
5. Increase the replication interval to prevent the replication from failing repeatedly during the upgrade. For additional information, see Changing the replication interval on Windows systems.
6. Upgrade the BigFix components according to the following order:
   1. Servers and consoles. These components must match their versions 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 functionality of the new release.
   Note: Existing BigFix proxy configurations defined on the server 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.

   If the existing proxy configuration exploits the BESGather_Service, during the migration you are requested to enter the password of the user that you specified for the BESGather_Service. The migration process uses that password to access the Internet Explorer and to map the proxy configuration settings into the set of registry keys used in V9.2 and documented in Proxy configuration settings for server and relays.

7. For DSA servers, upgrade first one DSA server to ensure the upgrade is successful and then the other DSA servers.
8. After the upgrade, run the BigFix Administration Tool to update the data with SHA-2 signature, to update a remote database and to set the NIST security standards, if needed.