Symantec Endpoint Protection 14.3 Ru6 System Requirements Direct

Here is the detailed content on the system requirements for Symantec Endpoint Protection (SEP) 14.3 RU6 (Release Update 6) , organized for IT administrators and deployment planning.

Note: SEP 14.3 RU6 is the last major release before the transition to Broadcom’s Symantec Endpoint Security Complete (SESC) . These requirements apply to on-premises management servers and client systems.

Hardware for clients

• Modern x86_64 CPU; 2+ GB RAM (depends on OS and additional software); disk space 1–5 GB for program files and quarantine—adjust per endpoint role.

SEPM (Management Server) requirements

4. Virtualization and Cloud Platform Support

SEP 14.3 RU6 runs natively on the following hypervisors and cloud instances, provided the guest OS meets above requirements. symantec endpoint protection 14.3 ru6 system requirements

| Platform | Supported Versions | Notes | |----------|--------------------|-------| | VMware ESXi | 6.7, 7.0, 8.0 | Use VMXNET3 network adapter; enable hardware virtualization | | Microsoft Hyper-V | Windows Server 2016/2019/2022, Windows 10/11 Pro/Enterprise | Dynamic memory recommended to be disabled for SEP | | Citrix Hypervisor | 8.2 LTSR, 8.2 CU1+ | – | | Nutanix AHV | AOS 5.20+ | – | | AWS EC2 | Any instance type (t3, m5, c5 families) | Use dedicated EBS-optimized volumes | | Microsoft Azure | Dv3, Ev3, or higher series | – | | Google Cloud (GCE) | N2, C2, or E2 series | – |

Virtualization-Specific Considerations:

• Do not overcommit CPU cores beyond 2:1 for high-throughput servers.
• Enable nested virtualization only if running sandboxing features (SEP’s SONAR relies on vT-x/AMD-V).

6. Review Summary – Important Caveats

| Pros | Cons / Gotchas | |-------|----------------| | Supports modern Windows Server versions | No Windows Server 2012 R2 (forces upgrade) | | Embedded DB improved, but still slow past 500 nodes | Linux client lacks full firewall (only basic) | | Smaller memory footprint than 14.2 | ARM64 Windows not supported (x86 emulation only) | | HTML5 console works on any modern browser | No official support for Windows 10 LTSC 2015/2016? (2019 LTSC OK) |

3.1 VMware ESXi / vSphere

• Supported ESXi versions: 7.0 Update 3, 8.0 Update 1+
• Recommendation: Disable memory ballooning for the SEPM VM.
• VDI optimization: Enable "VDI Mode" in SEP client policy to stagger on-access scans during login storms.

2.2 Hardware Minimums (Production Environments)

| Component | Small Environment (<250 clients) | Medium Environment (250–2,500 clients) | Large Environment (>2,500 clients) | |-----------|-----------------------------------|----------------------------------------|-------------------------------------| | CPU Cores | 4 cores @ 2.0 GHz | 8 cores @ 2.5 GHz+ | 16+ cores @ 3.0 GHz+ | | RAM | 8 GB | 16 GB | 32 GB (64 GB recommended) | | Disk Space (Program) | 10 GB | 10 GB | 15 GB | | Disk Space (Database) | 50 GB | 150 GB | 500 GB+ (depending on retention) | | Temp space during install | 5 GB | 10 GB | 20 GB | Here is the detailed content on the system

Critical Disk I/O Notes:

• Use SSD or NVMe drives for the database partition if managing more than 1,000 clients. Spinning HDDs cause severe performance degradation in policy updates and reporting.

Upgrade and migration notes

• Back up SEPM and database prior to upgrade.
• Review Symantec upgrade path and pre-upgrade checks; some older SEP client versions may require staged upgrades.
• Validate client policies and signatures after upgrade.

2. SEP Client (Managed / Unmanaged) – System Requirements

Supports Windows, Mac, Linux, and some legacy UNIX. Note: SEP 14