The following settings are imported:
- Antivirus scanning exclusions, which appear in the Exceptions policy.
- Antivirus policies
The following settings are not imported:
- Tamper Protection
- Scheduled scans
- Quarantine purge or custom Quarantine Directory settings
- Custom communications settings, since the mode of communication has changed with the architecture
- Any other setting that is Symantec System Center-specific
- Firewall policies (Symantec System Center only)
- Any settings changed directly on the client
Reasons for using the Migration Wizard from Symantec AntiVirus to Symantec Endpoint Protection:
- You have an organizational hierarchy and infrastructure established that you prefer to continue to use, including policy inheritance and client group structure.
- You have specific or highly specialized settings you wish to bring over.
- In the enterprise version, migrating the client group structure may make client migration easier for larger, more complex client group structures. The process of migration assigns existing clients to their respective groups, to which they will check in once Symantec Endpoint Protection is deployed. You do not need to individually create and deploy a group-specific installation package for each group. You only need to ensure that you unlock server groups before you begin. To deploy the client, you first export the installation package. However, when you export the package, you must uncheck group-specific options, including unchecking Add clients automatically to the selected group. You then deploy through the Client Deployment Wizard using an Existing Package Deployment.
See: Exporting client Installation packages
Reasons for not using the Migration Wizard from Symantec AntiVirus to Symantec Endpoint Protection:
- Your current organizational hierarchy and/or infrastructure within the Symantec System Center no longer meet your needs. You would prefer to start fresh and redesign the structure.
- If your current organizational hierarchy is based on the Symantec AntiVirus architecture of AV servers and AV clients, you may wish to design a new one based on other criteria, such as company department, administrative responsibility, or physical location or subnet. Symantec Endpoint Protection's architecture is radically different than Symantec AntiVirus'; in Symantec Endpoint Protection, there is a management console, and all computers are considered clients. All computers include servers and workstations, even the computer to which the Symantec Endpoint Protection Manager is installed.
- If you did not make significant changes to the default Symantec AntiVirus/Symantec System Center installation, there is no reason to prepare for or implement a migration of settings from Symantec AntiVirus.
- If you have a complex organizational structure and you are migrating to the Small Business Edition, you would have to create and deploy individual packages for each group in order to retain that client organization. This may mean a large administrative overhead.
If you choose not to import your settings from the Symantec System Center, you can install Symantec Endpoint Protection as if you are doing so for the first time.
However you decide to proceed, we recommend that you defer the migration of your primary and secondary Symantec AntiVirus servers until you migrate all Symantec AntiVirus clients to Symantec Endpoint Protection. The Symantec AntiVirus servers will continue to provide antivirus content to the Symantec AntiVirus clients until you migrate them.
Symantec AntiVirus 10.x or Symantec Client Security 3.x, migrating to Symantec Endpoint Protection