Issue with ATP's mapping between SEP client and SEPM database
Last Updated November 06, 2017
ATP failed to process multiple rows of the same SEP client in the SEPM database to determine correct SEP client / SEPM mapping.
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.
ATP has resolved this issue as of build 3.0.758.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe