The schema upgrade modifies your existing log files and client tables to support 14.3 features. or restart the server during this process, even if the progress bar appears to stall. Click Finish once the success screen appears. Phase 3: Upgrading the SEP Endpoints (Clients)
# On client "%ProgramFiles%\Symantec\Symantec Endpoint Protection\smc" -stop "%ProgramFiles%\Symantec\Symantec Endpoint Protection\smc" -start
Always upgrade your management servers before updating individual client endpoints. Step 1: Run the Installer symantec endpoint protection upgrade 14.2 to 14.3
Select or Remote Push to locate target endpoints.
The "Lean Client" architecture introduced in later versions of 14.2 is fully realized in 14.3. The schema upgrade modifies your existing log files
Never skip this step. If the upgrade fails, a backup is your only safety net.
Select Install Packages > Upgrade Clients with Package . Phase 3: Upgrading the SEP Endpoints (Clients) #
Perform a full backup of the SEPM database ( sem5.db ) and the recovery file ( recovery.zip ). B. Upgrade Order SEPM Servers: Always upgrade the management servers first.
After finishing your pre-upgrade preparation, follow these steps:
The 14.3 agent utilizes a more efficient, lighter footprint on endpoints, optimizing CPU and RAM usage.
Starting with SEP 14.3 RU8, installation or upgrade fails with an error about the installer integrity check, often showing "The filename, directory name, or volume label syntax is incorrect" (error 8007007B ). Cause: SEP 14.3 RU8 and later requires Microsoft Trusted Signing (formerly Azure Code Signing) support to verify its files. The necessary root certificate is missing from the client machine. Resolution: Install the "Microsoft Identity Verification Root Certificate Authority 2020" certificate into the Trusted Root Certification Authorities store on the problematic system. In some scenarios, the DigiCertAssuredIDRootCA may also be required.