Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Active Roles On Demand Hosted - Administration Guide

Introduction About Active Roles Getting Started Rule-based Administrative Views Role-based Administration
Access Templates as administrative roles Access Template management tasks Examples of use Deployment considerations Windows claims-based Access Rules
Rule-based AutoProvisioning and Deprovisioning
About Policy Objects Policy Object management tasks Policy configuration tasks
Property Generation and Validation User Logon Name Generation Group Membership AutoProvisioning E-mail Alias Generation Exchange Mailbox AutoProvisioning AutoProvisioning for SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Office 365 and Azure Tenant Selection User Account Deprovisioning Office 365 Licenses Retention Group Membership Removal Exchange Mailbox Deprovisioning Home Folder Deprovisioning User Account Relocation User Account Permanent Deletion Group Object Deprovisioning Group Object Relocation Group Object Permanent Deletion Notification Distribution Report Distribution
Deployment considerations Checking for policy compliance Deprovisioning users or groups Restoring deprovisioned users or groups Container Deletion Prevention policy Picture management rules Policy extensions
Understanding workflow Workflow activities overview Configuring a workflow
Creating a workflow definition Configuring workflow start conditions Configuring workflow parameters Adding activities to a workflow Configuring an Approval activity Configuring a Notification activity Configuring a Script activity Configuring an If-Else activity Configuring a Stop/Break activity Configuring an Add Report Section activity Configuring a Search activity Configuring CRUD activities Configuring a Save Object Properties activity Configuring a Modify Requested Changes activity Enabling or disabling an activity Enabling or disabling a workflow Using the initialization script
Example: Approval workflow E-mail based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic Groups Active Roles Reporting Management History
Understanding Management History Management History configuration Viewing change history
Workflow activity report sections Policy report items Active Roles internal policy report items
Examining user activity
Entitlement Profile Recycle Bin AD LDS Data Management One Identity Starling Management One Identity Starling Two-factor Authentication for Active Roles Managing One Identity Starling Connect Azure AD, Office 365, and Exchange Online management
Configuring Active Roles to manage hybrid AD objects Managing Hybrid AD Users Unified provisioning policy for Azure O365 Tenant Selection, Office 365 License Selection, and Office 365 Roles Selection, and OneDrive provisioning Office 365 roles management for hybrid environment users Managing Office 365 Contacts Managing Hybrid AD Groups Managing Office 365 Groups Managing Azure Security Groups Managing cloud-only Azure users Managing cloud-only Azure guest users Managing cloud-only Azure contacts Changes to Active Roles policies for cloud-only Azure objects Managing room mailboxes
Managing Configuration of Active Roles
Connecting to the Administration Service Adding and removing managed domains Using unmanaged domains Evaluating product usage Creating and using virtual attributes Examining client sessions Monitoring performance Customizing the console Using Configuration Center Changing the Active Roles Admin account Enabling or disabling diagnostic logs Active Roles Log Viewer
SQL Server Replication Appendix A: Using regular expressions Appendix B: Administrative Template Appendix C: Communication ports Appendix D: Active Roles and supported Azure environments Appendix E: Enabling Federated Authentication Appendix F: Active Roles integration with other One Identity and Quest products Appendix G: Active Roles integration with Duo Appendix H: Active Roles integration with Okta


This error may be due to one of the following reasons:

  • Incorrect server name. The computer running SQL Server is renamed, or SQL Server has lost its name.
  • Administration Service identifies SQL Server by alias. An alias was used to specify SQL Server when installing the Administration Service.
Incorrect server name

To isolate and resolve this problem, run the following two queries on the SQL Server instance affected by this issue. Copy these queries “as is,” without making any substitutions for the servername parameter:

select @@servername

select serverproperty('servername')

If select @@servername returns a non-null value that is different from the value returned by the second query, execute the following SQL script:

exec sp_dropserver 'oldname', 'droplogins'

exec sp_addserver 'newname', 'local'

In this script, replace:

  • oldname with the value returned by select @@servername
  • newname with the value returned by select serverproperty('servername')

If select @@servername returns NULL, execute the following SQL script:

exec sp_addserver 'newname', 'local'

In this script, replace newname with the value returned by select serverproperty('servername').

For these changes to take effect, you must restart SQL Server. You can restart SQL Server by using SQL Server Configuration Manager:

  1. In the console tree, select SQL Server Services.
  2. In the details pane, right-click the SQL Server instance to restart, and then click Restart.
Administration Service identifies SQL Server by alias

The Administration Service must be configured to identify SQL Server by computer name, rather than using a client alias. Otherwise, when attempting to make SQL Server the Publisher or a Subscriber, you encounter the error “An alias cannot be used for replication. Use the name of the SQL Server instance.”

To avoid this problem, you may need to reinstall the Administration Service. When installing the Administration Service, use the following syntax to identify SQL Server:

  • computername — for the default instance
  • computername\instancename — for a named instance

In this syntax:

  • computername is the (short) NetBIOS name of the computer running SQL Server;
  • instancename is the name of a SQL Server named instance.



Appendix A: Using regular expressions

When configuring search filter conditions or property validation criteria, you may need to use regular expressions. This section helps you learn about the syntax you must use in regular expressions.

A regular expression is a pattern of text that consists of ordinary characters (for example, letters a to z) and special characters, known as metacharacters. It serves as a template for matching a character pattern to the string value being validated.

The following table contains a list of metacharacters and their behavior in the context of regular expressions that can be used to create search filter conditions and property validation criteria in Active Roles. To match an exact metacharacter, precede the character with a backslash (\).

Table 113: Metacharacters in the context of regular expressions




Marks the next character as a special character, a literal, or an octal escape. For example, n matches the character n; \n matches a new line character. The sequence \\ matches \ and \( matches (.


Matches the position at the beginning of the input string.


Matches the position at the end of the input string.


Matches the preceding sub-expression zero or more times. For example, zo* matches z and zoo. * is equivalent to {0,}.


Matches the preceding sub-expression one or more times. For example, zo+ matches zo and zoo, but not z. + is equivalent to {1,}.


Matches the preceding sub-expression zero or one time. For example, do(es)? matches the do in do and does. ? is equivalent to {0,1}.


n is a nonnegative integer. Matches the preceding sub-expression exactly n times. For example, o{2} does not match the o in Bob, but matches the two o’s in food.


n is a nonnegative integer. Matches the preceding sub-expression at least n times. For example, o{2,} does not match the o in Bob, but matches all the o’s in foooood. o{1,} is equivalent to o+. o{0,} is equivalent to o*.


m and n are nonnegative integers, where n <= m. Matches the preceding sub-expression at least n and at most m times. For example, o{1,3} matches the first three o’s in fooooood. o{0,1} is equivalent to o?. Note that there cannot be spaces between the comma and the numbers.


When this character immediately follows any of the other quantifiers (*, +, ?, {n}, {n,}, {n,m}), the matching pattern is non-greedy. A non-greedy pattern matches as little of the searched string as possible, whereas the default greedy pattern matches as much of the searched string as possible. For example, in the string oooo, o+? matches a single o, while o+ matches all o’s.


Matches any single character except \n. To match any character including the \n, use a pattern such as [.\n].

( )

Groups one or more regular expressions to establish a logical regular expression consisting of sub-expressions. Used to override the standard precedence of certain operators. To match parentheses characters ( ), use \( or \).


Matches either x or y. For example, z|food matches z or food. (z|f)ood matches zood or food.


A character set. Matches any one of the enclosed characters. For example, [abc] matches the a in plain.


A negative character set. Matches any character not enclosed. For example, [^abc] matches the p in plain.


A range of characters. Matches any character in the specified range. For example, [a-z] matches any lowercase alphabetical character in the range a to z.


A negative range of characters. Matches any character not in the specified range. For example, [^a-z] matches any character not in the range a to z.


Matches a word boundary, that is, the position between a word and a space. For example, er\b matches the er in never but not the er in verb.


Matches a non-word boundary. For example, er\B matches the er in verb but not the er in never.


Matches the control character indicated by x. For example, \cM matches a Control-M or carriage return character. The value of x must be in the range of A-Z or a-z. If not, c is assumed to be a literal c character.


Matches a digit character. Equivalent to [0-9].


Matches a non-digit character. Equivalent to [^0-9].


Matches any white space character including space, tab, form-feed, etc. Equivalent to [ \f\n\r\t\v].


Matches any non-white space character. Equivalent to [^ \f\n\r\t\v].


Matches any word character including underscore. Equivalent to [A-Za-z0-9_].


Matches any non-word character. Equivalent to [^A-Za-z0-9_].


Matches n, where n is a hexadecimal escape value. Hexadecimal escape values must be exactly two digits long. For example, \x41 matches A. Allows ASCII codes to be used in regular expressions.

Examples of regular expressions

The following table includes some examples of regular expressions and matches.


Table 114: Examples of regular expressions



Does not match


Austin and Boston



Austin and Boston




Boston or Austin



South Boston or North Boston Harbor


Boston and Galveston



Seattle and Seaside and Oceanside

Seoul or Sidney



Dallas or Lockhart


Etoile and Wylie



Etoile and Wylie and Beeville



Etoile and Beeville



Addison and Caddo



Highland Village and Lake Dallas


Order of precedence

Once you have constructed a regular expression, it is evaluated much like an arithmetic expression. It is evaluated from left to right and follows an order of precedence.

The following table shows the order of precedence for the various regular expression operators, starting with the highest:

Table 115: Order of precedence





(), []

Parentheses and Brackets

*, +, ?, {n}, {n,}, {n,m}


^, $, \anymetacharacter

Anchors and Sequences



Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation