Planning the installation
About the Windows NT agent installation
27
Specifying the management server list for an agent
To use simple failover for an agent, you must provide the list of primary and alternate management servers using one of the following methods:
■If you are installing Symantec Critical System Protection for the first time, you provide the list of primary and alternate management servers during agent installation.
■If you are upgrading to Symantec Critical System Protection 5.1.1 or higher, you provide the list of primary and alternate management servers using the agent config tool.
To use simple failover, you must upgrade the management server, management console, and agent to version 5.1.1 or higher.
See “Migrating legacy installations of Symantec Critical System Protection” on page 101.
The primary and alternate management server host names or IP addresses configured for a single agent must be Tomcat servers that talk to a single Symantec Critical System Protection database. Using multiple databases can result in unexpected agent behavior.
The primary and alternate management servers must use the same server certificate and agent port.
About the Windows NT agent installation
You can install the Symantec Critical System Protection agent on computers that run Windows NT Server.
The Windows NT agent differs from the other the Windows agents in the following ways:
■The Windows NT agent has a separate installation kit
■All Windows NT agents must use the Windows NT prevention policy. The Windows NT prevention policy has significantly fewer PSETs and options than the other Windows prevention policies. The Windows NT prevention policy only works with Windows NT agents.
■The Windows NT policy is not part of the Symantec Critical System Protection installation. You must install the Windows NT policy separately. See “Installing the Windows NT policy” on page 64.
■Windows NT Server does not provide a safe mode startup to allow booting a Windows NT agent without the Symantec Critical System Protection
