Symantec — Endpoint Protection Upgrade 14.2 To 14.3

Even with perfect planning, issues arise. Here are solutions to the most frequent problems during the 14.2 to 14.3 transition.

| 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 | Do not upgrade – keep 14.2 client or retire the OS. |

If critical clients fail to upgrade or the SEPM becomes unstable: symantec endpoint protection upgrade 14.2 to 14.3

Downgrade is not supported – you cannot simply overwrite 14.3 with 14.2. Always test in a non-production environment first.

# On client
"%ProgramFiles%\Symantec\Symantec Endpoint Protection\smc" -stop
"%ProgramFiles%\Symantec\Symantec Endpoint Protection\smc" -start

| Activity | Duration | |----------|----------| | Pre-upgrade backup & health check | 2–4 hours | | SEPM upgrade | 30–60 minutes | | Client upgrade (phased) | 3–10 days (depending on scale) | | Post-validation & testing | 1–2 days | | Total project | 1–2 weeks | Even with perfect planning, issues arise

Option A – Push upgrade via SEPM (recommended for scale)

Option B – Manual / scripted

Option C – GPO / WSUS (for unmanaged clients)

Export the 14.3 Windows client MSI from the SEPM: Admin > Install Packages > Export Client Install Package If critical clients fail to upgrade or the

Deploy via your software distribution tool.