Unattended installation of Active Roles components
Active Roles supports Command line options for the installation of Active Roles Server. The following is a list of command line options available with Active Roles Server 7.4:
- Properties
ADDLOCAL=
Comma-separated list of Active Roles components to install.
REMOVE=
Comma-separated list of Active Roles components to remove.
TARGETDIR=
Path to the desired install folder.
- Component names
- ALL - all components
- Service - Administration Service
- Web - Web Interface
- Console - Console (MMC Interface)
- Tools - Management Tools
- SyncService - Synchronization Service
- Parameters
- /IAcceptActiveRolesLicenseTerms
- Required when both the /quiet and /install parameters are specified.
- By specifying this parameter, you acknowledge that you have read and understand the terms in the Active Roles license agreement.
- /install [optional properties]
- Takes effect if no Active Roles components installed; otherwise, disregarded.
- Installs components specified by ADDLOCAL property to TARGETDIR folder.
- If ADDLOCAL omitted, installs all components except Synchronization Service.
- To install Synchronization Service, you have to specify ADDLOCAL=SyncService.
- If TARGETDIR omitted, installs to %programfiles%\One Identity\Active Roles\.
Examples:
ActiveRoles.exe /quiet /install /IAcceptActiveRolesLicenseTerms
ActiveRoles.exe /quiet /install ADDLOCAL=Service,Console /IAcceptActiveRolesLicenseTerms
ActiveRoles.exe /quiet /install ADDLOCAL=Console TARGETDIR=D:\Active Roles\ /IAcceptActiveRolesLicenseTerms
When a user signs up for a Microsoft cloud service such as Azure Active Directory, details about the user’s organization and the organization’s Internet domain name registration are provided to Microsoft. This information is then used to create a new Azure AD instance for the organization. The same directory is used to authenticate sign in attempts when you subscribe to multiple Microsoft cloud services.
The Azure AD instance of the organization, also called the Azure AD tenant, stores the users, groups, applications, and other information pertaining to an organization and its security. To access the Azure AD tenant, we need an application that is registered with the tenant. Active Roles uses this application, also called the Azure AD application, to communicate to Azure AD tenant after providing the required consent.
The Active Roles Web Interface and Management Shell can be used to perform the Azure AD configuration tasks. The new feature in Active Roles enables you to add or modify existing tenants to the management scope through the web interface and Management Shell.
The latest release of Active Roles supports Multiple tenants model.
NOTE: Administrative users or users with sufficient privileges only can view Azure configuration.
The following section guides you through the Active Roles web interface and Management Shell to configure Azure AD tenants and applications and synchronize existing AD objects to Azure AD.
Use the Active Roles Web Interface and the Active Roles Configuration Center to perform the following actions and configure Azure AD deployments:
When installing Active Roles out-of-the-box, the Directory Management > Tree > Azure node of the Active Roles Web Interface only contains an empty Azure Configuration sub-node by default.
To manage Azure AD directory objects (Azure users, guest users, contacts, O365 groups and Azure Security groups), you must specify an Azure tenant and configure Active Roles as a consented Azure application for it in the Active Roles Configuration Center.
NOTE: If you have already used an Azure tenant (or tenants) in a previous version of Active Roles, you can import and reconfigure them in two ways:
-
If you perform an in-place upgrade of Active Roles (that is, you install the latest version without uninstalling the previous version of Active Roles first in one of the supported upgrade paths), you can reauthenticate the existing Azure tenants with the Upgrade configuration wizard upon launching the Active Roles Configuration Center after installation.
For more information on reauthenticating Azure tenants this way, see Reconfiguring Azure tenants during upgrade configuration in the Active Roles 7.5 Quick Start Guide. For more information on the supported upgrade paths, see Version upgrade compatibility chart in the Active Roles 7.5 Release Notes.
-
If you install a new version of Active Roles to a machine that does not have any earlier versions of the software installed (either because it has been already uninstalled, or it has been installed on another machine), you can import your existing Azure tenant(s) by importing your Azure AD configuration. Following the import, you can reconsent your Azure tenants manually.
For more information on importing existing Azure tenants this way, see Importing an Azure tenant and consenting Active Roles as an Azure application.
Prerequisites
The Active Roles Administration Service must be already running. If the service is not running, then:
-
Open the Active Roles Configuration Center.
-
Navigate to the Administration Service page.
-
Click Start.
TIP: If the Active Roles Administration Service is not running, the Azure AD Configuration page indicates it with an on-screen warning.
To configure a new Azure tenant (or tenants) and set Active Roles as a consented Azure application
-
In the Active Roles Configuration Center, on the left pane, click Azure AD Configuration.
-
From the drop-down list, select the type of domain assigned to the new Azure AD tenant:
-
Non-Federated Domain: When selected, on-premises domains are not registered in Azure AD, and Azure AD Connect is not configured. Azure users and Azure guest users are typically created with the onmicrosoft.com UPN suffix.
-
Federated Domain: On-premises domains are registered in Azure AD and Azure AD Connect. Also, Active Directory Federation Services (ADFS) is configured. Azure users and Azure guest users are typically created with the UPN suffix of the selected on-premises domain.
-
Synchronized Identity Domain: On-premises domains may or may not be registered in Azure AD. Azure AD Connect is configured. Azure users and Azure guest users can be created either with the selected on-premises domain, or with the onmicrosoft.com UPN suffix.
-
To configure a new Azure tenant, click Add.
-
The standard Microsoft Azure Select Account or Sign In pop-up appears. Log in with the user name and password of your Azure AD administrator account.
Upon successful authentication, the new Azure tenant appears in the list.
-
To be able to manage the Azure tenant and its contents in the Active Roles Web Interface, you must consent Active Roles as an Azure application. To do so, click Consent next to the Azure tenant.
-
The standard Microsoft Azure Select Account or Sign In pop-up appears. Log in with the user name and password of your Azure AD administrator account.
-
The standard Microsoft Permissions requested pop-up appears, listing all the permissions required for configuring Active Roles as an Azure application. To finish creating the Azure application, click Accept.
Active Roles then authenticates every Azure AD administrative operation performed in the Azure tenant with a set of generated client ID and client secret.
NOTE: Once you click Accept, Windows may show a Security Warning pop-up with the following message:
The current webpage is trying to open a site on your intranet. Do you want to allow this?
In such cases, clicking either Yes or No could freeze the pop-up dialog, but consenting the Azure tenant will finish without problem.
This issue can occur in case the computer running Active Roles has incorrect browser settings. As a workaround, to get an up-to-date status of the state of the Azure tenant, close and restart the Active Roles Configuration Center after clicking Yes in the Security Warning pop-up.
-
If you have additional Azure tenants to add and consent, configure them as described in the previous steps of this procedure.
-
To make the configured Azure tenant(s) appear in the Active Roles Web Interface, you must restart the Administration Service, as indicated on the user interface. Click Administration Service on the left pane, then either click Restart, or first click Stop and then Start.
TIP: Once the Azure tenant or tenants are configured, and Active Roles is also set as a consented Azure AD application for it, you can view and modify the configured tenant(s) and their settings at the following locations:
-
To change the domain type or OneDrive provisioning settings of an Azure tenant, in the Active Roles Configuration Center, navigate to Azure AD Configuration, select the Azure tenant, and click Modify. For more information, see Viewing or modifying the Azure AD tenant type.
-
To check the connectivity status of the Azure configuration, in the Active Roles Web Interface, navigate to Directory Management > Tree > Azure > Azure Configuration > Azure Health Check. For more information, see View Azure Health for Azure AD tenants and applications .
-
To check the Azure Licenses Report, in the Active Roles Web Interface, navigate to Directory Management > Tree > Azure > Azure Configuration > Azure Licenses Report. For more information, see View Azure Licenses Report .
-
To check the Office 365 Roles Report, in the Active Roles Web Interface, navigate to Directory Management > Tree > Azure > Azure Configuration > Office 365 Roles Report. For more information, see View Office 365 Roles Report .
NOTE: Consider the following when configuring an Azure tenant:
-
When Active Roles is registered as a consented Azure AD application, minimal permissions are assigned to it by default. To add additional permissions to the Azure application, sign in to the Azure Portal and add your required permissions there.
-
Azure Multi-Factor Authentication (MFA) is automatically enforced for Azure users and Azure guest users added to the configured Azure tenant. To disable Azure MFA for the Azure tenant, sign in to the Azure Portal and navigate to Tenant > Properties > Manage Security defaults and set Enable Security defaults to No.
