Capture Agent
To synchronize passwords from an Active Directory (AD) domain to some other connected data system, you must install Active Roles Capture Agent on all domain controllers (DCs) in the source AD domain.
This section lists the system requirements of Active Roles Capture Agent.
All Active Roles components require:
Table 15: Capture Agent requirements
|
Operating system |
The DCs on which you install Active Roles Capture Agent must run one of the following operating systems with or without any Service Pack (both x86 and x64 platforms are supported):
-
Microsoft Windows Server 2022
-
Microsoft Windows Server 2019
-
Microsoft Windows Server 2016
For more information, see the Active Roles Administration Guide. |
Use of this software is governed by the Software Transaction Agreement found at www.oneidentity.com/legal/sta.aspx. This software does not require an activation or license key to operate.
The product usage statistics can be used as a guide to show the scope and number of managed objects in Active Roles.
NOTE: You must run the Active Roles installer with administrator privileges.
|
|
CAUTION: Starting from Active Roles 7.6, Starling Two-Factor Authentication (2FA) is no longer supported and has been removed from Active Roles. If you use Starling with Starling 2FA enabled, before upgrading to Active Roles 7.6.2, disable Starling 2FA to remove it from your Starling configuration. Upgrading from an earlier Active Roles 7.x version to Active Roles 7.6.2 with Starling 2FA enabled can result in Active Roles not working as intended.
-
To disable Starling 2FA, in the Active Roles Configuration Center, Navigate to Starling > Starling 2FA and clear the Enable Starling 2FA check box.
-
(Optional) To unjoin Starling, in the Active Roles Configuration Center, navigate to Starling, and click Unjoin One Identity Starling. |
You can upgrade any 7.x version of Active Roles to Active Roles 7.6.2.
For instructions on how to upgrade from an earlier version of Active Roles, see the Active Roles Quick Start Guide.
NOTE: Consider the following before upgrading to a new version of Active Roles:
-
Components of an earlier Active Roles version may not work with the components of the new version you are upgrading to.
-
Custom solutions (scripts or other modifications) that rely on Active Roles features may fail to work after an upgrade due to compatibility issues. Therefore, before starting the upgrade, test your existing solutions with the new version of Active Roles in a lab environment to verify that your custom solutions will continue to work.
TIP: When upgrading to a new Active Roles version, One Identity recommends upgrading the Active Roles Administration Service first, and the client components (Active Roles Console and Active Roles Web Interface) afterwards.
For instructions on how to upgrade from an earlier version of Active Roles or how to install and initially configure Active Roles, see the Active Roles Quick Start Guide.
For special considerations regarding the installation of Active Roles 7.6.2, see the following information.
Changes related to Azure tenants
NOTE: If your organization has any Azure tenants that are managed with Active Roles, you need to reauthenticate and reconsent them after installing Active Roles 7.6.2. Otherwise, Active Roles will not receive the required permissions for managing existing Azure tenants, and tenant administration in Active Roles 7.6.2 will not work correctly. For more information, see Reconfiguring Azure tenants during upgrade configuration in the Active Roles Quick Start Guide.
Changes related to Active Roles
NOTE: Active Roles 7.5 introduced support for Modern Authentication in Azure BackSync workflows of the Active Roles . After upgrading to Active Roles 7.5 or 7.6.2 from an earlier version, if you previously had an Azure BackSync workflow configured, you will be prompted to reconfigure it in the Active Roles Console.
|
|
CAUTION: If you previously had an Azure BackSync workflow configured in Active Roles , and you use more than one Azure Active Directory (Azure AD) service in your deployment, you must specify the Azure AD for which you want to configure Azure BackSync. Failure to do so may either result in directory objects not synchronized at all, or synchronized to unintended locations.
For more information on how to specify the Azure AD used for back-synchronization, see Configuring automatic Azure BackSync in the Active Roles Administration Guide. |
