38Installing Symantec Critical System Protection on Windows
Installing the management server
Using the SQL Server Enterprise Manager, do the following:
■Drop the Symantec Critical System Protection database.
■Select the Security folder of the instance, click Logins, select the Symantec Critical System Protection user accounts, and then
You must delete the following accounts:
■scsp_ops
■scsp_guest
■scsp_plugin
■scspdba
Once you have cleaned up the database from the previous installation, you can install the new management server. If you fail to clean up these items, you will get a Database Population Failed error during the new installation.
Management server installation settings and options
Installation prompts you to enter a series of values consisting of port numbers, user names, passwords, and so forth. Each database that you can install uses different default settings and options for the management server and database. Also, some settings for evaluation installation are
Table
| Table | Management server installation settings | ||
|
|
|
| |
Setting | Default/options |
| Description | |
|
|
| ||
Installation type | Evaluation Installation, Install | Select the type of installation. | ||
| MSDE on the local system | If you install a database on SQL Server, the instance | ||
|
|
| ||
| You have the following options: | must be running. | ||
| Evaluation installation | The Install Tomcat Component Only option requires | ||
| ■ Install MSDE on the local | that you provide the file path to the following files | ||
| from an installed management server: | |||
| system |
| ||
|
|
|
| |
| ■ Use an existing MS SQL | ■ | server.xml | |
| instance |
| ■ | |
| Production installation |
|
| |
| ■ Install Tomcat and create the |
|
| |
| database schema |
|
| |
| ■ Install Tomcat Component |
|
| |
| ONLY |
|
|
|
|
|
|
|
|