If you have multiple management servers, disable replication before starting the upgrade. 2. Upgrade the Symantec Endpoint Protection Manager (SEPM)
Once the SEPM is upgraded, you can push the new client software to your endpoints using several methods:
This article provides a step-by-step guide and best practices for upgrading to SEP 14.3, ensuring a smooth transition for your network endpoints. Why Upgrade to SEP 14.3? symantec endpoint protection upgrade 14.2 to 14.3
or equivalent 64-bit dual-core processor (quad-core recommended).
SEP 14.2 (any RU) → SEP 14.3 (latest RU) If you have multiple management servers, disable replication
| Issue | Likelihood | Mitigation | |-------|------------|-------------| | Database upgrade fails (SQL compatibility) | Medium | Ensure SQL is at least 2016, run DBCC CHECKDB pre-upgrade. | | Client communication breaks after SEPM upgrade | Low | Restart Symantec Management Service; check firewall port 8014. | | Custom policies lost or reset | Low | Export all policies before upgrade as XML backup. | | High memory usage post-upgrade (Java console) | Medium | Increase SEPM heap size (set SEPM_JVM_MAX_MEMORY ). | | 14.3 client fails on Windows 7 / old OS | High | – keep 14.2 client or retire the OS. |
Before upgrading to SEP 14.3, ensure that your environment meets the following requirements: Why Upgrade to SEP 14
The upgrade requires a server restart and client reboots. Schedule this during a maintenance window.
Stronger ransomware protection and improved behavioral analysis. 2. Pre-Upgrade Checklist & Best Practices