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


Solution:

Page: < Previous 1 2 3 4 Next >

Migration overview
The goal of migration is to move Symantec Client Security from a previous version to the current version while preserving current settings and with as little uninstallation of previous versions as possible. Migration occurs by overinstalling the new version of Symantec Client Security management servers and clients on computers that run the old version.

The following table gives an overview of the migration process for each component of Symantec Client Security:

Component	Migration overview
Management servers	When you migrate a server, the installation automatically detects whether the server is primary or secondary, and migrates and configures it appropriately. You cannot designate a new primary server during a migration. You do not need to uninstall management servers before you install the new version. The overinstall process saves legacy settings, uninstalls the legacy software, and then installs the latest version. Furthermore, server group settings will be lost if you uninstall migration-supported legacy management servers and clients rather than migrating them.
Clients	When you migrate a client, the overinstall automatically detects the client, and migrates and installs it appropriately. You do not need to uninstall management servers before you install the new version.
Symantec System Center	You cannot migrate the Symantec System Center console with an overinstall. You must uninstall the legacy version, and then install the new version. When you upgrade the first instance of the Symantec System Center console in your network, you must uninstall the Symantec System Center console, overinstall one or more management servers in a server group, and then reinstall the Symantec System Center console in a very specific order.
LiveUpdate servers	If you have already set up LiveUpdate FTP servers or UNC paths, there is no need to modify them. They will continue to be used the same way with Symantec Client Security.
Quarantine Console or Server	You cannot migrate the Quarantine Console or Server with an overinstall. If either is installed on any server or client that you plan to migrate, uninstall the legacy software first.

Steps to migrating to the current version of Symantec Client Security
Migrating to the current version of Symantec Client Security includes the following steps:

Create a migration plan
Before you begin to install the Symantec Client Security client, server, and administration upgrades, you should have a solid understanding of your network topology and a streamlined plan to maximize the protection of the resources on your network during the upgrade. Migrating your entire network to the current version rather than managing multiple versions of Symantec Client Security is strongly recommended.

Uninstall legacy Quarantine Console or Server
If legacy Quarantine Console or Server is installed on any server or client that you plan to migrate, uninstall the legacy software first.

Upgrade the management infrastructure
The first checkpoint to be reached in migration is to install at least one new version of the Symantec System Center in the first server group. However, to install the Symantec System Center, the current version of Symantec Client Security must already be installed on the computer, and on any management server up the management chain from that computer. Therefore, to reach this point, you must first migrate a "path" to the Symantec System Center. The exact procedure depends on where the Symantec System Center will be installed, and is discussed in the next section.

This process involves uninstalling the legacy version of the Symantec System Center, upgrading the primary management server to the new version, upgrading the Symantec software that protects the computer that runs the Symantec System Center, and then installing the new version of the Symantec System Center.

Back up the server group root certificate
After unlocking the server group for the first time, it is vital to back up the server group root certificate. This allows recovery in case of catastrophic failure of the primary server.

Migrate secondary management servers in the server group
After you upgrade the initial instance of the Symantec System Center, you then migrate secondary management servers in the server group that contains the computer that runs the Symantec System Center.

Migrate the clients in the server group
After all management servers in the server group are migrated, deploy the new version of Symantec Client Security to clients.

Migrate management servers and clients in other server groups
Migrate servers and clients in other server groups by migrating the primary management server first, migrating the secondary management servers, and then migrating the clients. You can perform this server migration remotely from the new version of the Symantec System Center.


Click here to go to Part 3: Laying the foundations.

Page: < Previous 1 2 3 4 Next >

Document ID: 2005032315142248
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]