Upgrading the server with a fixlet

To automatically upgrade the server, run the fixlet from the BigFix console.

Before you begin

  • Back up the server so you can restore it if the upgrade fails.
  • Ensure that no files or directories in the installation directory are open in an external program. For example, that no log files are open in a text editor. Also, ensure that no PDF reports are being generated during the upgrade. Otherwise, the upgrade might fail with error code 41.

About this task

Linux You can upgrade the server with a fixlet only when you installed it as a root user. Otherwise, you must upgrade the server in interactive or silent mode.

Procedure

  1. Log in to the BigFix console.
  2. In the navigation tree, click Sites > External Sites > Fixlets and Tasks.
  3. Select Upgrade to the latest version of , and click Take Action.
  4. Select the computer on which you want to upgrade the server, and click OK.
    Tip: To check the status of the upgrade, in the navigation tree of the BigFix console, click Actions and look for the upgrade action. If the upgrade fails, check the upgrade logs. For more information, see: Server installation and upgrade logs.
  5. If the database schema changed between the versions, you are asked to update it. After the upgrade completes, log in to , and click Update Schema.
    Important: Update of the schema can take from a couple of minutes to a couple of hours depending on your environment size and how long you have installed.
  6. To ensure that all changes are processed, run an import. In , click Management > Data Imports, and click Import Now.
    Important: The first import after the upgrade might last longer because it includes the new software catalog.
  7. If any of the fixlets was updated on the action site, restart actions created by that fixlet. Otherwise, some new features might not work properly. View the fixlet version in the console to see which actions need to be restarted.
    To restart the actions, perform the following steps:
    1. In the navigation tree of the BigFix console, click Actions.
    2. Look for actions started by the fixlets that were updated, right-click each action, and click Stop Action.
    3. Run the updated version of the fixlet.

Results

The installer is downloaded to the chosen endpoint and the server is upgraded to the latest version. The server is stopped before the upgrade and started again when the process is complete. Additionally, new software catalog and PVU table are uploaded to . The versions that are uploaded are the newest ones that were available during the release of the application update to which you are upgrading. If the versions that are already available in are newer than the ones that are uploaded as part of the upgrade, the upload is skipped.
Note: If you use the disconnected scanner, make sure that you download the new software catalog and distribute it to each endpoint after the server upgrade.

What to do next

If you upgraded from version 9.2.1, and you had computer groups defined, subcapacity calculations are disabled for those groups after the upgrade. As a result, some of the panels and reports are not visible for users who are assigned to those computer groups. To re-enable subcapacity calculations, go to Management > Computer Groups, open a computer group, and select PVU, RVU MAPC and VPC. Then, click Save. For more information, see: Setting up computer groups.