: Back up the Server Private Key and recovery files located under the %Symantec\Symantec Endpoint Protection Manager\Server Private Key Backup path.
If the DB upgrade fails, restore from the backup created earlier and review the upgrade.log .
Why move from 14.2 to 14.3? ✅ Improved heuristic detection for fileless and zero-day attacks. ✅ Performance Boost: Optimized scan engines mean less CPU impact on your endpoints. ✅ Product Lifecycle: Ensure you stay supported and secure against the latest threat landscape.
Ensure your servers and client machines meet the hardware and software requirements for 14.3.
This is the easiest method, allowing you to configure the upgrade through the SEPM console. In the SEPM console, go to . symantec endpoint protection upgrade 14.2 to 14.3
If your network will operate in a pure IPv6 environment, ensure that all clients are upgraded to at least version 14.2 (or later) migrating the network. Earlier versions do not support IPv6 communication, and performing the network migration first can cause the upgrade to fail or result in communication loss.
: Integration with Windows AMSI allows for deeper scanning of script-based threats.
If you are still running Symantec Endpoint Protection (SEP) 14.2, it is highly recommended to upgrade to 14.3 to take advantage of critical security patches and performance improvements. Here is a quick overview of the process and some "gotchas" to watch out for.
Complete Upgrade Guide: Symantec Endpoint Protection 14.2 to 14.3 : Back up the Server Private Key and
Navigate to the tab and select the target group you wish to upgrade. Click the Install Packages tab in the main window view. Under Tasks, click Add Client Install Package .
: 14.3 RU9 and earlier support Windows Server 2012/2012 R2, while later versions require Windows Server 2016, 2019, 2022, or 2025. Database Health Back up your SEPM database, logs, and recovery files. If using a local SQL Server database, ensure at least of available disk space (200 GB recommended). Stop Replication
Open services.msc and verify that , SEPM API Server , and Symantec Embedded Database (if applicable) are running.
Upgrading from to 14.3 involves a specific sequence: upgrading the management server (SEPM) first, followed by the client agents. Pre-Upgrade Checklist ✅ Improved heuristic detection for fileless and zero-day
Upgrade SEPM upgrading clients.
By following these steps and best practices, you can ensure a successful upgrade from SEP 14.2 to 14.3 and take advantage of the latest security features and enhancements.
Improved detection capabilities against ransomware and fileless attacks.