Veritas Data Insight Administrator's Guide
- Section I. Getting started
- Introduction to Veritas Data Insight administration
- Configuring Data Insight global settings
- Overview of Data Insight licensing
- About scanning and event monitoring
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Data Insight integration with Symantec Data Loss Prevention (DLP)
- Configuring advanced analytics
- About open shares
- About bulk assignment of custodians
- Section II. Configuring Data Insight
- Configuring Data Insight product users
- Configuring Data Insight product servers
- About node templates
- About automated alerts for patches and upgrades
- Configuring saved credentials
- Configuring directory service domains
- Configuring containers
- Section III. Configuring native file systems in Data Insight
- Configuring NetApp file server monitoring
- Configuring clustered NetApp file server monitoring
- About configuring secure communication between Data Insight and cluster-mode NetApp devices
- Configuring EMC Celerra or VNX monitoring
- Configuring EMC Isilon monitoring
- Configuring EMC Unity VSA file servers
- Configuring Hitachi NAS file server monitoring
- Configuring Windows File Server monitoring
- Configuring Veritas File System (VxFS) file server monitoring
- Configuring monitoring of a generic device
- Managing file servers
- Adding filers
- Adding shares
- Renaming storage devices
- Configuring NetApp file server monitoring
- Section IV. Configuring SharePoint data sources
- Configuring monitoring of SharePoint web applications
- About the Data Insight web service for SharePoint
- Adding web applications
- Adding site collections
- Configuring monitoring of SharePoint Online accounts
- About SharePoint Online account monitoring
- Adding SharePoint Online accounts
- Adding site collections to SharePoint Online accounts
- Configuring monitoring of SharePoint web applications
- Section V. Configuring cloud data sources
- Section VI. Configuring ECM data sources
- Section VII. Health and monitoring
- Section VIII. Alerts and policies
- Section IX. Remediation
- Section X. Reference
- Appendix A. Backing up and restoring data
- Appendix B. Data Insight health checks
- Appendix C. Command File Reference
- Appendix D. Data Insight jobs
- Appendix E. Troubleshooting
- Troubleshooting FPolicy issues on NetApp devices
Importing additional attributes for users and user groups
Data Insight periodically scans directory domains and fetches basic information about users, groups, and their relationships. You can also import the additional attributes for users and user groups from other user management systems into Data Insight users database. This attribute information is later included in the report outputs and also sent to Symantec Data Loss Prevention as a part of ownership information.
To import additional attributes
- Create and save a
.csv
file,customattr.csv
in theusers
folder in the Data Insight data directory on the Management Server. By default, theusers
directory on the Management Server is located atC:\DataInsight\data\users
.Note:
When you save a
.csv
file with multibyte characters, you must select UTF-8 encoding instead of unicode or default encoding.The .csv file must contain the following information:
Whether the entity is a user or group.
The name of the user or group in the format, logon_name@domain name.
The type of custom attribute, for example, Email or DN. Four types of custom attributes are defined, Integer, String, DNString, and Email.
The name of the custom attribute.
The value of the custom attribute. In case a custom attribute has multiple values, list each value separated by commas.
<user/group>,<logon_name@domain>,<value_type>,<attribute_name>,<value1> <value2>,...<value_n>.
For example, user, John_Doe@mycompany.com, integer, age, 26
- The information that is contained in the
.csv
file is imported into the users database when the next Active Directory scan runs. To do so immediately, run the following command:adcli.exe - - mode importcustomattr - - csvfile <location of csv file>
Note:
To troubleshoot issues related to import of such attributes, check the log file, adcli.log
in the log
folder on the Management Server