Migrating to Symantec Client Security 3.0, part 1

Symantec.com > Enterprise > Support > Knowledge Base

Migrating to Symantec Client Security 3.0, part 1

Question/Issue:
Upgrading to Symantec Client Security 3.0, part 1 How to upgrade to Symantec Client Security 3.0, part 1 How to migrate to Symantec Client Security 3.0, part 1 Migrating to Symantec Client Security 3.0, part 1

Solution:

Page: 1 2 3 4 Next >

This document is divided into four sections, each on its own page. It's best to start by reading this document from beginning to end.

Part 1, Before you begin: Important information that you need to know for your migration to be successful.
Part 2, Migration overview: Description of the migration process for each component from start to finish.
Part 3, Laying the foundations: Reaching the first checkpoint, the installation of the Symantec System Center, from which the rest of the network can be deployed.
Part 4, Migrating clients and servers: Deploying the rest of the network.

Before you begin
This page gives the information that you need to know in order to plan the migration. This includes supported and unsupported migration paths, and factors that can affect the outcome of the migration.

Things to know to ensure a successful migration
The following is a list of critical information that you will need to know in order for your migration to be successful.

You cannot change your Symantec Client Security network topology while migrating. The current primary management server must remain the primary management server, and secondary servers must remain secondary. You can make changes to the network topology after the migration completes.
Before you migrate the primary server of the server group, make sure that the server group password contains six or more characters. If you need to change the password, allow time for all secondary servers in the server group to receive this change before starting the migration.
The system clocks of all management console computers, servers, and clients must be within the default of 24 hours plus or minus of the system time that is used by the primary management server. If this time requirement is not met, servers and clients will not authenticate the Symantec System Center logged on user and communications will fail.
All communications (except one) between clients and servers now occur over TCP, while legacy communications continue to occur over UDP. The communications exception is that discovery still occurs over UDP port 38293. If you have opened UDP ports in a firewall to allow communication, the firewall settings will need to be changed to allow TCP traffic on those ports instead.
When you migrate a legacy primary management server to this version of Symantec Client Security, and if its server group contains legacy servers and clients, the migrated primary management server will continue to support legacy servers and clients over UDP.
You cannot manage newly installed servers and clients with legacy server groups or legacy Symantec System Center consoles.
Symantec Client Security 3.0 scans for security risks that are associated with adware and spyware, runs in real time, and might cause conflicts with similar products offered by other vendors. Before you migrate antivirus servers and clients, disable or remove similar products offered by other vendors, especially those products that run in real time.
Any computer that will be managed must be migrated after the computer that manages it. That is, you must migrate the primary server before secondary servers, and any server before a client managed by it.
All newly installed or upgraded Symantec System Center consoles must run on the new version of Symantec Client Security, on either a management server or a managed client.
You must restart every management server that is migrated.

Migration paths
This section lists the platforms that are supported and unsupported when migrating to the current version of Symantec Client Security.

About supported and unsupported platforms
If the migration of a program is supported, the Symantec Client Security setup program automatically detects the software, removes the legacy components and registry entries, and installs the new version. If the migration from a previous product is not supported, you must uninstall the program before you run the Symantec Client Security installation program.

In most cases, if you are migrating from a legacy antivirus or firewall program that is not included in the list of supported migration paths, the installation program will fail during the installation, the user is notified that the installation was unsuccessful, and the Windows Installer log is updated.

However, in some cases, if you do not uninstall the unsupported product before you run the installation, the installation may appear to succeed, but the product may not function properly. You should always uninstall any antivirus or firewall program that is not included in the list of supported migration paths before attempting to install the current version.

Supported and unsupported platforms
Symantec Client Security can migrate seamlessly over the following products:

Symantec AntiVirus Corporate Edition 8.0 and later
Norton AntiVirus Corporate Edition 7.6 and later
Symantec Client Security, all versions
Symantec Client Firewall 5.0/5.1/7.1

Notes:

By default, when you migrate supported versions of legacy Symantec Client Firewall, the settings and rulebases on the legacy versions are also migrated with one exception. The exception is the intrusion prevention system (IPS) settings. The IPS engine in the new version is different than the engine in the legacy versions.
Installing legacy Symantec Client Firewall policy files on new versions of Symantec Client Firewall is not supported. Legacy policy files do not contain all of the new settings.
For Symantec Antivirus Corporate Edition 9.0 and later and Symantec Client Security 2.0 and later, custom installation paths are preserved. For example, if you installed the product in C:\Abc\MyAntiVirus\, the latest product files are install in this directory after migration. For all other versions, the legacy product is uninstalled from custom installation paths, and the latest product is installed in the default installation directory.

Symantec Client Security migration is not supported for the following products:

Symantec AntiVirus 64-bit client, version 9.0
Symantec AntiVirus 64-bit client version 10.0 does not support Intel® Itanium® 2 processors, which were supported in version 9.0.
Symantec Client Firewall Administrator
Norton AntiVirus
Norton Internet Security
Norton Personal Firewall
Norton SystemWorks
Symantec Desktop Firewall
Antivirus products from other vendors

Symantec Client Security migration is not supported for the following Administrator tools:

Symantec System Center
Symantec Client Firewall Administrator
LiveUpdate Administrator
Quarantine Server and Quarantine Console

You must uninstall previous versions of these tools, and then install the latest version.

Preserving custom settings
If you are not migrating from a supported migration path, any custom settings that you have are not saved during the migration process. On supported platforms, custom settings on clients and servers are preserved during migration.

Settings that are preserved for supported platforms include the following:

Scheduled scans and LiveUpdate sessions
All scan options
Symantec Client Firewall policy files
All Auto-Protect options
Custom exclusions and file extensions to scan
LiveUpdate host files
Symantec Client Security activity logs
Quarantine forwarding information

Notes:

When you uninstall a legacy version of Symantec Client Firewall Administrator, the policies directory and policy files in the directory are preserved. When you install the new version of Symantec Client Firewall Administrator, the policy files are also preserved.
If there are any items in Quarantine on Symantec Client Security clients or servers, they are migrated automatically to the Symantec AntiVirus Quarantine. However, if any items in Quarantine are determined by Symantec Client Security to be uninfected, they are deleted rather than migrated.

Click here to go to Part 2: Migration overview.

Page: 1 2 3 4 Next >

Available Translations:

Document ID: 2005032315105948
Last Modified: 10/03/2007
Date Created: 03/23/2005
Operating System(s): Windows 2000, Windows XP Home, Windows XP Professional Edition, Windows XP Tablet PC, NetWare 5.1, NetWare 6.0, NetWare 6.5, Windows XP 64-Bit Edition 2003, Windows Server 2003 32-bit Edition, Windows Server 2003 64-bit Edition, Windows XP Media Center Edition 2005
Product(s): Symantec AntiVirus Corporate Edition 10.0, Symantec Client Firewall 8.0, Symantec Client Security 3.0
Release(s): SAV 10.0, SAV 10.0 [All Releases], Symantec Client Firewall 8.6, Symantec Client Firewall 8.x [All versions], Symantec Client Security 3.0, Symantec Client Security 3.x [All versions]