About upgrading to Symantec Mail Security 6.5 for Microsoft Exchange from a previous version
| Article:TECH97484 | | | Created: 2009-01-16 | | | Updated: 2011-10-25 | | | Article URL http://www.symantec.com/docs/TECH97484 |
Problem
You want to know how to upgrade to Symantec Mail Security 6.5 for Microsoft Exchange (SMSMSE) from a previous version.
Solution
Upgrading simply involves running SMSMSE's setup.exe.
1. Download the latest version of SMSMSE from http://fileconnect.symantec.com. (You will need your current serial number to log in. ex., M1234567890)
2. This will download a self-extracing EXE file. Extract the files to a directory.
3. Run <extracted directory>\SMSMSE\Install\setup.exe.
Symantec Mail Security for Microsoft Exchange can be upgraded to Version 6.5 from the following scenarios:
| Upgrade From | Upgrade To | Supportability |
| SMSMSE 6.5 | SMSMSE 6.5 (newer version) | Supported on Exchange 2003/2007/2010 |
| SMSMSE 6.0 | SMSMSE 6.5 | Supported on Exchange 2003/2007 |
| SMSMSE 5.0 | SMSMSE 6.5 | Supported on Exchange 2003 |
| SMSMSE 4.6 | SMSMSE 6.5 | Supported on Exchange 2003 |
Note: You cannot upgrade from a previous version through silent installation or remote installation.
- Remote install on cluster is not supported but is supported in Exchange 2010 Database Availability Group (DAG) setup.
- Upgrade in cluster is not supported.
- SMSMSE does not support Veritas cluster Server Exchange 2010.
- Upgrading on Exchange Server 2003 does not require a reboot.
- It is not possible to upgrade on Exchange Server 2010 as SMSMSE 6.5 is the first release supported on this platform.
- For step-by-step installation instructions, see the version of the Implementation Guide that corresponds to your version of Microsoft Exchange. You can find the Implementation Guide in the DOCS folder of your installation media and on the Symantec Web site.
Backup Settings
It is recommended that you back up the existing configuration files prior to upgrading. The backup files are for use in the case of a failed migration to ensure that you can easily roll back to the previous version.
Read Backing up configuration settings for Symantec Mail Security 5.x or 6.x for Microsoft Exchange for details about backing up SMSMSE 5.x configuration files.
Settings exported from SMSMSE 6.0 can be imported into SMSMSE 6.5 in the following condition:
-From SMSMSE 6.0 on Exchange 2003 to SMSMSE 6.5 on Exchange 2003
-From SMSMSE 6.0 on Exchange 2007 to SMSMSE 6.5 on Exchange 2007
-Settings exported from SMSMSE 5.0 cannot be imported into SMSMSE 6.0 onwards
It is not possible to import SMSMSE settings from version 6.0 running on Exchange Server 2003 into SMSMSE 6.5 running on Exchange 2010. On Exchange 2010, a clean installation of SMSMSE 6.5 is required.
The following table lists the settings that do not migrate from version 5.x to the new version.
Version 5.x migration settings
| Setting | Description |
| Heuristic antispam | This feature is no longer supported. Enable and configure Symantec Premium AntiSpam for spam detection. |
| Save to folder option | The "Save to folder" option is no longer supported. If "Save to folder" was a disposition for a content filtering rule, the disposition is set to "Log Only." The "Add X-header" settings associated with the "Save to folder" disposition has been removed. In the Symantec Premium AntiSpam settings, the "Save to folder" settings and the "Add X-header" settings associated with them have been removed. The "Add X-header" settings that are not associated with the "Save to folder" settings migrate as is. |
| Report templates and the report database | These items do not migrate. |
| SESA Alerts | This feature is no longer supported. |
| Background scanning | These settings do not migrate. Re-enable and schedule background scanning. |
| Veritas Cluster Server configurations | Mail Security does not support upgrades from 5.0 on Veritas Cluster Server configurations. |
If you are upgrading from 4.6.x, the policy settings are incorporated into the applicable policy on the new installation. Mail Security version 5.x and higher do not contain a separate multiserver console. Single and multiple servers are administered from the same console. Multiserver console settings do not migrate to the new version. You must add any existing servers to be upgraded to an asset group (for example, Global). You can use the Install/Upgrade servers feature to upgrade the selected server. Custom policies, heuristic antispam settings, content filtering rules, and report templates do not migrate to the new version.
The following table lists the migrations from version 4.6.x to the new version.
Version 4.6.x migration settings
| Setting | Description |
| Auto-protect | Migrates to the new version as the standard policy. |
| Heuristic antispam | This feature is no longer supported. Enable and configure Symantec Premium AntiSpam for spam detection. |
| Macro Virus Rule | These settings are no longer supported. |
| Bloodhound Virus Rule | These settings are no longer supported. |
| Mass-Mailer Virus Rule | These settings do not migrate. |
| HeartBeat | This feature is no longer supported. |
| Filtering subpolicy | These settings do not migrate. |
| Messenger Service Alerts | This feature is no longer supported. |
| AMS Alerts | This feature is no longer supported. |
| SESA Alerts | This feature is no longer supported. |
| Scheduled scans | These settings do not migrate. |
| Manual scans | These settings do not migrate. |
| Attachment Blocking rule | This rule is migrated to a new rule — File Name Rule. |
| Outbreak settings | These settings do not migrate. |
| Content Dictionary | This feature is no longer supported. |
| Generated reports | Reports cannot be viewed through the console. Reports that you generated in version 4.6.x are copied to the following directory: You can view a report by opening it from this directory. |
| Report templates and the report database | These features and documents do not migrate. |
| Background scanning | These settings do not migrate. Re-enable and schedule background scanning. |
|
|
Related Articles
Legacy ID
2009111710371954
Article URL http://www.symantec.com/docs/TECH97484
Terms of use for this information are found in Legal Notices
Thank you.