ActiveRoles_EvaluationGuide
ActiveRoles_EvaluationGuide
Evaluation Guide
Copyright 2023 One Identity LLC.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this
guide is furnished under a software license or nondisclosure agreement. This software may be used
or copied only in accordance with the terms of the applicable agreement. No part of this guide may
be reproduced or transmitted in any form or by any means, electronic or mechanical, including
photocopying and recording for any purpose other than the purchaser’s personal use without the
written permission of One Identity LLC .
The information in this document is provided in connection with One Identity products. No license,
express or implied, by estoppel or otherwise, to any intellectual property right is granted by this
document or in connection with the sale of One Identity LLC products. EXCEPT AS SET FORTH IN THE
TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT,
ONE IDENTITY ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR
STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-
INFRINGEMENT. IN NO EVENT SHALL ONE IDENTITY BE LIABLE FOR ANY DIRECT, INDIRECT,
CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT
LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF
INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF
ONE IDENTITY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. One Identity makes
no representations or warranties with respect to the accuracy or completeness of the contents of this
document and reserves the right to make changes to specifications and product descriptions at any
time without notice. One Identity does not make any commitment to update the information
contained in this document.
If you have any questions regarding your potential use of this material, contact:
One Identity LLC.
Attn: LEGAL Dept
4 Polaris Way
Aliso Viejo, CA 92656
Refer to our Web site (http://www.OneIdentity.com) for regional and international office
information.
Patents
One Identity is proud of our advanced technology. Patents and pending patents may apply to this
product. For the most current information about applicable patents for this product, please visit our
website at http://www.OneIdentity.com/legal/patents.aspx.
Trademarks
One Identity and the One Identity logo are trademarks and registered trademarks of One Identity
LLC. in the U.S.A. and other countries. For a complete list of One Identity trademarks, please visit
our website at www.OneIdentity.com/legal. All other trademarks are the property of their
respective owners.
Legend
Introduction 6
Delegating administration 18
Assign the Help Desk role for an OU 18
Test the delegated administrator’s rights 19
About us 67
Contacting us 67
Technical support resources 67
Introduction
NOTE:
l Unless otherwise indicated, the instructions in this document assume that you are
logged on as Active Roles Admin. The Active Roles Admin account is specified when
installing the Administration Service, and defaults to the Administrators local group
of the computer running the Administration Service.
l You should verify that the Active Roles console is in Advanced view mode: On the
View menu, click Mode; then, click Advanced Mode.
Successful deployment requires thorough testing in a lab environment. When planning your
testing, we recommend:
l Designing your lab to reflect your production environment. For example, if your
network has multiple sites, then your lab should have multiple sites.
l Having your lab’s number of users and computers be at least two to five percent of
the number of users and computers in your production environment.
This section describes how to initially set up your test lab for evaluation purposes: install
Active Roles on your computer, connect to the Active Roles Administration Service and
register domains with Active Roles.
Install the Windows Server operating system on your server, and join the server to your
test Active Directory domain.
Then, install the following software on your server:
Once you have prepared your server, you are ready to install and configure Active Roles.
1. Run Setup, which installs binaries and configures registry settings for Active Roles.
2. Run Active Roles Configuration Center, which creates and configures the Active Roles
database, Administration Service, and Web Interface.
Run Setup
Setup installs binaries and configures registry settings for Active Roles.
1. Log on with a user account that meets the requirements listed in Setup user account.
2. Navigate to the location of the Active Roles distribution package, and start the Setup
wizard by double-clicking ActiveRoles.exe.
3. In the Setup wizard, review the Introduction page, and click Next.
4. On the License Terms page, review the Active Roles license agreement, select
the option indicating that you accept the terms in the license agreement, and
then click Next.
5. On the Component Selection page, verify that the Administration Service, Web
Interface, and Console components are selected, and click Next.
6. On the Ready to Install page, click Install to begin installation.
7. On the Completion page, verify that the I want to perform configuration check
box is selected, and click Finish.
Setup will start Active Roles Configuration Center, allowing you to configure your Active
Roles installation (see Run Active Roles Configuration Center).
1. In the Active Roles Setup wizard (see Run Setup), select the I want to perform
configuration check box on the Completion page and click Finish to start Active
Roles Configuration Center.
You can also start Configuration Center by selecting Active Roles 8.1.3
Configuration Center on the Apps page or Start menu, depending upon the
version of your Windows operating system.
3. On the Service Account page, verify that the Logon name field displays the name
of your Setup user account, type the password of that user account in the Password
field, and then click Next.
4. On the Active Roles Admin page, verify that the Name field reads
BUILTIN\Administrators (which identifies the Administrators group of the
computer on which you are configuring Active Roles), and then click Next.
11. On the Administration Service page, select the Administration Service on the
computer running the Web Interface option, and then click Configure.
12. Wait for the wizard to complete the operation.
13. On the Completion page, click Finish to close the wizard.
Once you have installed the Collector, you can start the Collector wizard by selecting
Active Roles Active Roles Collector and Report Pack on the Apps page or Start
menu, depending upon the version of your Windows operating system.
Report Pack requires Microsoft SQL Server Reporting Services (SSRS). Make sure that you
have SSRS deployed in your environment. When deploying Report Pack, the Collector
wizard prompts you for the address (URL) of the Report Server Web service. You can find
this address on the Web Service URL page in the Reporting Services Configuration
Manager tool on the server where SSRS is installed.
1. Start the Collector wizard by selecting Active Roles Active Roles Collector and
Report Pack on the Apps page or Start menu, depending upon the version of your
Windows operating system.
2. On the Select Task page, click Deploy reports to Report Server, and then
click Next.
3. On the Report Server page, type the URL of your SSRS Report Server in the Report
Server Web Service URL box. Click Next.
By default, the URL is http://<ComputerName>/reportserver where
<ComputerName> stands for the name of the computer on which SSRS is installed.
Once the connection is established, the name of the Administration Service computer is
displayed in the brackets next to the console tree root.
NOTE: You can un-register domains by deleting their registration objects from the
Managed Domains container. To access that container, select the console tree root,
and then, in the details pane, click Go to Managed Domains in the Domains area.
This section provides sample procedures that illustrate how to manage users and groups in
Active Directory using the Active Roles console or Web Interface.
NOTE: To walk through the scenarios outlined in this chapter, you must be logged on as a
user with sufficient permissions in Active Roles. For example, it would suffice if you are
logged on as Active Roles Admin—a member of the Administrators group on the
computer running the Administration Service. Alternatively, you might be granted full
control of the organizational unit that holds your test users and groups. For information
on how to specify user permissions in Active Roles, see Delegating administration later in
this document.
Create a user
To create a user account
1. In the console tree, expand Active Directory and select the OU where you want to
add the user.
2. In the console tree, right-click the OU, and select New | User.
3. Type in the First name, Last name, and User logon name boxes. Click Next.
4. Click the button next to the Password box to generate a password. Click Next.
5. If Microsoft Exchange Server is deployed in your test domain, you can make the user
mailbox-enabled. To do this, select the Create an Exchange mailbox check box.
Click Next.
6. If you need to specify additional properties of the new user, select the Display the
object properties when this wizard closes check box. Click Finish.
1. In the console tree, expand Active Directory and select the OU where you want to
add the group.
2. In the console tree, right-click the OU, and select New | Group.
3. Type a name for the new group, click the Group scope and Group type you want,
and then click Next.
4. If Microsoft Exchange Server is deployed in your test domain, you can establish an e-
mail address for the group. To do this, select the Create an Exchange e-mail
address check box. Click Next.
5. Use the Add and Remove buttons to populate the group membership list. When
finished, click Next.
6. If you need to specify additional properties of the new group, select the Display the
object properties when this wizard closes check box. Click Finish.
1. Connect to the Web Interface for Administrators: Open your Web browser and
navigate to http://localhost/ARWebAdmin.
2. In the Search box on the header of the Web Interface page, type the name of the OU
where you want to create the user, and then press Enter.
3. In the list of search results, click the name of the OU.
4. In the right pane of the Web Interface page, click New User.
5. Type in the First Name, Last Name, and User logon name boxes. Click Next.
6. Click the Generate button (beneath the Confirm password box) to generate a
password. Click Finish (or Next, if Microsoft Exchange Server is deployed in your
test domain).
7. If Microsoft Exchange Server is deployed in your test domain, you can create a
mailbox for the new user. To do this, select the Create an Exchange mailbox
check box. Click Finish.
8. Close the property page that appears.
9. In the Search box on the header of the Web Interface page, type the name of the
user account you have created.
10. In the list of search results, select the check box next to the name of the
user account.
11. In the right pane of the Web page, click Member Of.
12. On the Member Of page that appears, click the Add button.
13. On the Select Object page that appears, choose the groups to which you want to
add the user account:
a. Specify search criteria and press Enter to build a list of groups.
b. Choose the desired groups by selecting the check box next to the name of the
group in the list.
c. When finished, click OK.
For example, you can type group names separated by a semicolon in the Search box
at the top of the Select Object page, and then press Enter.
14. To remove the user account from groups, on the Member Of page, select the check
box next to the name the group and then click the Remove button.
1. Connect to the Web Interface for Help Desk: Open your Web browser and navigate to
http://localhost/ARWebHelpDesk.
2. In the Search box on the header of the Web Interface page, type the name of the
user you want to find, and then press Enter.
3. In the list of search results, select the check box next to the name of the
user account.
4. In the right pane of the Web Interface page, click Reset Password.
5. On the Reset Password page that appears, click the Generate button.
Perform self-administration
Active Roles makes it possible to authorize users to administer their own accounts in Active
Directory. Specifically, users may be permitted to modify personal information in their
accounts. An administrator can use the Active Roles console to delegate this task.
To delegate self-administration
1. In the console tree, select the domain or OU where you want to delegate the self-
administration task.
2. Right-click the selection and click Delegate Control.
3. In the Active Roles Security dialog box, click Add.
4. Follow the steps in the Delegation of Control Wizard.
5. On the Users or Groups page, click Add, use the Select Objects dialog box to
select the Self object, and then click Next.
6. On the Access Templates page, expand User Self-management, and select the
check box next to Self - Account Management. Click Next.
7. Click Next two times, and then click Finish.
8. In the Active Roles Security window, click OK.
Once you have delegated the self-administration task, you can check how users can
perform self-administration in the Active Roles Web Interface.
Delegating administration
1. In the Active Roles console, right-click the OU, and then click Delegate Control.
2. In the Active Roles Security window, click Add.
3. Follow the steps in the Delegation of Control wizard.
4. On the Users or Groups page, click Add.
5. Select the group to which you want to assign the Help Desk role and click OK.
6. Click Next.
7. On the Access Templates page, expand Active Directory, select the check box
next to Users – Help Desk, and then click Next.
8. Click Next, click Next, and then click Finish.
9. In the Active Roles Security window, click OK.
To enable the delegated administrators to browse OUs in the domain, you must grant them
the Read All Properties permission on the OU objects at the domain level.
1. Select the domain and use the Delegation of Control wizard as described in the
previous procedure.
1. Open the Active Roles console and connect to the Administrative Service as the
delegated administrator:
a. Right-click the console tree root, and then click Connect.
b. In the Connect to Administration Service dialog box, click Options.
c. In the Connect as area, click The following user and specify the user logon
name and password of the delegated administrator.
2. In the console tree, select the OU for which the delegated administrator is assigned
the Help Desk role.
3. Verify that you can reset passwords and unlock accounts: Right-click a user account
in the details pane, and click Reset Password.
4. Verify that you can view user properties: Right-click a user account in the details
pane, and click Properties.
The delegated administrator can also use the Web Interface to perform administrative
tasks. Take the following steps to verify the rights of a delegated administrator using the
Active Roles Web Interface.
1. Log on to your computer with the delegated administrator’s user name and
password.
2. Connect to the Web Interface for Help Desk: Open your Web browser and navigate to
http://localhost/ARWebHelpDesk.
3. In the Search box on the header of the Web Interface page, type the name of the
OU for which the delegated administrator is assigned the Help Desk role, and then
press Enter.
4. In the list of search results, click the name of the OU to display a list of objects
held in that OU.
5. In the list of objects, select the check box next to the name of a user account.
The examples in this section demonstrate how to configure Managed Units, and allow you
to see how Managed Units work.
Managed Unit (MU) is a collection of objects (administrative view), created for the purposes
of distribution of administration, enforcement of business rules, and management of
complex network environments. Managed Units provide the capability to separate the
management framework from the Active Directory design. By using Managed Units,
directory objects can be grouped into administrative views regardless of object location in
Active Directory.
1. Start the Active Roles console and connect to the Administration Service.
2. Ensure that the console is in Advanced View mode: On the View menu, click Mode,
and then select the Advanced Mode option.
3. In the console tree, expand Configuration, right-click Managed Units, and select
4. In the Name box, type the name of the Managed Unit - Sales MU. Click Next.
5. Click Add.
6. In the list of rule types, click Include by Query. Click OK.
7. From the Find list, select Organizational Units.
8. Click Browse next to the In box, and select your test domain.
9. In the Name box, type *Sales*
10. Optionally, click Preview Rule.
The window displays a list of all the Sales OUs found.
This procedure ensures that all OUs with names containing ‘Sales’ are included in the Sales
MU. If you only want the MU to include the OUs with specific names, such as ‘PHX Sales
OU’, ‘BST Sales OU’ and ‘SEA Sales OU’, use explicit inclusion. To create the Sales MU using
explicit inclusion, modify the above procedure as follows:
1. In the Active Roles console, right-click the Sales MU, and then click Delegate
Control.
2. In the Active Roles Security window, click Add.
3. Follow the steps in the Delegation of Control wizard.
4. On the Users or Groups page, click Add.
When assigned the Full Control role for an MU, the delegated administrator is authorized to
view the MU and manage all objects in it. In the Active Roles console, the MU appears under
Managed Units in the console tree.
1. Start the Active Roles console and connect to the Administrative Server as the
delegated administrator:
a. Right-click the console tree root, and then click Connect.
b. In the Connect to Administration Service dialog box, click Options.
c. In the Connect as area, click The following user and specify the user logon
name and password of the delegated administrator.
2. In the console tree, expand Managed Units | Sales MU, and select an OU.
3. Verify that you can administer objects in the OU: Right-click an object in the details
pane and use commands on the shortcut menu.
4. Verify that you can create new objects: In the console tree, under Sales MU, right-
click an OU, point to New, and select the type of the object to create.
Delegated administrators can also use the Web Interface to perform administrative tasks.
Take the following steps to verify the rights of the delegated administrator using the Active
Roles Web Interface.
1. Log on to your computer with the user name and password of the delegated
administrator.
2. Connect to the Web Interface for Administrators: Open your Web browser and
navigate to http://localhost/ARWebAdmin.
3. On the Web Interface Home page, click Directory Management.
The examples in this section demonstrate how to configure provisioning policies, and allow
you to see how provisioning policy enforcement works in Active Roles.
NOTE: The instructions in this section assume that you are logged on as an Active Roles
Admin. The Active Roles Admin account is specified when installing the Administration
Service, and defaults to the Administrators local group of the computer running the
Administration Service.
To enforce these naming conventions, you need to create and apply an Active Roles
Policy Object.
Next, perform the following steps to configure policy for the User logon name and User
logon name (pre-Windows 2000) properties.
1. In the console tree, right-click an OU in your test domain, and select New | User.
2. Fill in the First name and Last name boxes.
3. Verify that the console automatically fills in the Full name, User logon name, and
User logon name (pre-Windows 2000) boxes in accordance with the user
naming conventions.
4. Complete the New Object - User wizard.
5. Right-click the newly created user account, click Properties, and examine the
Properties dialog box to verify that the user properties are in compliance with the
naming conventions.
Use the following steps to see how the naming conventions are enforced when you create a
user account using the Active Roles Web Interface.
1. In the Web Interface for Administrators, select an OU from your test domain.
2. In the right pane of the Web Interface page, click New User.
3. Fill in the First Name and Last Name fields.
1. In the Active Roles console, right-click your test domain, and click Enforce Policy.
2. In the Active Roles Policy window, locate the list entry named User Naming
Conventions, and select the Blocked check box in that entry.
3. Click OK to close the Active Roles Policy window.
You must also take certain steps to override the effect of the default logon name generation
policy. You may block the policy effect for the entire domain or for individual containers
within the domain.
1. In the Active Roles console, right-click your test domain (or a certain container, such
as OU), and click Enforce Policy.
2. In the Active Roles Policy window, locate the list entry named Built-in Policy -
Default Logon Name, and select the Blocked check box in that entry.
3. Click OK to close the Active Roles Policy window.
1. The first character of the user first name, followed by the user last name
2. The first two characters of the user first name, followed by the user last name
3. The first three characters of the user first name, followed by the user last name
The length of the policy-generated name is at most 8 characters. If the name is longer,
trailing characters are truncated as needed.
Examples of names generated by this policy are as follows:
l JSmitson
l JoSmitso
l JohSmits
1. In the Active Roles console, right-click the User Logon Name Generation Policy
Object, and click Properties.
2. On the Policies tab, select the policy, and then click View/Edit.
3. Remove the uniqueness number entry from the first rule:
a. On the Generation Rules tab, select the rule, and then click View/Edit.
b. In the Configure Value dialog box, select the Uniqueness number entry,
click Remove, and then click OK.
4. Add the second rule:
a. On the Generation Rules tab, click Add.
b. In the Configure Value dialog box, click Add.
c. In the Add Entry window:
i. Select the User Property entry type
ii. Select the First name property
iii. Click The first and then type 2
iv. Click OK
d. In the Configure Value dialog box, click Add.
e. In the Add Entry window:
i. Select the User Property entry type
ii. Select the Last name property
iii. Click OK
f. In the Configure Value dialog box, click OK.
5. Repeat Step 4, modifying Sub-step c) as follows in order to add the third rule: Click
The first and then type 3.
6. On the Generation Rules tab, select the Allow manual edits of pre-Windows
2000 logon name check box, and then click Only if a unique name cannot be
generated by this policy.
1. In the Active Roles console, right-click your test domain, and click Enforce Policy.
2. In the Active Roles Policy window, locate the list entry named E-mail Alias
Generation, and select the Blocked check box in that entry.
3. Click OK to close the Active Roles Policy window.
The policy generates the alias John001.Smith for the user John Smith if the alias
John.Smith is in use. If both John.Smith and John001.Smith are in use, the policy
generates the alias John002.Smith, and so on.
The following two sections elaborate on the steps to implement this scenario.
You must also take certain steps to override the effect of the default e-mail alias generation
policy. You may block the policy effect for the entire domain or for individual containers
within the domain.
1. In the Active Roles console, right-click your test domain (or a certain container, such
as OU), and click Enforce Policy.
2. In the Active Roles Policy window, locate the list entry named Built-in Policy -
Default E-mail Alias, and select the Blocked check box in that entry.
3. Click OK to close the Active Roles Policy window.
1. In the Active Roles console, right-click your test domain, and click Enforce Policy.
2. In the Active Roles Policy window, locate the list entry named E-mail Alias
Generation, and select the Blocked check box in that entry.
3. Click OK to close the Active Roles Policy window.
1. In the console tree, expand Configuration, right-click Script Modules, and then
click Import.
2. Use the Import Script window to open the file RestrictGroupScope.ps1, located
in the folder %ProgramFiles%\One Identity\Active
Roles\8.1.3\SDK\Samples\RestrictGroupScope\
3. In the Script dialog box, click OK.
The module RestrictGroupScope is created in the Script Modules container. You can
view the script code in the details pane by selecting the module in the console tree.
1. In the console tree, right-click an OU in your test domain, and select New | Group.
2. Type a name for the group.
3. Under Group scope, click Universal.
4. Click Next.
This will cause an error message to appear stating that you cannot create
universal groups.
As you can see, the policy allows you to created a group with any scope except for
universal.
1. Using the Active Roles console, create a user account in any OU in your test domain.
2. Right-click the user account created in Step 1 and click Properties.
3. In the Properties dialog box, click the Profile tab.
4. On the Profile tab, in the Home folder area, examine the home folder path: The
path is identical to the network path you specified when creating the Policy Object,
with the user logon name (pre-Windows 2000) substituted for %USERNAME%.
5. On your file server, verify that the home folder is created.
6. In the Properties dialog box for the user account, click the Account tab.
This section provides sample procedures that illustrate how you can use the Active Roles
Console or Web Interface to perform Exchange tasks, and manage Exchange-related
properties of users and groups. To follow these procedures, you must have a supported
Microsoft Exchange Server version installed in your test domain. For the list of Exchange
Server versions supported by Active Roles, see System requirements in the Active Roles
Release Notes.
NOTE: Mailboxes can be created only for Users, enabling mailbox for a Contact is
not allowed.
To create a mailbox for an existing user by using the Active Roles console
1. Connect to the Web Interface for Administrators: Open your Web browser and
navigate to http://localhost/ARWebAdmin.
2. In the Search box on the header of the Web Interface page, type the name of the
user account, and then press Enter.
3. In the list of search results, select the check box next to the name of the
user account.
4. In the right pane of the Web Interface page, click Create User Mailbox.
5. Verify that the information in the Alias and Mailbox database boxes is correct, and
then click the Finish button.
1. Right-click the mailbox-enabled user account you want to modify, and then click
Properties.
2. On the E-mail Addresses tab, double-click the address you want to modify.
3. Modify the e-mail address information that appears for the address you have
selected, and click OK.
4. Click OK to close the Properties dialog box.
1. Connect to the Web Interface for Administrators: Open your Web browser and
navigate to http://localhost/ARWebAdmin.
2. In the Search box on the header of the Web Interface page, type the name of the
mailbox-enabled user account, and then press Enter.
3. In the list of search results, select the check box next to the name of the
user account.
4. In the right pane of the Web Interface, click Exchange Properties.
5. Click the E-mail Addresses tab on the Exchange Properties page that appears.
6. In the E-mail addresses list, click the address you want to modify, and then click
the Edit button.
7. In the E-mail Address dialog box that appears, modify the e-mail address
information as needed, and then click OK.
8. Click the Save button to commit your changes.
The Active Roles console provides a centralized view of all permission entries for any object
in Active Directory. For each permission entry, the view displays a number of properties,
including the permission description, origin, and security principal. Additional properties of
permission entries can be displayed and the native security editor can be accessed.
To further simplify and enhance the management of permission entries, Active Rolessions
in Active Directory by using of Access Templates. Active Roles provides the option to
keep Active Directory native security updated with selected permissions specified using
Access Templates.
This section outlines the procedures to follow in order to see how Active Roles assists in
managing Active Directory permission entries.
4. On the Native Security tab, right-click an entry in the list, and then click
Properties to examine the selected permission entry.
The ACE Properties window displays the following properties of the permission
entry you have selected:
1. Select an Active Directory container to which you want to add permission entries.
2. Right-click the selection and click Delegate Control.
3. In the Active Roles Security window, click Add.
4. Follow the steps in the Delegation of Control wizard.
5. On the Permissions Propagation page, select the Propagate permissions to
Active Directory check box.
6. Complete the Delegation of Control wizard.
7. In the Active Roles Security window, click OK.
Once you have completed these steps, new permission entries are created in Active
Directory. You can examine them using the Active Roles console.
Active Roles maintains one-way synchronization from Active Roles security to each
permission entry defined with the Permissions Propagation option.
2. On the Active Roles Security tab, right-click an entry with the Yes label in the
Sync to Native Security column, click Desync to AD, and then click Yes.
The label in the Sync to Native Security column changes to No.
3. Go to the Native Security tab and refresh the view (press F5).
Active Roles removes the permission entries corresponding to the entry you selected
on the Active Roles Security tab in Step 2.
4. Go to the Active Roles Security tab, right-click the entry you selected in Step 2,
and then click Sync to AD.
The label in the Sync to Native Security column changes to Yes.
5. Go to the Native Security tab and refresh the view (press F5).
Active Roles adds the permission entries corresponding to the entry you selected on
the Active Roles Security tab in Step 4.
6. Go to the Active Roles Security tab, right-click a blank area of the tab, and
then click Add.
7. Follow the steps in the Delegation of Control Wizard to apply an Access Template.
8. On the Permissions Propagation page of the wizard, select the Propagate
permissions to Active Directory check box.
9. Go to the Native Security tab and refresh the view (press F5).
Active Roles adds the permission entries corresponding to the Access Template you
have applied by using the Delegation of Control Wizard.
The groups whose membership lists are automatically maintained by Active Roles are
referred to as dynamic groups. For dynamic groups, Active Roles ensures that their
membership lists include only those objects that match membership rules, even if
administrative tools other than Active Roles are used to manage groups.
To automate the maintenance of group membership lists, Active Roles provides:
l Rules-based mechanism that automatically adds and removes objects from groups
whenever object attributes change in Active Directory
l Flexible membership criteria that enable both query-based and static
population of groups
Active Roles processes membership rules in the following order by rule category:
l Include by Query
l Include Group Members
This section outlines the procedures to follow in order to configure dynamic groups and to
examine the behavior of dynamic groups.
NOTE: Once you have added a membership rule to a regular group, the group becomes a
dynamic group. This behavior does not depend on the type of the rule. When a group is
converted, all of its previous members are removed. Therefore, after you complete these
steps, the group only includes the objects you selected.
Next, add membership rules to further configure the dynamic group. To accomplish this
task, perform the following steps.
If you no longer want the group to be dynamic, right-click the group and then click Convert
to Basic Group. This operation only removes all membership rules from the group,
whereas the group membership list remains intact.
Explicit inclusion
To examine the behavior of membership rules based on explicit inclusion, perform the
following steps with the Active Roles console.
1. Open the Properties dialog box for your dynamic group, and go to the Members
tab: the objects you explicitly included in the group are in the membership list.
2. Close the Properties dialog box.
3. Rename, modify, or move objects you selected for the explicit inclusion.
4. Open the Properties dialog box for your dynamic group, and go to the Members
tab: the objects remain in the group membership list; for the objects you renamed,
the list displays new names.
Explicit inclusion adds objects by object ID that remains unchanged during the entire object
lifecycle. Once added through explicit inclusion, an object can only be removed from a
dynamic group in one of these ways:
l Delete the membership rule for explicit inclusion of that object.
l Add the membership rule for explicit exclusion of that object.
To add or remove membership rules, you can use the Membership Rules tab in the
Properties dialog box for the dynamic group.
Explicit exclusion
To examine the behavior of membership rules based on explicit exclusion, perform the
following steps using the Active Roles console. These instructions assume that you have
chosen the Administrator account for explicit exclusion from your dynamic group.
1. Open the Properties dialog box for Domain Admins group and go to the Members
tab to check that Administrator is a member of the Domain Admins group. Close the
Properties dialog box.
2. Open the Properties dialog box for your dynamic group, go to the Membership
Rules tab, and add the explicit inclusion rule that makes Administrator a member of
your dynamic group.
3. Apply your changes by clicking Apply in the Properties dialog box for your
dynamic group.
4. Go to the Members tab, click the Rebuild button and note that Administrator is not
a member of your dynamic group although each of the following rules adds
Administrator to the group:
l Explicit inclusion rule (you configured it in Step 2).
l Query-based inclusion rule (Administrator’s name begins with the letter a).
l Group membership inclusion rule (Administrator is a member of the group
Domain Admins).
Inclusion by query
To examine the behavior of query-based inclusion rules, perform the following steps using
the Active Roles console. These instructions assume that your query-based rule is
configured so that the group includes all users whose names begin with the letter a.
1. In any OU in your test domain, create a new user account with a full name that
begins with the letter a.
2. Open the Properties dialog box for your dynamic group, and go to the Members
tab: the new user account is in the membership list (unless it is removed from the
dynamic group by exclusion rules).
3. Rename an existing user account so that its new full name begins with the letter a.
4. Go to the Members tab in the Properties dialog box for your dynamic group, and
click the Rebuild button: the user account is added to the membership list (unless it
is removed from the dynamic group by exclusion rules).
5. Rename the user account you managed in Step 4 so that its new full name begins
with the letter b.
6. Go to the Members tab in the Properties dialog box for your dynamic group, and
click the Rebuild button: the user account is removed from the membership list
(unless it is added to the dynamic group by explicit inclusion rules).
1. Open the Properties dialog box for your dynamic group, and go to the Members
tab: the members of the Domain Admins group are in the membership list (except
those removed from the dynamic group by exclusion rules).
2. Add a member to the Domain Admins group.
3. Go to the Members tab in the Properties dialog box for your dynamic group, and
click the Rebuild button: the new member of the Domain Admins group is added to
your dynamic group (unless that member is removed from the dynamic group by
exclusion rules).
1. Open the Active Directory Users and Computers tool (run dsa.msc from a
command prompt).
2. In any OU in your test domain, create a user account with a full name that begins
with the letter a.
3. Open the Properties dialog box for your dynamic group, and go to the Members
tab: the new user is in the group membership list.
4. On the Members tab, select that user, and click Remove. Click Yes. Click OK.
5. Open the Properties dialog box for your dynamic group, and go to the Members
tab: the user is still in the group membership list.
Active Roles has detected the removal, and added the user to the group in
accordance with the membership rules.
Active Roles provides the capability to delegate administration of computer resources, such
as network shares, services, and logical printers. It is also possible to delegate
administration of local users and groups on member servers and workstations. Delegated
administrators can use the Active Roles Web Interface to manage computer resource.
Active Roles comes with a suite of Access Templates that facilitate the delegation of
computer management tasks. When applied to an OU, Access Templates from that suite
provide for the following levels of access to the computers placed in that OU:
l Full Control Perform all management tasks on computer resources.
l Local Account Operator Create, modify, and delete local user accounts and
groups.
l Network Share Operator Create, modify, and delete network shares.
l Print Operator View and modify properties of logical printers; manage print jobs.
l Service Operator Start/stop services; view/modify service properties.
l Server Operator Start/stop services; create, modify, and delete network shares;
pause/resume/cancel printing; view properties of all computer resources.
This section outlines the procedure you can use to assign the Server Operator role to a
delegated administrator for an OU, and briefly describes how to perform computer
management tasks using the Active Roles Web Interface for Administrators.
1. In the Active Roles console, right-click the OU and then click Delegate Control.
2. In the Active Roles Security window, click Add.
3. Follow the steps in the Delegation of Control wizard.
4. On the Users or Groups page, click Add.
5. Select the group you want to designate as the delegated administrator and click OK.
6. Click Next.
7. On the Access Templates page, expand Computer Resources, select the check
box next to Computer Management - Server Operator, and then click Next.
8. Click Next two times, and then click Finish.
To enable the delegated administrators to browse OUs in the domain, you must grant them
the Read All Properties permission on the OU objects at the domain level.
1. Select the domain and use the Delegation of Control wizard as described in the
previous procedure.
2. On the Access Templates page, expand Active Directory, and select the check
box next to OUs – Read All Properties.
1. Log on to your computer with the delegated administrator’s user name and
password.
2. Connect to the Web Interface for Administrators: Open your Web browser and
navigate to http://localhost/ARWebAdmin.
3. In the Search box on the header of the Web Interface page, type the name of the OU
for which the delegated administrator is assigned the Server Operator role, and then
press Enter.
4. In the list of search results, click the name of the OU to displays a list of computers
held in that OU.
5. In the list of computers, click select the check box next to the name of a computer.
This section describes how to view the Active Roles audit trail and how to work with Active
Roles reports.
1. On the computer running the Active Roles Administration Service, open Event
Viewer.
2. In the console tree, under Application and Services Logs, select the Active
Roles Admin Service log.
3. In the details pane, right-click an event, and then click Event Properties.
1. Open the Active Roles Collector wizard by selecting Active Roles Active Roles
Collector on the Apps page or Start menu, depending upon the version of your
Windows operating system.
2. On the Welcome page, click Next.
3. On the Select Task page, select the option Collect data from the
network. Click Next.
4. Click Browse and complete the SQL Server Connection wizard as follows.
You only need to complete the SQL Server Connection wizard once, when using the
Collector wizard for the first time.
5. On the SQL Server page, click Use SQL Server authentication, and set the other
options as follows:
a. In the Server box, enter <ServerName>\sqlexpress, replacing
<ServerName> with the name of the computer on which you installed SQL
Server Express.
b. In the Logon Name box, type sa.
c. In the Password box, type the password for the sa login.
6. Click Next.
7. On the Select database page, in the Database box, type ARServerReporting.
The wizard will create a database with the name you specify. It is advisable to
create a new database rather than select an existing database. If you select an
existing database, the data in that database may be corrupted during the data
collection process.
8. In the Configure Data Source dialog box, review the settings you have specified,
and then click OK.
4. Click Apply.
Active Roles uses the replication functionality of Microsoft SQL Server to copy and
distribute configuration data from one Administration Service database to another, and to
synchronize between configuration databases for consistency.
Administration Service database servers synchronized by using the SQL Server replication
function are referred to as replication partners. Each replication partner hosts a writable
copy of the Active Roles configuration data. Whenever changes are made on one replication
partner, the changes are propagated to the other replication partners.
This section outlines the procedures to follow in order for you to configure replication and
see how replication works in Active Roles. To use these procedures, you must install Active
Roles on two network computers, as described in the Test lab setup section earlier in this
document. Two Active Roles instances will be configured to replicate configuration data
with each other.
NOTE:
l Due to limited replication-related capabilities of SQL Server Express (may hold only
the Subscriber role), the scenario discussed in this section requires a different
edition of SQL Server (such as Enterprise, Standard, or Workgroup) to be used as
the Publisher role holder.
l For the purposes of this evaluation scenario, you may use the same SQL
Server to host the databases for both the Administration Services participating
in the scenario.
l When installing the second Administration Service, specify a database name that is
different from the name of the database used by the first Administration Service.
This ensures that each Administration Service uses a separate database, so two
databases could be synchronized with each other via replication of data.
Configure replication
When configuring Active Roles replication, you first create a replication group by
designating the database server of a particular Administration Service as the Publisher.
When planning to assign the Publisher role to the database server of a certain
Administration Service, ensure that the following requirements are met:
For evaluation purposes, you may configure both the SQL Server Agent service and the
Administration Service to log on as a user account that belongs to the Domain Admins
group of your test domain.
To assign the Publisher role to the database server of a certain Administration Service,
perform the following steps using the Active Roles console.
1. Open the Active Roles console and connect to the Administration Service whose
database server you want to designate as the Publisher.
2. In the console tree, expand Configuration, expand Server Configuration, and
then select Configuration Databases.
3. In the details pane, right-click the database server and click Promote.
4. In the confirmation message box, click Yes.
5. Wait while Active Roles completes the operation.
The new replication group now has a single member—the Publisher. You can add replication
partners—Subscribers. To add a Subscriber, perform the following steps using the Active
Roles console.
To add a Subscriber
1. Open the Active Roles console and connect to the Administration Server whose
database server you have designated as the Publisher.
2. In the console tree, expand Configuration, expand Server Configuration, and
then select Configuration Databases.
3. In the details pane, right-click the Publisher, and then click Add Replication
Partner.
4. Follow the instructions in the New Replication Partner wizard.
5. On the Database Selection page, click Browse.
6. Use the Connect to Administration Service dialog box to specify the
Administration Service whose database server you want to add to the replication
group. Click OK.
7. Click Next two times, and then click Finish.
1. Open the Active Roles console and connect to one of the Administration Services.
2. In the console tree, expand Configuration, right-click Managed Units, and select
New | Managed Unit.
3. Complete the New Object - Managed Unit wizard.
Wait a few minutes and then use the Active Roles console to verify that the new Managed
Unit is also created on the other Administration Service.
1. Open the Active Roles console and connect to the other Administration Service.
2. In the console tree, expand Configuration, and click Managed Units: the newly
created Managed Unit appears in the details pane.
You can create, modify, or delete Active Roles configuration objects, such as Managed
Units, Access Templates or Policy Objects, on one of the replication partners, regardless of
whether it is the Publisher or a Subscriber, and then connect to other replication partners
and see that your changes are propagated to all replication partners.
NOTE: Although Active Roles replication is configured to initiate the propagation of
changes immediately after the changes are made, it may take a few minutes for SQL
Server to propagate the changes between the Publisher and Subscribers.
The Active Roles Web Interface allows you to customize menus, commands, and forms
used to administer directory objects. You can add and remove commands or entire menus,
assign tasks and forms to commands, modify existing forms, and create new commands,
tasks, and forms.
To use the customization capabilities of the Web Interface, you must be logged on as Active
Roles Admin. If you have used the default settings when installing the Administration
Service, the Active Roles Admin account is set to the Administrators local group on the
computer running the Administration Service. So, to customize the Web Interface in your
test environment, log on with any user account that is a member of that group.
This section provides an example of how to customize the Site for Administrators. By
default, the Web Interface pages for user account creation do not include the box where
you could specify the user’s telephone number. After you complete the following steps, a
new field—Telephone Number—is added on the Web page for user account creation.
When you fill in that field, the number is saved in the telephoneNumber property of the
user account.
1. Connect to the Web Interface for Administrators: Open your Web browser and
navigate to http://localhost/ARWebAdmin.
2. On the Web Interface Home page, click Customization.
3. On the Customization page that appears, click Customization Tasks.
This displays a list of object types. Each object type is linked with a list of commands,
referred to as a menu. When you manage an object in the Web Interface, the menu
linked with the type of that object provides the commands to perform management
tasks. Since you want to customize the behavior of the user creation command, you
7. On the toolbar in the Form Editor, point to Add Entry and click Create.
This displays a list of properties. You can select the property you want to manage by
using the new entry.
10. Click Save, and then click Reload on the message bar that appears at the top of the
Form Editor page.
NOTE: You can undo the changes you have made: In the leftmost pane of the
Web Interface page, click to expand the Customization item, and then click
Restore Default.
NOTE: You can also use the Customize link to add and remove user interface elements
from the form. This link is equivalent to the command Edit Form.
About us
One Identity solutions eliminate the complexities and time-consuming processes often
required to govern identities, manage privileged accounts and control access. Our solutions
enhance business agility while addressing your IAM challenges with on-premises, cloud and
hybrid environments.
Contacting us
For sales and other inquiries, such as licensing, support, and renewals, visit
https://www.oneidentity.com/company/contact-us.aspx.