|
|
|
|
|
|
|
-
Close all Secure Configuration Manager consoles and shut down Core Services.
For more information, see Preparing to Upgrade.
|
|
-
(Conditional) If you are upgrading the Dashboard, ensure that all user sessions are closed.
|
|
-
Using Microsoft SQL Server Enterprise Manager, ensure that no users are connected to the Secure Configuration Manager database.
IMPORTANT:Before beginning to upgrade Secure Configuration Manager, close all the windows that are open against Vigilent database in SQL Server Management Studio.
|
|
-
Back up your Secure Configuration Manager database.
For more information, see the Microsoft SQL Server documentation.
|
|
|
|
|
|
-
Upgrade Core Services and the Secure Configuration Manager database. After the upgrade dialog box closes, Secure Configuration Manager continues to run the upgrade process. Do not stop Core Services until the upgrade fully completes.
For more information, see Upgrading Secure Configuration Manager.
|
|
-
Upgrade each Windows console computer. Secure Configuration Manager displays a message if you attempt to log in to the Web or Windows console before the database upgrade process completes.
For more information, see Upgrading Secure Configuration Manager and the Release Notes.
|
|
|
|
-
Run the AutoSync update service to download the latest security checks and policy templates.
For more information, see Updating Security Knowledge.
|
|
|
|
-
(Conditional) If you do not have the latest version of an agent, download the appropriate software update from the web site and use the instructions provided in the installation kit to upgrade the agent or see Updating Agent Content in the User's Guide for Secure Configuration Manager.
|
|
-
(Conditional) Upgrade the Dashboard, if it is on a separate server than the Core Services computer.
For more information, see Upgrading the Dashboard.
|