Migrating to Symantec AntiVirus Corporate Edition 10.0, part 1

Article:TECH101217  |  Created: 2005-01-14  |  Updated: 2009-01-10  |  Article URL http://www.symantec.com/docs/TECH101217
Article Type
Technical Solution


Environment

Issue



Upgrading to Symantec AntiVirus Corporate Edition 10.0, part 1 Migrating to Symantec AntiVirus Corporate Edition 10.0, part 1 How to upgrade to Symantec AntiVirus Corporate Edition 10.0, part 1 How to migrate to Symantec AntiVirus Corporate Edition 10.0, part 1

Symptoms
This document gives a detailed description of migrating to Symantec AntiVirus Corporate Edition 10.0 from previous versions of Symantec AntiVirus Corporate Edition or Norton AntiVirus Corporate Edition.



Solution



Page 1 2 3 4 Next >

This document is divided into four sections, each on its own page. It's best to read this document from beginning to end.
  • Part 1, Before you begin: 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 section includes what you need to know in order to plan the migration. This includes supported and unsupported migration paths, and information that can affect the outcome of the migration.

Things to know to ensure a successful migration
Here is critical information that you need to know in order for your migration to be successful.
  • You cannot change your Symantec AntiVirus 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 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 AntiVirus, 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 AntiVirus Corporate Edition 10.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 scan 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 Symantec System Center consoles must run on the new version of Symantec AntiVirus, 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 AntiVirus.

About supported and unsupported platforms
If the migration of a program is supported, the Symantec AntiVirus 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 AntiVirus 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 will be notified that the installation was unsuccessful, and the Windows Installer log will be 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 AntiVirus can migrate seamlessly over the following products:
  • Symantec AntiVirus Corporate Edition 8.0 and later
  • Norton AntiVirus Corporate Edition 7.6 and later


Notes:
  • The Symantec AntiVirus Administration Guide indicates that you can migrate legacy versions of Symantec Client Security to Symantec AntiVirus Corporate Edition 10.0. This is in error. You can only migrate to the current version of Symantec Client Security from legacy versions of Symantec Client Security.
  • For Symantec Antivirus Corporate Edition 9.0 and later, custom installation paths are preserved. For example, if you installed the product in C:\Abc\MyAntiVirus\, the latest product files are installed 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 AntiVirus migration is not supported for the following products:
  • Symantec Client Security, all versions
  • Symantec Client Firewall 5.0/5.1/7.1
  • 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.
  • Norton AntiVirus
  • Norton Internet Security
  • Norton Personal Firewall
  • Norton SystemWorks
  • Symantec Desktop Firewall
  • Antivirus products from other vendors

Symantec AntiVirus migration is not supported for the following Administrator tools:
  • Symantec System Center
  • 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
  • All Auto-Protect options
  • Custom exclusions and file extensions to scan
  • LiveUpdate host files
  • Symantec AntiVirus activity logs
  • Quarantine forwarding information


Note: If there are any items in Quarantine on Symantec AntiVirus clients or servers, they are migrated automatically to the Symantec AntiVirus Quarantine. However, if any items in Quarantine are determined by Symantec AntiVirus to be uninfected, they are deleted rather than migrated.



Page 1 2 3 4 Next >





Legacy ID



2005041411005848


Article URL http://www.symantec.com/docs/TECH101217


Terms of use for this information are found in Legal Notices