11.3 Preparing to Upgrade

Before upgrading, you might want to back up the configuration settings for Secure Configuration Manager. You can also shut down running processes and ensure that users are not logged into the consoles or Dashboard.

11.3.1 Backing Up Configuration Data

To back up configuration data before you upgrade Secure Configuration Manager:

  1. Back up the SCM installation directory. Generally, the installation directory is C:\Program Files (x86)\NetIQ\Secure Configuration Manager.

  2. Back up the SCMNSS directory. Generally, the SCMNSS directory is C:\scmnss.

  3. Back up registry keys by exporting the following registry keys. To export the registry keys, open the command prompt and type regedit.exe, and then go to File > Export. Save the registry key file in .reg format.

    • HKEY_CURRENT_USER\Software\PENTASAFE

    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PSService

    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PENTASAFE

    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\NetIQ Core Services

    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\NetIQ Secure Configuration Manager

  4. Back up the SCM shortcuts by backing up the C:\ProgramData\Microsoft\Windows\Start Menu\Programs\NetIQ Secure Configuration Manager directory.

    NOTE:The ProgramData directory might be hidden. If it is not visible, change the folder options settings to show the hidden files and folders.

  5. Back up the Vigilent database.

11.3.2 Preparing Your Environment for Upgrade

Before upgrading Secure Configuration Manager, you need to prepare the environment through the following steps.

  1. Verify that the version of Secure Configuration Manager currently running in your environment is supported by the upgrade process. For more information, see Secure Configuration Manager Upgrade Checklist.

  2. To ensure a clean snapshot of your Secure Configuration Manager database, close all consoles and shut down Core Services. Follow these steps to shut down Core Services:

    1. Log on to the Core Services computer.

    2. Click Services in the Administrative Tools program folder, and then click NetIQ Core Services.

    3. On the Action menu, click Stop.

  3. Using Microsoft SQL Server Enterprise Manager, ensure no users are connected to the Secure Configuration Manager database.

  4. To ensure that your session is not timed out during the upgrade, modify time-out settings, by using the following steps:

    1. Log in to the Microsoft SQL Server Management Studio.

    2. Select your SQL server by right-clicking the name of the server, and then go to Properties > Connections.

    3. Set the value of the Remote Query Timeout property to 0.

  5. Back up your Secure Configuration Manager database. For more information, see the Microsoft SQL Server documentation.

  6. Ensure the free disk space allocated for the database upgrade is at least four times the size of the current VigilEnt.mdf file. By default, you can find the VigilEnt.mdf file at C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data.

  7. To ensure that the Browser Service is running in SQL Server, complete the following steps:

    1. Open SQL Server Configuration Manager.

    2. In the left pane, select the SQL Server services.

    3. In the right pane, ensure SQL Server Browser is set to Running.

    4. (Conditional) If the SQL Server Browser is stopped, select SQL Server Browser, and on the Action menu, click Start.

  8. To ensure that the TCP/IP protocol is enabled in SQL Server, complete the following steps:

    1. In the left pane, expand SQL Server Network Configuration and select Protocols for <database server name>.

    2. In the right pane, ensure that TCP/IP is set to Enabled.

    3. (Conditional) If the TCP/IP protocol is disabled, select TCP/IP, and on the Action menu, select Enable.

  9. Before you run the upgrade program, ensure that no users are connected to the database and no Secure Configuration Manager consoles are running. The database upgrade fails if users attempt to connect to the database at any time during the upgrade process.

11.3.3 Stopping Scheduled Jobs Before Upgrade

You cannot run scheduled jobs during the upgrade of Secure Configuration Manager. Scheduled jobs that complete or start during the upgrade process indicate a zero score upon completion. You must run the jobs again.

Stopping Pending Jobs

  1. In the Pending jobs queue, right-click the job.

  2. On the context menu, click Cancel.

Preventing Jobs from Starting

  1. In the Scheduled jobs queue, right-click the job.

  2. On the context menu, click Disable.

  3. After upgrading Secure Configuration Manager, right-click the job in the Scheduled jobs queue.

  4. On the context menu, click Enable.