Rule description
This rule updates AD user attributes according to values defined in the CSV file. When the rule executes, it compares the current value for a found user with the value from the CSV file and updates the user only if these values are different.
Output report contains detailed information about which users have been updated by the rule.
When to use this rule
Use this rule when you need to update AD user properties that depend on some other AD property. For example, set the various address attribute values based on the office name attribute value.
This rule queries the Active Directory attribute defined by the name of the "key" column, for example, office name (physicalDeliveryOfficeName). When a user object attribute "key" attribute matches the value of the specified "key" column, the subsequent columns in the text file are used to update attributes that are defined by the remaining column names, for example, street address, postal code, state, and others.
Example CSV File:
physicalDeliveryOfficeName;streetAddress;l;st;postalcode
Atlanta;100Atlantic Blvd, Suite90;Atlanta;GA;30301
Video Tutorial
Rule Settings
Query Section
| Setting name | Description |
|---|---|
|
Select Data Source |
This setting specifies the text file for import. The […] button allows the user to browse for the file and the Create button allows creating or editing of the file in the Cayosoft Administrator data source editor. |
|
The separator used in file |
Use this setting to select the separator used in the file.
|
|
More options |
|
|
Filter CSV data |
This setting specifies the filter that can remove data rows from the imported text file that satisfies the specific condition. |
|
Column name > Attribute Mapping (optional) |
Use this setting to map column names from the file to the AD user attributes. When file column names do not match Active Directory Attribute names, map them here using a separated string. Map column to AD Attribute by specifying each in the format ColumnName>ADAttributeName. Indicate the key search column with an '*'. You can add columns that already match without formatting. Example: *username>SamAccountName, *Office>physicalDeliveryOfficeName,description |
|
Empty field in Data Source |
If the record in the CSV file column is empty, you can skip updating the attribute or clear its value. |
Action Section
| Setting name | Description |
|---|---|
|
Limit scope to this Domain or OU |
This setting defines the search query scope. To improve query performance, limit the scope to specific OU. Important: To test rule configuration, limit the rule scope to an OU that contains test accounts or objects.
|
| More Options | |
|
Server |
Select the domain controller to run the rule. |
|
Credentials |
Specify credentials to the selected domain controller. |
|
LDAP Filter Filter |
Set the filtering conditions to only return objects or data that need to be processed by the rule. It is possible to use only one of these filters: either the LDAP filter or the filter, where you can select properties and operators from the list. |
Output Section
This section defines the output format of this rule.
To get more information about this section, please see the Output section article.
Enforce/Schedule section
This section defines the schedule for how often to run the rule.
To get more information about this section, please see the Enforce/Schedule section article.
Change History
| Version | Notes |
|---|---|
| 7.3.1 | Filter CSV data setting is added. |
| 6.4.0 | Empty field in Data Source setting is added. |
| 5.4.0 | The rule is supplied with the pre-built CSV file template, which is selected by default when you create a new rule. |
Comments
0 comments
Please sign in to leave a comment.