Symantec Critical System manual Migrating other legacy agent installations

Migrating to the latest version

Migrating other legacy agent installations

105

		Table 5-1	Agent config tool commands
Command	Syntax			Description
-test	To test first server in list (default):			Test the connection information for a server in the
	■	Windows: sisipsconfig -t		management server list.
	■	UNIX: sisipsconfig.sh -t
	To test nth server in list:
	■	Windows: sisipsconfig -t n
	■	UNIX: sisipsconfig.sh -t n

To specify the management server list for an agent

1At a command prompt, locate the folder that contains the agent config tool, and then navigate to that directory.

2At a command prompt, type sisipsconfig -host(Windows) or sisipsconfig.sh -host(UNIX), followed by a comma-separated list of server host names or IP addresses, and then press Enter.

Migrating other legacy agent installations

You can migrate legacy software agent installations for the following software:

■Symantec Intruder Alert™ 3.6 and higher

■Symantec Host Intrusion Detection System (Symantec Host IDS) 4.0 and higher

Agent software migration is straightforward. When you install Symantec Critical System Protection agents, the installation kit automatically detects legacy agents, uninstalls the legacy software, and installs the latest version.

Note: You cannot migrate server or management software. If an agent runs on a computer that also runs a legacy server or manager, you must first uninstall the legacy software before you migrate the agent.

You can migrate legacy customized detection policy files for the following software:

■Symantec Intruder Alert 3.6 and higher

■Symantec Host IDS 4.1 and higher

It is not necessary to migrate uncustomized stock policy files. The new stock policy files are migrated for you.