Issue with ATP's mapping between SEP client and SEPM database

book

Article ID: 169469

calendar_today

Updated On:

Products

Advanced Threat Protection Platform

Issue/Introduction

ATP failed to process multiple rows of the same SEP client in the SEPM database to determine correct SEP client /  SEPM mapping.

Cause

A query told ATP about SEP client / SEPM mapping so that ATP could issue commands to the right SEPM. If the result set that was returned from this query had two rows, ATP failed to distinguish the current data from the older data.  This resulted in the SEP client being assigned to the wrong SEPM in the database. 

Environment

Multi-site environments.

Resolution

ATP has resolved this issue as of build 3.0.758.