Chat now with support
Chat with Support

Active Roles 8.1.1 - Administration Guide

Introduction Getting started Rule-based administrative views Role-based administration
Access Templates as administrative roles Access Template management tasks Examples of use Deployment considerations Windows claims-based access rules
Rule-based autoprovisioning and deprovisioning
Provisioning Policy Objects Deprovisioning Policy Objects How Policy Objects work Policy Object management tasks Policy configuration tasks
Property Generation and Validation User Logon Name Generation Group Membership AutoProvisioning Exchange Mailbox AutoProvisioning AutoProvisioning in SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Microsoft 365 and Azure Tenant Selection E-mail Alias Generation User Account Deprovisioning Office 365 Licenses Retention Group Membership Removal Exchange Mailbox Deprovisioning Home Folder Deprovisioning User Account Relocation User Account Permanent Deletion Group Object Deprovisioning Group Object Relocation Group Object Permanent Deletion Notification Distribution Report Distribution
Deployment considerations Checking for policy compliance Deprovisioning users or groups Restoring deprovisioned users or groups Container Deletion Prevention policy Picture management rules Policy extensions
Using rule-based and role-based tools for granular administration Workflows
Key workflow features and definitions About workflow processes Workflow processing overview Workflow activities overview Configuring a workflow
Creating a workflow definition for a workflow Configuring workflow start conditions Configuring workflow parameters Adding activities to a workflow Configure an Approval activity Configuring a Notification activity Configuring a Script activity Configuring an If-Else activity Configuring a Stop/Break activity Configuring an Add Report Section activity Configuring a Search activity Configuring CRUD activities Configuring a Save Object Properties activity Configuring a Modify Requested Changes activity Enabling or disabling an activity Enabling or disabling a workflow Using the initialization script
Approval workflow Email-based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic groups Active Roles Reporting Management History Entitlement profile Recycle Bin AD LDS data management One Identity Starling Join and configuration through Active Roles Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users Azure AD, Microsoft 365, and Exchange Online Management
Configuring Active Roles to manage Hybrid AD objects Managing Hybrid AD users
Creating a new Azure AD user with the Web Interface Viewing or updating the Azure AD user properties with the Web Interface Viewing or modifying the manager of a hybrid Azure user Disabling an Azure AD user Enabling an Azure AD user Deprovisioning of an Azure AD user Undo deprovisioning of an Azure AD user Adding an Azure AD user to a group Removing an Azure AD user from a group View the change history and user activity for an Azure AD user Deleting an Azure AD user with the Web Interface Creating a new hybrid Azure user with the Active Roles Web Interface Converting an on-premises user with an Exchange mailbox to a hybrid Azure user Licensing a hybrid Azure user for an Exchange Online mailbox Viewing or modifying the Exchange Online properties of a hybrid Azure user Creating a new Azure AD user with Management Shell Updating the Azure AD user properties with the Management Shell Viewing the Azure AD user properties with the Management Shell Delete an Azure AD user with the Management Shell Assigning Microsoft 365 licenses to new hybrid users Assigning Microsoft 365 licenses to existing hybrid users Modifying or removing Microsoft 365 licenses assigned to hybrid users Updating Microsoft 365 licenses display names
Unified provisioning policy for Azure M365 Tenant Selection, Microsoft 365 License Selection, Microsoft 365 Roles Selection, and OneDrive provisioning Microsoft 365 roles management for hybrid environment users Managing Microsoft 365 contacts Managing Hybrid AD groups Managing Microsoft 365 Groups Managing cloud-only distribution groups Managing cloud-only dynamic distribution groups Managing Azure security groups Managing cloud-only Azure users Managing cloud-only Azure guest users Managing cloud-only Azure contacts Changes to Active Roles policies for cloud-only Azure objects Managing room mailboxes Managing cloud-only shared mailboxes
Modern Authentication Managing the configuration of Active Roles
Connecting to the Administration Service Managed domains Using unmanaged domains Evaluating product usage Creating and using virtual attributes Examining client sessions Monitoring performance Customizing the Console Using Configuration Center Changing the Active Roles Admin account Enabling or disabling diagnostic logs Active Roles Log Viewer
SQL Server replication Using regular expressions Administrative Template Communication ports Active Roles and supported Azure environments Integrating Active Roles with other products and services Active Roles Language Pack Active Roles Diagnostic Tools Active Roles Add-on Manager

Configuring the Active Roles Service account to use a gMSA

After completion of Active Roles Setup, the Configuration Center enables you to create an instance of the Administration Service to get the Administration Service ready for use.

To configure the Administration Service account to use a gMSA as the service account during initial configuration

  1. Start Configuration Center on the computer running the Administration Service.

    You can start Configuration Center by selecting Configuration Center on the Apps page or Start menu, depending upon the version of your Windows operating system. For more information, see Running Configuration Center.

  2. In the Configuration Center main window, under Administration Service, click Configure.

  3. On the Administration Service page, in the Service Account area, click Browse.

  4. In the Select User or Service Account dialog, click Object Types.

  5. In the Object Types dialog, select the Service Accounts object type along with the Users object type and click OK.

  6. In the Service User or Service Account dialog, click Check Names to select the required gMSA, and click OK.

    The Configure Administration Service dialog displays the new login name for the gMSA. The Password field is disabled.

  7. Click Next to complete the service account configuration.

    If the system running the Active Roles Service is not linked to the gMSA, then an error is displayed prompting you to check if the system is permitted to use the provided gMSA.

    If the gMSA is not part of the Local Administrators group, then an error is displayed prompting you to check if the gMSA is a member of the Local Administrators group on the system.

  8. If all the prerequisites are met, you can proceed to the next step. Provide the name of the group or user account that will have full access to all Active Roles features and functions through this Administration Service instance (Active Roles Admin). Click Next.

  9. Provide the details for the database in which this Administration Service instance will store the configuration data and management history data.

    You have the option to create a new database or use an existing database of the current Active Roles version. It is possible to have multiple Administration Service instances that use the same database.

    NOTE: When you create a new database, you can add the DB_owner permission to the gMSA for the new database only after the Administration Service is configured.

    Based on the authentication mode that the Administration Service instance uses when connecting to the database, the Administration Service uses the relevant credentials:

    • With the Windows authentication option, the Administration Service will use the credentials of the service account.

    • With the SQL Server authentication option, the Administration Service will use the SQL login name and password you supply in the wizard.

  10. After all steps are complete, review the settings on the Ready to Configure summary page and click Configure to save the configuration.

The Active Roles Admin setting is specific to the instance of the Administration Service. If you have multiple Administration Service instances deployed in your environment, then you need to apply the changes on each computer running the Administration Service.

Changing the Active Roles Service account to use a gMSA

Active Roles provides support to change an Active Roles account to use a gMSA.

To change the Administration Service account to use a gMSA as the service account

  1. Start Configuration Center on the computer running the Administration Service.

    You can start Configuration Center by selecting Configuration Center on the Apps page or Start menu, depending upon the version of your Windows operating system. For more information, see Running Configuration Center.

  2. In the Configuration Center main window, under Administration Service > Service account, click Change.

  3. In the Change Service Account dialog, under Service Account, click Browse.

  4. In the Select User or Service Account dialog, click Object Types.

  5. In the Object Types dialog, select the Service Accounts object type along with the Users object type and click OK.

  6. In the Service User or Service Account dialog, click Check Names to select the required gMSA, and click OK.

    The Change Service Account dialog displays the new login name for the gMSA. The Password field is disabled.

  7. Click Change to save the changes for the service account.

    If the system that is running the Active Roles Service is not linked to the gMSA, then an error is displayed prompting you to check if the system is permitted to use the provided gMSA.

    If the gMSA is not part of the Local Administrators group, then an error is displayed prompting you to check if the gMSA is a member of the Local Administrators group on the system.

    If all the prerequisites are met, the service account is changed to gMSA successfully and the success message is displayed.

Changing the Active Roles Admin account

When you configure the Active Roles Administration Service, you are prompted to specify the group or user account that will have unrestricted access to all Active Roles features and functions. This account is referred to as Active Roles Admin. By default, Active Roles Admin is the Administrators local group on the computer running the Administration Service. You can change this setting in the Configure Administration Service wizard when initially configuring the Administration Service.

After you have configured the Administration Service, you can choose a different Active Roles Admin account by using Active Roles Configuration Center on the computer running the Administration Service.

To change the Active Roles Admin Account

  1. Start Configuration Center on the computer running the Administration Service.

    You can start Configuration Center by selecting Configuration Center on the Apps page or Start menu, depending upon the version of your Windows operating system. For detailed instructions, see Running Configuration Center.

  2. In the Configuration Center main window, under Administration Service, click Manage Settings.

  3. On the Administration Service page, in the Active Roles Admin area, click Change.

  4. On the Active Roles Admin page in the Change Active Roles Admin wizard that appears, click Browse and select the group or user account you want to be designated as Active Roles Admin.

    If you select a group, any member of that group will have the Active Roles Admin rights. If you select a user account, then only that account will have the Active Roles Admin rights.

  5. Click Change on the Active Roles Admin page.

NOTE: The Active Roles Admin setting is specific to the instance of the Administration Service. If you have multiple Administration Service instances deployed in your environment, then you need to apply the changes on each computer running the Administration Service.

Enabling or disabling diagnostic logs

Active Roles administrators can enable diagnostic logging at the request of support personnel to assist them in finding root causes of issues that occur during Active Roles operations. The diagnostic information includes the Active Roles configuration statistics (referred to as Active Roles system summary), the Active Roles Administration Service diagnostic log and the Active Roles Console diagnostic log.

The Active Roles Administration Service’s diagnostic log (ds.log) contains tracing information, such as API calls, internal function calls and state transitions performed by the Administration Service. This information is stored in the ds.log file that you can send to the support team for issue diagnostic purposes. Two logging levels are available: Basic and Verbose. The Verbose option writes much more information to the log, which can aid in the process of isolating an issue. However, with the increase in verbosity comes a corresponding decrease in performance and increase in the size of the log file.

The Active Roles Console’s diagnostic log (EDMSnap.txt) contains debugging information specific to the Active Roles Console, this can be helpful in isolating Console-related issues.

You can use the Active Roles Console to perform the following tasks:

  • Export Active Roles system summary.

    This option allows you to save the Active Roles configuration statistics to a file that you can later send to the support team for diagnosing the issue.

  • Turn the Administration Service’s diagnostic log on or off.

    The Console shows the path to the log file located on the computer running the Administration Service.

  • Choose the level of verbosity for the Administration Service: Basic or Verbose.

    The Verbose option results in a more detailed log, but considerably increases the size of the log file.

  • Turn the Console’s diagnostic log on or off.

    The Console shows the path to the Console’s log file on the local computer.

It is also possible to enable or disable diagnostic logs by using Configuration Center (see Logging management tasks). The following instructions apply to the Active Roles Console.

To view or change the diagnostic settings

  1. Log on as an Active Roles Admin, and open the Active Roles Console.

  2. In the Active Roles Console tree, click the root node to display the Active Roles summary page in the details pane.

  3. On the summary page, expand the Diagnostics area.

    In the Diagnostics area, you can view whether the Active Roles Administration Service’s diagnostic logging is currently enabled (turned on) or disabled (turned off).

  4. In the Diagnostics area, click View or change diagnostic settings.

    This opens the Diagnostics page in the Properties dialog for the Administration Service instance to which the Console is currently connected. Another way to open that page is by directly opening the Properties dialog from the Administration Service object in the Configuration/Server Configuration/Administration Service container.

  5. Use the Diagnostics page to perform the following tasks:

    • To turn the Administration Service’s log on or off, click the appropriate option. This option enables or disables the Administration Service diagnostic logging on the computer running the Administration Service instance to which the console is currently connected.

    • Choose the level of verbosity from the Logging level list, if you have selected the option to turn on the Administration Service’s log.

    • View the path and name of the Administration Service’s log file, along with the name of the computer that holds the log file.

    • Click the appropriate option to turn on or off the Console’s log. This option enables or disables the console diagnostic logging on the local computer.

    • View the path and name of the Console’s log file, along with the name of the computer that holds the log file.

  6. Click Export Active Roles system summary to save the Active Roles configuration statistics to a file that you can later send to the support team for diagnosing the issue.

  7. When finished, click OK or Apply for your changes to take effect.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating