ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Migrating legacy Data Owner Exception configurations


Article ID: 160697


Updated On:


Data Loss Prevention Enforce


In Data Loss Prevention releases prior to version 11, the Data Owner Exception feature of EDM was implemented using configuration files. Starting with version 11, the Data Owner Exception feature is moved to the Enforce Server administration console.

If you implemented Data Owner Exception using configuration files, you need to migrate these exceptions to the Enforce Server administration console. In addition, you need to remove any previous Data Owner Exception configuration files from the system.


To migrate legacy Data Owner Exceptions configurations, complete the following steps:
  1. Remove or comment out any legacy Data Owner Exception entries found in the following configuration file: \SymantecDLP\protect\config\
  2. Use the Enforce Server administration console to map the Data Owner Exception fields when you create the Exact Data Profile.
  3. Configure each Data Owner Exception in one or more policies.

Refer to the Symantec Data Loss Prevention Administration Guide for instructions on creating the EDM profile and configuring EDM policies.