AD Users | Rename rule
Rule description
This rule queries the specified Active Directory scope and renames each returned user according to the specified settings.
Rule settings
Query 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 a specific OU. IMPORTANT: To test the rule configuration, limit the rule scope to an OU that contains test accounts or objects and use the Preview feature. |
| Query criteria* |
Query criteria are sent with the query and may improve query performance. TIP: For additional information on the criteria builder, see the How to use Query Builder dialog for Query Criteria and Filter rule settings. |
| Maximum number of users* | Specify the maximum number of users to modify in the selected scope. |
| More options | |
| Filter | Filter the returned query to show matching data only. The setting features filters not supported by the Query criteria setting. |
| Properties to display | Define the object properties to display in the output file. |
| Sort by | Define a property to sort the resulting list of objects. |
| Initialization script | |
| Script |
Usually, rules use query criteria to limit the query search scope. It improves the performance of the executed rule. Due to the PowerShell limitations, it is not possible to use calculated expressions in query criteria. That is the point where the initialization script can help. You can initialize a global variable in this setting and then use it in query criteria. IMPORTANT: To use a variable, declared in the initialization script, in the query scope, it must be global: Example: Update AD users, created in the last ten days.
|
Action section
| Setting name | Description |
|---|---|
| Attribute generation rules |
Cayosoft Administrator can automatically generate object attributes. Select a generation rule from the list or create your own generation rule to satisfy the requirements and policies of your organization. Refer to the following video guide to learn more about the expression builder: Expression Builder for Generating UserNames. |
| Validate display name uniqueness | Enable the uniqueness check of the |
| More options | |
| Name conflict resolution |
Define the conflict resolution logic to automatically resolve name conflicts and ensure the name attributes are unique:
|
| Update targetAddress prefix for user with remote mailbox | Define the update behavior for the |
Remove previous targetAddress value |
Set the option to Yes to remove the previous targetAddress value from the proxyAddresses attribute. |
| Set mail attribute to new Primary SMTP | Define the update behavior for the |
| Previous email address |
Define the action for the previous email address:
|
| Alternative name generation rules | |
| Alternative attribute generation rules |
Cayosoft Administrator can automatically resolve name conflicts and ensure the name attributes are unique. Select an alternative generation rule from the list or create your own generation rule to satisfy the requirements and policies of your organization in case of an attribute generation conflict. Refer to the following video guide to learn more about the expression builder: Expression Builder for Generating UserNames. |
| Counter format |
Define the counter format to suffix conflicting users with a numeric value and generate unique names across the organizations. TIP: To use two-digit numbers, specify 00. To start from a specific number (e.g., 5), specify 5. |
| Virtual and other attributes | |
| Virtual attributes | Using the Attribute mapping dialog, map a data source attribute to the target attribute. |
| Attribute mapping script |
Set up attribute mapping using scripts. Refer to the following example:
|
Output section
This section defines the output format of this rule.
To get more information about this section, please see the Rule Output section article.
Enforce/Schedule
This section defines the schedule for how often to run the rule.
To get more information about this section, please see the Rule Enforce/Schedule section article.
Comments
0 comments
Please sign in to leave a comment.