This document describes how to migrate to Symantec Endpoint Protection 11.0 Release Update 6 (RU6).
Before you begin
This section gives the information that you need to know in order to plan for migration. This information includes supported migration paths and factors that can affect the success of the migration.
This document is meant only for migrations in which a previous version of Symantec Endpoint Protection 11.0 exists on the network or on individual computers. If no previous versions of Symantec Endpoint Protection products are already installed, please read the installation guide.
Things to know to ensure a successful migration
The following is a list of critical information that you need to know in order for your migration to succeed.
Symantec Endpoint Protection 11.0.6 (RU6) can migrate seamlessly over the following:
For more information, see the Symantec Knowledge Base article Migration paths for Symantec Endpoint Protection 11.0.
Supported platforms for Symantec Endpoint Protection 11.0.6 (RU6) are listed in the document System requirements for Symantec Endpoint Protection and Symantec Network Access Control 11.0.6.
Downloading the Symantec Endpoint Protection 11.0.6000.550 or 562 RU6 or RU6a Release Update
The installer package to upgrade Symantec Endpoint Protection is available from the Symantec FileConnect site: https://fileconnect.symantec.com/
The following table gives an overview of the migration process for each component of Symantec Endpoint Protection:
|Symantec Endpoint Protection Manager||When you migrate a server, the installation automatically detects and configures it appropriately.
You do not need to uninstall management servers before you install the new version. The overinstall process saves legacy settings, and then upgrades to the latest version.
|Symantec Endpoint Protection
|When you migrate a client, the overinstall automatically detects the client, and migrates and installs it appropriately. You do not need to uninstall existing clients before you install the new version.|
Overview of the migration process
Migration to the current version of Symantec Endpoint Protection includes the following steps in order:
Backing up the database
Before you upgrade, you should back up the database.
If your environment utilizes replication, you must disable replication on all sites prior to upgrading the Symantec Endpoint Protection Manager. You must not re-enable replication between sites until they are running the same version of the software.
Stopping the Symantec Endpoint Protection Manager service
Before you upgrade, you must manually stop the Symantec Endpoint Protection Manager service on every management server in your site. After you upgrade, the service is started automatically.
WARNING: You must stop the Symantec Endpoint Protection Manager service before you perform this procedure or you will corrupt your existing installation of Symantec Endpoint Protection Manager.
Upgrading the Symantec Endpoint Protection Manager
You must upgrade all Symantec Endpoint Protection Managers on which you stopped the Symantec Endpoint Protection service.
Repeat the above steps on all other Symantec Endpoint Protection Managers on which you stopped the Symantec Endpoint Protection Manager service.
Enabling replication after migration
After you migrate all servers that used replication including the servers that were configured for failover and load balancing, you must re-enable replication. After migration, you add a replication partner to enable replication. You only need to add replication partners on the computer on which you first installed the management server. Replication partners automatically appear on the other management servers.
Upgrading the Symantec Endpoint Protection clients
The easiest way to migrate Symantec Endpoint Protection clients is by using the auto-upgrade feature. All other client software deployment methods are supported, but the auto-upgrade approach is the easiest way. The client migration installation can take up to 30 minutes. It is recommended to migrate when most users are not logged on to their computers.
Note: Test this migration approach before rolling out migration to a large number of computers. Create a new group and place a small number of client computers in that group for testing purposes.
Note: Client computers that take a long time to automatically upgrade to Release Update 6 (RU6) may need to be restarted. This occurs on client computers that run Windows Vista or Windows Server 2008.
Login to Subscribe
Please login to set up your subscription.
Get support for your product, with downloads, knowledge base articles, documentation, and more.
Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments.
Set default language
Do you wish to save this as your future site?