Symantec Critical System Manuel D’Utilisation

Page de 122
109
Migrating to the latest version
Migrating legacy agent software
(and each ungrouped agent), noting the stock policies and the custom 
policies that are applied. You should be able to find equivalent Symantec 
Critical System Protection policies for the Symantec Host IDS stock policies 
that you applied.
Uninstall the Symantec Host IDS agent, and install the Symantec Critical 
System Protection agent on each client to be migrated. You should have 
pre-configured your Symantec Critical System Protection groups using the 
Symantec Critical System Protection management console, placing the 
appropriate stock and custom policies in each group and configuring the 
policy option settings.
If you were performing event forwarding in Symantec Host IDS, perhaps 
you can configure the Symantec Critical System Protection database to do 
this for you.
Migrating legacy agent software
Before you migrate agent software, install the latest version of Symantec 
Critical System Protection management server and management console, and 
then log on to the management console. When you log on to the management 
console for the first time, you are prompted to create the default administrator 
login credentials. The default user name is symadmin; you create the password 
the first time that you log on to the management console.
To migrate legacy agent software
Install the latest version of Symantec Critical System Protection agent on 
the computers that run the legacy agent software.
See
The installation routine automatically uninstalls the legacy software and 
installs the latest software.
Preparing for detection policy migration
The following procedures are necessary to prepare for migrating legacy 
detection files: 
Installing the authoring environment and policy conversion utility
Copying files required for the policy conversion utility