ActiveRoles 7.4 How To Guide
ActiveRoles 7.4 How To Guide
One Identity Active Roles 7.4
How-To Guide
Copyright 2019 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
IMPORTANT, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting
information.
Active Roles How-To Guide
Updated - December 2019
Version - 7.4
Contents
What’s New 1
What’s new in Active Roles 7.4 1
What’s new in Active Roles 7.3 2
What’s new in Active Roles from version 7.0 3
System Requirements 9
Ports Used by Active Roles 9
Product Licensing 17
Clean Installation 20
Installing the Active Roles service 20
Installing the Web interface 21
Synchronization Service 27
Capture Agent 29
Upgrade from Quick Connect 29
Limitations 30
Synchronization Service upgrade 30
Communication Ports 31
Customizations 36
Troubleshooting 37
Performance 37
Safe Mode 37
Error and Log resources 38
Active Roles Log Viewer 40
Replication 42
Service Account 47
Changing Active Roles service account credentials 47
Changing Service account credentials for SQL database connection 47
About us 49
Contacting us 49
Technical support resources 49
What’s New
l Additional Hybrid Directory features:
l Support for Office 365 Group CRUD activities.
l Support for Office 365 roles and reporting for Office 365 users.
l Support for Exchange Online Mailbox Properties for Office 365 users in
Federated and Synchronized environment.
l Support for provisioning objects in SaaS products.
l Separate configuration and management history databases during installation or in-
place upgrade, confirming to Microsoft standards and best practices for replication.
l Support for Azure AD Graph 1.6 for Active Roles Synchronization Services.
l Use of Group Managed Service Account (gMSA) for Active Roles Service account.
l Bulk attribute operations for multiple users.
l Reset the password for multiple users at one time.
l Solution Intelligence for Active Roles.
l Log in to MMC interface through 2FA authentication.
l Support for remote mailbox creation and modification.
NOTE: The ‘Remote mailbox migration (RemoteMailbox.ps1)’ script has been
provided as a sample script only, to illustrate the steps required, and should not
be used as-is in a production situation without modification and enhancement.
The use of security credentials within a script in clear text should never be
considered appropriate or secure. In testing this script, care and consideration
Enhancements
l Support for the multiSubnetFailOver feature of MS SQL Server to maximize
internal availability.
l Support for Archive Mailbox-Exchange Online functionality.
l Support for the Security Identity Mappings functionality as available in Active
Directory Users and Computers (ADUC) Snap-in.
l Workflow enhancements that enable you to add Azure or Office 365 modules in
PowerShell and run the Office 365 services such as Skype for Business, Azure
AD, Azure RM, AZ, and Sharepoint Powershell scripts within existing Active
Roles workflows.
l Restrict MMC interface access to users, by enabling the MMC Interface access
settings using the Configuration Center. By default, on installing Active Roles, all
users are enabled to log in to the MMC interface. You can now enable the MMC
interface access setting to restrict users from accessing the MMC interface.
l Enhancement of SPML operation to get ObjectSid to retrieve the value in the SID
format along with the base64Binary format.
l Creation of OneDrive for Azure AD users using OneDrive Provisioning Policy.
l Configuring secure communication for Active Roles Web interface using Force SSL
Redirection.
l Support for One Identity Hybrid Subscription
l Support for Hybrid Directory Mailbox Management
l Support for Microsoft SQL Server 2017
l Support for connecting to One Identity Starling, the Software as a Service (SaaS)
solution of One Identity through Active Roles
l Integration of Starling Two-factor Authentication with Active Roles through the Web
l Web Interface has been redesigned for greater clarity and ease of use, to ensure
consistent look and feel, improve user experience, and simplify and streamline
management tasks.
l A new component, Synchronization Service, performs data synchronization and
replication tasks to enable user, group, or recipient management across various on-
premises systems and in the cloud.
l Integrated administration of users and mailboxes in Exchange resource forest
environments, with the ability to create and administer mailboxes by managing
mailbox users in external forests.
l Integrated administration of Lync Server users in single and multi-forest
environments, with the ability to enable, disable or re-enable users for Lync Server
and administer Lync Server user properties.
l Various improvements to Active Roles workflow, including new activities to help
access and modify workflow data context at run time, new activity options, and
workflow scripting capabilities.
l Support for Exchange 2010 remote Shell removes the need to install the
Exchange 2010 Management Tools on the computer running the Active Roles
Administration Service.
l Active Roles Configuration for Hybrid Environment.
l Azure AD /Office 365 Object Management in Hybrid Environment.
l Microsoft Office 365 License Management.
l Support for Microsoft Windows Server 2016.
Active Roles 7.4 introduces the following changes to Setup and Installation:
Numerous MSI files Single ActiveRoles.EXE
The components must be installed in the correct order.
Silent Install
The Active Roles installer, Setup.exe has command-line options for a silent installation.
For more details, refer to KB 185799
Example:
Setup.exe /quiet /install ADDLOCAL=Service,Console /IAcceptActiveRolesLicenseTerms
Configuration Center
The Configuration Center unifies management of core configuration for the Active Roles
Administration Service and Web Interface, which allows administrators to perform the core
configuration tasks from a single location.
Highlights include:
l Initial configuration tasks such as creation of Administration Service instances and
default Web Interface sites.
l Import of configuration and management history from earlier Active Roles versions.
l Management of core Administration Service settings, such as the Active Roles Admin
account, service account, and database connection.
l Graphical User Interface (Active Roles Configuration Center)
l PowerShell (Active Roles Management Shell)
l ActiveRolesManagementShell
l ActiveRolesConfiguration
ActiveRolesManagementShell
l Provides cmdlets for managing users, group, computers, and other objects in Active
Directory via Active Roles; managing digital certificates; and administering certain
Active Roles objects.
l Cmdlets are prefixed with QAD or QARS, such as New-QADUser, Add-QADCertificate, or
New-QARSAccessTemplateLink.
ActiveRolesConfiguration
l Provides cmdlets for configuring Active Roles Administration Service instances and
Web Interface sites.
l Available on 64-bit (x64) systems only. It requires the Active Roles Administration
Service or Web Interface to be installed; otherwise, the module does not provide
all cmdlets.
l The cmdlets provided in this module have their noun prefixed with AR, such as New-
ARDatabase, New-ARService, or New-ARWebSite.
Active Roles 7.4 introduces the following changes to system requirements:
l Active Roles can no longer be installed on Window Server 2008.
l Microsoft SQL Server 2005 is no longer supported. Microsoft SQL Server versions
2008 and later including 2017 are supported. The Configuration Center may be used
to import Active Roles databases from SQL Server 2005 to a later SQL Server
version. For details, see “Upgrading the Administration Service” in the Active Roles
Quick Start Guide.
l To manage Exchange recipients on Exchange Server 2010, Active Roles no longer
requires the Exchange 2010 Management Tools on the computer running the
Administration Service.
l Active Roles supports the following browsers only: Internet Explorer 11, Google
Chrome, Mozilla Firefox, and Microsoft Edge.
l Web Interface is optimized for screen resolutions of 1280 x 800 or higher. The
minimum supported screen resolution is 1024 x 768.
l Active Roles console requires Internet Explorer 11.
Active Roles 7.3 introduces the following changes to supported platforms:
l Exchange 2007 and earlier versions are no longer supported.
l Microsoft Exchange 2013 CU11 is not supported.
System Requirements
l Operating Systems Supported for Active Roles installation: Microsoft Windows 2008
R2 and later, including 2019
l SQL Server requirements: Microsoft SQL 2008 and later, including SQL 2019
l Microsoft .NET Framework: .NET 4.7.2
l Other software required for Active Roles may be installed from the Redistributables
folder on the installation media.
Resource Usage
The sizing of disk space and the SQL database capacities are best planned out by using the
Resource Usage Calculator, which is found in the Documentation folder on the
installation disk or image.
The Resource Usage Calculator is included with the installation media and can be
found under:
Documentation\ ActiveRoles_7.4_ResourceUsageCalc.xls
For more information on the system requirements, please see the Pre-Installation and
Upgrade section for the Active Roles Diagnostic and System Readiness Checker tools.
l Port 53 TCP/UDP Inbound/Outbound
l Port 88 (Kerberos) TCP/UDP Inbound/Outbound
l Port 135 (RPC endpoint mapper) TCP Inbound/Outbound
l Port 139 (SMB/CIFS) TCP Inbound/Outbound
l Port 445 (SMB/CIFS) TCP Inbound/Outbound
l Port 389 (LDAP) TCP/UDP Outbound
l Port 636 (LDAP SSL) TCP Outbound
l Port 3268 (Global Catalog LDAP) TCP Outbound
This port is required if Active Roles is configured to access the domain by using SSL.
l Port 3269 (Global Catalog LDAP SSL) TCP Outbound
This port is required if Active Roles is configured to access the domain by using SSL.
l The TCP port allocated by RPC endpoint mapper for communication with the
domain controller
Active Directory domain controllers can be configured to use specific port numbers for RPC
communication. For instructions, see http://support.microsoft.com/kb/224196.
l Port 135 (RPC endpoint mapper) TCP Inbound/Outbound
l The TCP port allocated by RPC endpoint mapper for communication with the
Exchange server
Exchange servers can be configured to use specific port numbers for RPC communication.
For instructions, see http://support.microsoft.com/kb/270836.
l Port 139 (SMB/CIFS on the managed computers) TCP Inbound/Outbound
l Port 445 (SMB/CIFS on the managed computers) TCP Inbound/Outbound
Computer restart
l Port 139 (SMB/CIFS on the managed computers) TCP Inbound/Outbound
l Port 137 (WINS) UDP Outbound
l Port 138 (NetBIOS datagrams) UDP Outbound
l Port 139 (SMB/CIFS on the servers that host home folders) TCP Inbound/Outbound
l Port 445 (SMB/CIFS on the servers that host home folders) TCP Inbound/Outbound
l Port 25 (Default SMTP port) TCP Outbound
Active Roles uses SMTP port 25 by default. The default port number can be changed in the
properties of the Mail Configuration object in the Active Roles console. If Mail Configuration
specifies a different port, open that port rather than port 25.
l The TCP port specified when registering the AD LDS instance with Active Roles
If SQL Server that hosts the Active Roles database is located behind the firewall, open the
following ports between Active Roles Administration Service and SQL Server:
l Port 1433 (Default SQL Server instance) TCP Inbound/Outbound
Open this port if the Active Roles database is on the default instance of SQL Server. If a
different port is assigned to the default instance, open that port rather than port 1433.
l Port 1434 (SQL Server Browser service) UDP Inbound/Outbound
Open this port if the Active Roles database is on a named instance of SQL Server. In this
case Active Roles uses UDP port 1434 to determine the port assigned to the named
instance, open port 1434 along with the TCP port assigned to the named instance.
If a firewall is required between Active Roles clients, such as MMC Interface, Web
Interface, ADSI Provider or Management Shell, and Active Roles Administration Service,
open the following ports in the firewall:
l Port 15172 TCP Inbound/Outbound
If the Active Roles Web Interface will be accessed through a firewall, open the
following ports:
l Port 80 (Default HTTP) TCP Inbound/Outbound
l Port 443 (Default HTTPS) TCP Inbound/Outbound
The Web Interface normally runs over port 80, or over port 443 if SSL is enabled (off
by default).
Synchronization Service
The Synchronization Service requires the following port to be open:
l Port 15173 TCP Outbound
The Capture Agent requires this port to be open (on the Domain Controller):
As Active Roles performs operations on objects on behalf of delegated users, the Active
Roles service account requires adequate permissions. The officially supported
configuration is to manage Active Directory domains by using a Domain Admin account.
If a Domain Admin's membership is restricted, it is necessary to grant the Active Roles
service account the following minimum permissions and access:
NOTE: Contact One Identity Sales for any assistance in engaging One Identity Profes-
sional Services.
The service account must be a member of the local Administrators group on the computer
running Active Roles Administration service.
For Active Roles clients to discover available Active Role services, the service account
must be able to publish itself in Active Directory. On the One Identity sub-container, under
the System container in the domain, grant the following rights:
• Create Container Objects
• Create ServiceConnectionPoint Objects
The service account must have at least Read Permissions in any Managed Domain. In
addition, the service account must have Modify Permissions rights on the Active
Directory objects and containers where the Active Roles security synchronization feature
will be utilized.
Exchange 2010
To manage Exchange recipients on Exchange Server 2010, the service account or the
override account must be configured to have sufficient rights in the Exchange organization.
The rights must be delegated to the service account if an override account is not used;
1. Add the account to the Recipient Management role group. For instructions, see “Add
Members to a Role Group” at http://technet.microsoft.com/library/dd638143
(EXCHG.141).aspx.
2. Add the account to the Account Operators domain security group.
3. Enable the account to use remote Exchange Management Shell. For instructions, see
“Enable Remote Exchange Management Shell for a User” at
http://technet.microsoft.com/library/dd298084(exchg.141).aspx.
4. Ensure that the account can read Exchange configuration data (see Permission to
read Exchange configuration data).
5. Restart the Administration Service after changing the configuration of the account:
l Start Active Roles Configuration Center (see “Running Configuration Center” in
the Active Roles Administrator Guide), go to the Administration Service page in
the Configuration Center main window, and then click the Restart button at
the top of the Administration Service page.
NOTE: For instructions for Exchange 2010, 2013, 2016, and 2019, see the relevant
Microsoft Exchange pages at https://technet.microsoft.com/en-us/library.
The Exchange 2010 management tools are not required on the computer running the
Administration Service.
Exchange 2013, 2016, or 2019
To manage Exchange recipients on Exchange Server 2013, 2016, or 2019 the service
account or the override account must be configured to have sufficient rights in the
Exchange organization. The rights must be delegated to the service account if an override
account is not used; otherwise, the rights must be delegated to the override account. For
details, see the steps that follow.
1. Add the account to the Recipient Management role group. For instructions, see
“Manage Role Group Members” at http://technet.microsoft.com/library/jj657492
(exchg.150).aspx.
2. Add the account to the Account Operators domain security group.
3. Enable the account to use remote Exchange Management Shell. For instructions, see
“Enable remote Shell for a user” in the topic “Manage Exchange Management Shell
Access” at http://technet.microsoft.com/library/dd638078(exchg.150).aspx.
4. Ensure that the account can read Exchange configuration data (see Permission to
read Exchange configuration data).
5. Restart the Administration Service after changing the configuration of the account:
Start Active Roles Configuration Center (see “Running Configuration Center” in the
Active Roles Administrator Guide), go to the Administration Service page in the
To perform Exchange recipient management tasks, Active Roles requires Read access to
Exchange configuration data in Active Directory. This requirement is met if the service
account (or the override account, if specified) has administrator rights. For example the
service account , is a member of the Domain Admins or Organization Management group.
Otherwise, provide the account Read permission in the Microsoft Exchange container, using
the ADSI Edit console.
NOTE: The following instructions apply to the ADSI Edit console that ships with
Windows Server 2012 or Windows Server 2012 R2.
To provide Read access to the service account using the ADSI Edit console:
1. Open the ADSI Edit console, and connect to the Configuration naming context.
2. In the ADSI Edit console, navigate to the Configuration/Services container, right-
click Microsoft Exchange in that container, and then click Properties.
3. On the Security tab in the Properties dialog box that appears, click Advanced.
4. On the Permissions tab in the Advanced Security Settings dialog box, click Add.
5. On the Permission Entry page, configure the permission entry:
a. Click Select a principal, and select the desired account.
b. Ensure that the Type box indicates Allow.
c. Ensure that the Applies onto box indicates: This object and all
descendant objects.
d. In the Permissions area, select the List contents and Read all properties
check boxes.
e. Click OK.
6. Click OK to close the Advanced Security Settings dialog box, and then click OK to
close the Properties dialog box.
When performing Exchange recipient management tasks on Exchange Server 2010 or later,
Active Roles uses remote Exchange Management Shell to communicate with Exchange
Server. Hence, it is not required to install the Exchange management tools on the computer
running the Administration Service.
l Windows Server 2008 R2 SP1 or a later version of the Windows Server
operating system.
Remote Shell also requires the following:
l TCP port 80 must be open between the computer running the Administration Service
and the remote Exchange server.
l The user account the Administration Service uses to connect to the remote Exchange
server (the service account or the override account) must be enabled for remote
Shell. To enable a user account for remote Shell, update that user account by using
the Set-User cmdlet with the RemotePowerShellEnabled parameter set to $True.
l Windows PowerShell script execution must be enabled on the computer running
the Administration Service. To enable script execution for signed scripts, run
the Set-ExecutionPolicy RemoteSigned command in an elevated Windows
PowerShell window.
Product Licensing
After installing Active Roles 7.x (or upgrade to Active Roles 7.x), no additional steps are
required to activate the purchased commercial license for Active Roles.
Product usage statistics may be used to verify Active Roles licensing compliance. For
further details, see Evaluating Product Usage in the Active Roles Administrator Guide.
Active Roles 7.4 supports a direct upgrade from versions 6.9 and later including 7.2.1.
NOTE: If customizations have been implemented by One Identity Professional
Services, please contact One Identity Sales before proceeding with an installation or
upgrade, as all customizations may not function with newer versions.
1. Install the Active Roles Diagnostic Tools, which consists of Active Roles System
Checker, which should be run in order to confirm that the server has adequate
resources to host and run Active Roles 7.4. Navigate to the installation media.
2. Go to Solutions | Diagnostic Tools.
3. Double-click to run ActiveRolesDiagnosticsTools_1.4.0.msi.
The Active Roles Diagnostic Tools Setup Wizard is displayed.
4. Click Next.
5. In the License Terms window, read and accept the license agreement and click Next.
6. In the Custom Setup window, select the appropriate tools to install. It is
recommended to install the Active Roles Log Viewer, Directory Changes Monitor, and
the Active Roles System Checker for later use. Click Next.
7. In the Ready to Install window, click Install.
8. After the tools are installed, click Finish.
Clean Installation
For an installation demonstration, please refer to the following knowledge base article:
https://support.oneidentity.com/kb/258459
1. Run ActiveRoles.exe.
2. Accept the licensing agreement and click Next.
3. Select the desired components and click Next.
4. Review the summary and click Install.
By default, the I want to perform configuration option is selected.
1. Launch the Active Roles Configuration Center.
2. Click Dashboard.
3. Click Configure under the Web Interface section.
4. Select the appropriate service to connect to and click Configure.
5. After completing, click Finish.
Upgrading from Active Roles 6.9 to 7.x version is a side-by-side upgrade, which does not
interrupt operations or affect the configuration of the currently installed Active Roles
version. To ensure smooth upgrade to the new Active Roles version, upgrade the
Administration Service first, and then upgrade the Web Interface.
Active Roles 6.9 components are not used in the upgrade and neither are any components
from the earlier version uninstalled.
Before upgrading to the latest version of Active Roles, the add-ons of the earlier versions
must be uninstalled.
l After an upgrade of Active Roles components to Active Roles 7.4, the Office 365 add-
on which was supported in the earlier versions of Active Roles, ceases to work.
Hence, it is recommended to uninstall the Office 365 add-on prior to the upgrade of
Active Roles.
l Office 365 add-on is not supported on Active Roles 7.3 or later and must be
uninstalled prior to the installation of Active Roles 7.1.
l Active Roles 7.4 manages Office 365 and Azure AD natively.
For an upgrade demonstration, please refer to the following knowledge base article:
https://support.oneidentity.com/kb/257995
l There is no need to break replication when upgrading to Active Roles 7.4 from 6.9 as
Active Roles 7.3 or later does not support an in-place upgrade in this scenario. A
NOTE: During and post-installation of Active Roles 7.4, the existing installation
of Active Roles 6.9 will be available and fully functional. Hence, users will not
be affected during the upgrade process with the exception of Dynamic Groups.
For more details please review the knowledge base article, https://sup-
port.oneidentity.com/kb/211388.
l An upgrade of the Active Roles components may affect custom solutions. Custom
solutions (such as scripts and other modifications), which work fine as expected with
an earlier version of Active Roles may cease to work after the upgrade. Before
starting an upgrade, test the existing solutions with the new version of Active Roles
in a lab environment to verify that the solutions continue to work as expected after
the upgrade.
l If ERFM (Exchange Resource Forest Management) is installed on the Active Roles 6.9
version, it must be uninstalled before installing 7.4 as ERFM is now part of the
product. Failure to uninstall ERFM beforehand may result in conflicts and issues.
l If Lync Add-On is installed, it must be uninstalled before installing Active Roles 7.4 as
Lync is now an integrated product feature.
l If Office 365 Add-On is installed, it must be uninstalled before installing Active Roles
7.4 as this functionality is replaced with the inbuilt Azure Active Directory Hybrid
Integration.
l For additional information, please review Solution 111679:
https://support.oneidentity.com/kb/111679
l Due to the design changes implemented in Active Roles 7.x in the Web Interface, any
Web Interfaces and customizations from Active Roles 6.9 may not function in Active
Roles 7.4. It is recommended not to import. Please refer to KB 189186 for additional
information:
https://support.oneidentity.com/kb/189186
1. From the installation media, run ActiveRoles.exe.
2. Accept the licensing agreement and click Next.
3. Select the desired components and click Next.
4. Review the summary and click Install.
5. By default, the I want to perform configuration option is selected. Click Finish
to launch the Configuration Center
6. In the Configuration Center, under the Administration Service option click
Configure.
7. Select a service account that will run the Active Roles service and click Next.
8. Choose the appropriate security group that will hold the role of the Active Roles
Admin group and click Next.
17. Click Next.
18. Once ready, click Import.
Office 365 Add-On that was previously available for Active Roles is no longer compatible
with Active Roles 7.4. Before proceeding with the upgrade from 7.0.x to 7.4, the Office 365
Add-On must be uninstalled.
For an upgrade demonstration, please refer to the following knowledge base articles:
l https://support.oneidentity.com/kb/257996
l https://support.oneidentity.com/kb/257997
Before upgrading, it is recommended to back up the Active Roles database. For general
best practices, please refer to the following Microsoft article:
https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/create-a-full-
database-backup-sql-server
It is recommended to back up the current Web Interfaces if any customizations have been
implemented.
Any Web Interfaces that were created in Active Roles 7.2.x will continue to function in 7.4.
However, it is recommended to thoroughly test before upgrading, as some customizations
may not work as expected in newer versions of Active Roles.
1. Launch the Active Roles Configuration Center.
2. Click Web Interface.
3. Select the desired site(s) and click Export Configuration.
1. Run ActiveRoles.exe from the installation media.
2. Click Next to continue.
Synchronization Service
Formerly a standalone product called Quick Connect, the Synchronization Service is now
part of Active Roles 7.4.
With Synchronization Service, complete automation can be implemented to process data
synchronization between the data systems.
Synchronization Service increases the data management efficiency by allowing automation
of the creation, deprovision, and update operations between data systems. For example,
when an employee joins or leaves the organization, the related information in the data
systems managed by Synchronization Service is automatically updated, thereby reducing
the administrative workload and getting the new users up and running faster.
In order to synchronize identity data between external data systems, Synchronization
Service must be configured to connect to these data systems through connectors. A
connector enables Synchronization Service to access specific data system to read and
synchronize data in that system according its settings. Out of the box, Synchronization
Service includes a number of built-in connectors:
l Active Roles versions 7.4, 7.3, 7.2.x, 7.1, 7.0 and 6.9
l Identity Manager version 8.1, 8.0, or 7.0
l Quest One Identity Manager version 6.1 or 6.0
l Delimited text files
l Microsoft Active Directory Domain Services
l Microsoft Active Directory Lightweight Directory Services
l Microsoft Azure Active Directory
l Microsoft Exchange Server
l Microsoft Skype for Business Server
l Microsoft Office 365
l Microsoft SharePoint
l Microsoft SQL Server
l OLE DB-compliant relational database
l Generic LDAP Directory service
l MY SQL Database
Capture Agent
Synchronization Service Capture Agent allows password synchronization between Active
Directory domains managed by Synchronization Service and other connected data
systems. The following diagram shows how the Password Synchronization feature of
Synchronization Service works:
Capture Agent tracks changes to user passwords in the source Active Directory domain and
provides that information to Synchronization Service, which in turn synchronizes the
changes with target connected data systems by using the configured password
synchronization rules. To synchronize passwords, install a Capture Agent on each domain
controller in the Active Directory source domain.
Limitations
Synchronization Service is unable to run synchronization workflows that employ
connections to the following systems:
l ActiveRoles Server 6.5
l Google Apps
l Novell eDirectory
l ODBC-compliant data source
l OpenDS directory service
l Oracle Database
l Oracle User Accounts
l PeopleSoft HCM
l Red Hat Directory Server
l SAP Systems
l Sun One Directory Server
l Workday
If it is necessary to synchronize data held in these systems, continue using Quick Connect
as not all connectors provided by Quick Connect are included with Synchronization Service.
Alternatively, One Identity Manager may support these systems.
1. Install Synchronization Service on the computer running Quick Connect or on a
different host.
2. Configure Synchronization Service to use a new database for storing configuration
settings and synchronization data. To perform this step, use the Configuration Wizard
NOTE: Before proceeding with this step, it is highly recommended to disable
the scheduled workflows and mapping operations in Quick Connect. The
scheduled workflows and mapping operations may be started after this step is
completed.
To import configuration settings:
a. On the computer where the Synchronization Service is installed, start the
Synchronization Service Administration Console.
b. In the upper right corner of the Administration Console window, click the gear
icon, and then click Import Configuration.
c. In the wizard that appears, select the correct version of Quick Connect Sync
Engine from which to import the configuration settings. Optionally, the Import
sync history check box may be selected to import the sync history along with
the configuration settings.
d. Follow the steps in the wizard to complete the import operation. If the
synchronization data to be imported is stored separately from the configuration
settings, then, on the Specify source SQL Server databases step, select
the Import sync data from the specified database check box, and specify
the database.
2. Retype access passwords in the connections that were imported from Quick Connect.
This is required due to security reasons. The import of configuration settings does not
retrieve the encrypted passwords from Quick Connect. Use the Synchronization
Service Administration Console to make changes to each connection as appropriate,
depending upon the data system to which the connection applies.
3. If the synchronization workflows involve synchronization of passwords, install the
new version of Capture Agent on the domain controllers.
The new version of Capture Agent replaces the old version. However, as the new
version supports both Synchronization Service and Quick Connect, the password
synchronization functions of Quick Connect will not be lost after the Capture
Agent is updated.
Communication Ports
Table 2: Communication ports
Outbound
For further information regarding Synchronization Service, refer to the Active Roles
7.4 Synchronization Service Administrator Guide included with the Active Roles
installation media.
Active Roles version 7.4 supports integration with One Identity Starling services. The
Starling Join feature in Active Roles now enables you to connect to One Identity Starling,
the Software as a Service (SaaS) solution of One Identity. The Starling Join feature enables
access to the Starling services through Active Roles thus allowing to benefit from the
Starling services such as Two-factor Authentication and Identity Analytics and Risk
Intelligence.
To start the wizard, click Configure in the One Identity Starling area on the Dashboard page
in the Configuration Center main window. For further information and step-by-step
instructions, see the “Initial configuration” topic in the “Installing and configuring the Web
Interface” section in the Active Roles Quick Start Guide.
A video demonstration is available in the following knowledge base article:
https://support.oneidentity.com/kb/258341
In order to use Starling Two-Factor Authentication with Active Roles, you must first
join One Identity Starling to Active Roles on the Active Roles Configuration Center. The
Join to One Identity Starling wizard also includes links, which provide assistance for
using Starling:
l The Online link displays information about the Starling product and the benefits you
can take advantage of by subscribing to Starling services.
l The Trouble Joining link displays the Starling support page with information on the
requirements and process for joining with Starling.
Reports
Reporting is an optional component of Active Roles. To use Active Roles reports, the
following components are required:
l Microsoft SQL Server Reporting Services (SSRS) must be installed and configured.
NOTE: If the SQL Server service and SRSS are on different hosts, a “Double-
Hop” authentication issue may occur. For more information, see the knowledge
base article, https://support.oneidentity.com/kb/69693.
l The Active Roles service account must have sufficient permissions to create and
write to a database on the SQL Server.
NOTE: The database cannot be pre-created, and must be created by Active
Roles.
l The Active Roles service account must have sufficient permission to publish reports
on the SRS server.
NOTE: Quest Knowledge Portal is no longer included with Active Roles 7.x. To
view reports, use the native SQL Server Report URL.
Customizations
Custom solutions (scripts or other modifications) may not function properly after an
upgrade due to compatibility issues. Prior to attempting an upgrade, test existing
customizations with the new version of Active Roles in a lab or test environment to verify
that the customizations function as expected. If compatibility issues arise during the test
process, please contact One Identity Sales to arrange assistance from One Identity
Professional Services.
Troubleshooting
The following sections provide information on troubleshooting Active Roles:
l Performance
l Safe Mode
Performance
For Active Roles performance, please refer to the following knowledge base article:
https://support.oneidentity.com/kb/185471
Safe Mode
Active Roles provides a troubleshooting option, referred to as safe mode, which starts the
Administration Service in a limited state. When safe mode is enabled, the Administration
Service disregards the following:
l Custom policies
l Workflows
l Scripts
l Scheduled tasks
l Other customizations that may block Active Roles from starting and operating
normally, and rejects connections from any user other than an Active Roles Admin.
Active Roles Admin can connect to the Administration Service and make changes in order
to fix or remove customizations that cause issues, and then disable safe mode.
1. Log on to the computer running the Administration Service with a user account that
has administrator rights on that computer.
NOTE: Local administrator rights are required to enable or disable safe mode.
2. Open Active Roles Management Shell on the computer running the
Administration Service.
3. Click Active Roles 7.4 Management Shell on the Apps page or Start menu
depending upon the version of the Windows operating system.
4. To enable safe mode, enter the following commands at the Management Shell
command prompt:
l Set-ARService -SafeModeEnabled $true
l Restart-ARService
5. To disable safe mode, enter the following commands at the Management Shell
command prompt:
l Set-ARService -SafeModeEnabled $false
l Restart-ARService
In versions earlier to Active Roles 7.0, after the logs are generated, the logs are sent to
One Identity Support for analysis as the logs on their own can be difficult to read.
l Errors encountered by the Administration Service and recorded in the log file
l Requests processed by the Administration Service and traced in the log file
l All trace records found in the diagnostic log file
l All events found in the event log file
Select an error in the list, and choose a command to look for the solution in Knowledge
Base. The command performs a search in One Identity Software Knowledge Base to list the
Knowledge Articles that can provide helpful information on how to troubleshoot the
selected error. Log Viewer can be used to:
l Search the list for a particular text string, such as an error message
l Filter the list by various conditions, to narrow the set of list items of interest
l View detailed information about each list item, such as error details, request details
or stack trace
The logs grow in size quickly. Therefore, it is recommended to enable logging right before
and disable logging immediately after the issue has been reproduced.
The file captures any activity being performed by the service, including the tasks
performed by connected users while debug logging is enabled.
In some scenarios, it may be required to leave the logging on for a specific period of time.
Due to the logs getting stored on the computer running Active Roles, sufficient hard drive
space may not be available. In this event, the following solution can help to set logging for
a specific interval and move the logs to another drive or network share:
l How to automate Active Roles logging (debug):
https://support.oneidentity.com/kb/8617
For the Web Interface, there is a separate log file,<name of Site>.log.
Replication
For a video demonstration, please refer to the following knowledge base article:
https://support.oneidentity.com/kb/234198
For additional information and troubleshooting, please refer to the Active Roles 7.4
Administration Guide.
The Management History feature provides information on who did what and when it was
done with regard to the Active Directory management tasks performed using Active Roles.
This feature provides a clear log, documenting the changes that have been made to a given
object, such as a user or group object. The log includes entries regarding actions
performed, success or failure of the actions, as well as which attributes were changed.
The Management History feature can be used to examine:
l Change History Information on changes that were made to directory data via
Active Roles.
l User Activity Information on management actions that were performed by a
given user.
Both Change History and User Activity use the same source of information—the
Management History log, also referred to as the Change Tracking log. For information on
the configuration settings of the Change Tracking log, see the Management History
configuration section.
Active Roles also includes reports to examine management history by collecting and
analysing event log records. For more information on reports, see the Active Roles
Reporting section. However, the process of retrieving and consolidating records from the
event log may be time-consuming and inefficient.
NOTE: You must import the Management History from the old version after an
upgrade in order to perform Deprovisioning operations and Undo Temporal Group
operations.
l Who made the most recent changes to a given user or group object?
l Who modified a given user or group object during the last X days?
l What changes were made to a given user object last night (yesterday, the
day before)?
l Have any planned modifications of a given user or group object actually been
performed?
l What objects did a given delegated administrator modify during the last X days?
Management History can be accessed instantly whenever an investigation is required or
troubleshoot a problem that results from inappropriate modifications of directory data.
Management History includes a dedicated repository to store information about data
changes, referred to as the Change Tracking log, and GUI to retrieve and display
information from that repository. No additional tasks, such as collecting or consolidating
information, are required to build Management History results. However, the advantages
of the Management History feature also entail some limitations. Before using the
Management History feature, consider the following recommended best practices and
limitations of using this feature. The main factor to consider is the size of the Change
Tracking log. To ensure real-time update of the log on all Administration Services, the log
is normally stored in the Active Roles configuration database, but can be separated into its
own database if required. This imposes some limitations on the log size. By default, the
Change Tracking log is configured to store information about changes that occurred within
last 30 days. If the setting is increased, do so carefully; otherwise, the following problems
may be encountered:
l Excessive increase in the log size significantly increases the time required to build
and display Change History and User Activity results.
l As the log size grows, so does the size of the configuration database. This
considerably increases the time required to back up and restore the database, and
causes high network traffic replicating the database when an additional
Administration Service is joined to Active Roles replication.
l The GUI is not suitable to represent large volumes of Management History results in
a manageable fashion. Since there is no filtering or paging capabilities, it may be
difficult to sort through the results.
To address these limitations, Active Roles provides different means for change auditing,
change-tracking reports, included with the Active Roles Report Pack. These reports are
designed to answer the following questions:
l What management tasks were performed on a given object within a certain
period of time?
Change-tracking reports are based on data collected from event logs. A separate log is
stored on each computer running the Administration Service, and each log contains events
generated by one Administration Service only. Therefore, to use reports, the events from
all event logs need to be consolidated to form a complete audit trail. The process of
consolidating events, referred to as the data collection process, is performed by a separate
Active Roles component—Collector. The Collector wizard can be configured to execute data
collection jobs, and schedule them to run on a regular basis. The main limitation of change-
tracking reports is the fact that the information needs to be collected and consolidated in a
separate database before the reports can be built. The data collection process exhibits the
following disadvantages:
l Collecting data may be a very lengthy operation and the database size may grow
unacceptable when collecting all events that occurred within a long period of time in
a large environment.
l Collecting data is impossible over slow WAN links. This limitation is inherent to the
Active Roles component intended to collect data for reporting.
l Change-tracking Policy Builds the data pertinent to history of changes made to
directory objects, and specifies what changes are to be included in the reports on
change history and user activity.
l Change Tracking Log Configuration Specifies how many change requests are to be
stored in the log.
l Replication of Management History Data Specifies whether to synchronize
Management History data between Administration Services that use different
databases.
Reference
Management History is being synchronized, the Active Roles service is unavailable:
https://support.oneidentity.com/kb/103363
Management History Wizard:
https://support.oneidentity.com/kb/90375
Important Considerations
The Management History Migration Wizard was designed for a "one-to-one" database
migration for an Active Roles upgrade. It was designed to speed up the upgrade process as
NOTE: The Configuration database import functionality performs a Replace action.
This operation overwrites current settings.
Active Roles stores its configuration data in the Configuration database in SQL. It is
recommended to backup Configuration and Management History databases prior to
the upgrade.
For more information on upgrade paths, refer to the knowledge base article
https://support.oneidentity.com/kb/111679.
Service Account
Active Roles 7.0 introduced the Configuration Center, which provides a simple method for
changing or updating the Active Roles service account.
1. Launch the Active Roles Configuration Center.
2. Click Administration Service tab.
3. Click Change on the Service Account.
4. Enter the new credentials and click Change.
5. After completing, click Finish.
To start using the new credentials, you must restart the service. Restart the service
immediately or later, at a more convenient time.
To start using the new credentials, you must restart the service. Restart the service
immediately or later, at a more convenient time.
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 or other inquiries, visit https://www.oneidentity.com/company/contact-us.aspx
or call +1-800-306-9329.
l Submit and manage a Service Request
l View Knowledge Base articles
l Sign up for product notifications
l Download software and technical documentation
l View how-to-videos at www.YouTube.com/OneIdentity
l Engage in community discussions
l Chat with support engineers online
l View services to assist you with your product