11.4 Upgrading Secure Configuration Manager

This section provides requirements and instructions for upgrading Secure Configuration Manager.

11.4.1 Upgrading Secure Configuration Manager

If a Windows agent exists on the Core Services computer, the setup program upgrades the agent. Otherwise, the setup program installs and registers a new Windows agent on the computer. The new agent and the endpoint representing the computer’s operating system become a managed system in your asset map.

To upgrade Secure Configuration Manager:

  1. Ensure that you have prepared your environment for upgrade. For more information, see Preparing Your Environment for Upgrade.

  2. Ensure that the computers on which you want to upgrade Secure Configuration Manager components meet the specified requirements. For more information, see Section 2.0, Planning Overview and Step 6 of Preparing Your Environment for Upgrade.

  3. To upgrade Core Services, Web console, and the Secure Configuration Manager database, complete the following steps:

    1. Log in to the Core Services computer with the appropriate permissions:

      • (Conditional) If Core Services and the database are installed on the same computer, log on as a user with local administrator rights.

      • (Conditional) If Core Services and the database are installed on different computers, you must log on to the Core Services computer with an account that has administrator rights in SQL Server.

        NOTE:If Core Services and the Secure Configuration Manager database are installed on different computers, the Secure Configuration Manager installation kit detects the database location and upgrades it along with Core Services.

    2. Exit all programs that are open on the computer.

    3. Run the setup.exe, located by default in the CDImage directory of the Secure Configuration Manager installation kit.

    4. Select the type of authentication: Windows or SQL.

      If you select SQL, provide the user name and password for the account.

    5. Click Upgrade.

    6. Follow the instructions in the wizard until you have finished upgrading the product.

    7. (Conditional) For the Dashboard Installation Requirement page, if the Dashboard is not installed in your environment, you can either specify the IP address and host for the server where you plan to install the Analytics Database or click Next without entering values.

      If you do not enter values, you can specify the settings after you install the Dashboard. Otherwise, the Web console will not function appropriately. For more information, see the Help for the Web console or Configuring the Web Console in the User's Guide for Secure Configuration Manager.

    8. (Conditional) If the upgrade process prompts you to install the Windows agent, you must specify a run-as account for the Windows agent service. For more information about the Windows agent service and permissions, see the Secure Configuration Manager Windows Agent Installation and Configuration Guide.

    9. Do not stop or start Core Services until the upgrade process completes.

      After the upgrade window closes, Secure Configuration Manager continues to run the upgrade processes.

  4. To upgrade Windows consoles, complete the following steps on each console computer:

    1. Log in to the console computer with an administrator account.

      NOTE:You must wait until the database upgrade completes before you can log in to a Secure Configuration Manager console.

    2. Exit all programs open on the computer.

    3. Run the setup program from the root folder of the Secure Configuration Manager installation kit.

    4. (Conditional) If you accept the terms in the license agreement, click Accept and then click Next.

    5. Select Upgrade and then click Next.

    6. Follow the instructions in the wizard until you have finished installing the product.

  5. Upgrade the Dashboard. Click Cancel when prompted if you do not want to upgrade the Dashboard on the current server.

  6. When you have completed the upgrade, re-run the AutoSync wizard in Secure Configuration Manager to download the latest security knowledge. For more information about the AutoSync feature, see Updating Security Knowledge and the User's Guide for Secure Configuration Manager.

Troubleshooting Database Upgrade Failure

If your database upgrade fails due to a power outage, users connecting to the database during upgrade, or other errors, restore the database backup you made prior to upgrade and run the database upgrade again. You can find information to help you troubleshoot database issues in the log files. To access your log files, enter %TEMP% in the Windows Run command window. For information about restoring a database, see the Microsoft SQL Server documentation.