Risk log is not uploaded to secondary SEPM after primary SEPM was down

book

Article ID: 171386

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

You have two sites and one Symantec Endpoint Protection Manager (SEPM) on each site. A client connected SEPM-A as primary server in management server lists (MSL) and detected a risk on it. After that, SEPM-A was down without uploading risk log from that client. The client connected to another SEPM-B as secondary server. But the risk log was not uploaded to SEPM-B.

Cause

Fast Pathing function upload of critical logs was trying to send logs to only the first server in the MSL. In this scenario, the first SEPM is down so the log would never be uploaded.

Resolution

This issue is fixed in Symantec Endpoint Protection 14 RU1 MP2  For information on how to obtain the latest build of Symantec Endpoint Protection, see Download the latest version of Symantec Endpoint Protection.