search cancel

Adding object attributes to Active Directory imports


Article ID: 171190


Updated On:


Information Centric Analytics Data Loss Prevention Core Package


When using Information Centric Analytics (ICA), it is sometimes necessary to bring in additional attributes from Active Directory. 


To add more object attributes to bring into the ActiveDirectoryDW database from Active Directory aside from the out-of-the-box attributes, navigate to the Active Directory Import Utility installation directory.  Open the file named ADConnectorConfig.xml in notepad (or any text editor).  Inside the tags <ComputerProperties>, <UserProperties>, <GroupProperties> and/or <OUProperties>, insert the object attributes to add.  For example, if the attribute being added is the user attribute, wWWHomePage, go to the <UserProperties> section in the config file and add the attribute name to the end of the list:




After adding the attribute to the correct section of the config file, save and close the config file.  In SQL Management Studio, add the appropriate column/s in the correct table where the attribute as added.  In our example above, a user attribute was added, so the column for the new attribute needs to be added into the User table in the ActiveDirectoryDW database.  To do this, execute the command below in SQL Management Studio:

ALTER TABLE table_name

ADD column_name datatype;


Specific to our example, the command is:


ADD [wWWHomePage] NVARCHAR(max);


Make sure that the data type designated for the new column matches the data type expected from the new attribute.  Also, note that the Active Directory Import Utility is only able to import single-valued attributes.  For a list of Active Directory attributes and additional attributes information, go to:


CAUTION: These commands assume a basic understanding of SQL. Any changes to the Database pose the potential to affect the operation of the product. ALWAYS ENSURE YOU HAVE A BACKUP OF YOUR DATABASE BEFORE MAKING CHANGES.

In order for Symantec to provide full support of the schema and the DB environment, you have to be running Oracle in the version specific to the used version as outlined in the System Requirements Guide. Please see the limitations section at