AD Users with Suggested Update to UserPrincipalName (UPN) Suffix rule
This rule queries the specified Active Directory scope and for each returned user suggests updates for UserPrincipalNames that will allow you to replace all instances of one UserPrincipalNames suffix with another suffix.
NOTE: To replace the original value of UserPrincipalName suffix with a new value, use the AD Users | Find & Replace UserPrincipalName (UPN) Suffix rule rule.
When to use this rule
Use this rule to get the report with suggested updates when you are going to replace the UserPrincipalName suffixes for Active Directory users while maintaining unique names.
Rule Settings
| Setting name | Description |
|---|---|
| Query Section | |
| 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. |
| Original UPN Suffix (abc.com) | Specify the current value of the UserPrincipalName suffix that you want to replace with another value. |
| New UPN Suffix (xyz.com) | Specify the new value for the UserPrincipalName suffix. |
| Other Query Settings | |
| Properties to display |
Each object property defined in this setting matches the column that will be displayed in the Web Portal for this web query. To display additional columns, add the required properties to the Properties to display list. To add extension attribute 1 that is synchronized from AD, you need to use a value like:
Copy
|
| System properties | List of properties required for this rule to be executed correctly. |
| Filter query results |
Set the filtering conditions to hide unwanted data based on criteria not supported in the Query criteria setting. Example: filter by the found object Distinguished Name. TIP: For optimal performance, use the Query criteria setting above to filter objects whenever possible. |
| Sort by | Sort result object list. |
| Initialization Script | |
| Initialization 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.
|
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 section
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.