Chat now with support
Chat mit Support

Active Roles 7.5.3 - Administration Guide

Introduction About Active Roles 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
About Policy Objects Policy Object management tasks Policy configuration tasks
Property Generation and Validation User Logon Name Generation Group Membership AutoProvisioning E-mail Alias Generation Exchange Mailbox AutoProvisioning AutoProvisioning for SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Office 365 and Azure Tenant Selection 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
Workflows
Understanding workflow Workflow activities overview Configuring a workflow
Creating a workflow definition Configuring workflow start conditions Configuring workflow parameters Adding activities to a workflow Configuring 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
Example: Approval workflow E-mail based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic Groups Active Roles Reporting Management History
Understanding Management History Management History configuration Viewing change history
Workflow activity report sections Policy report items Active Roles internal policy report items
Examining user activity
Entitlement Profile Recycle Bin AD LDS Data Management One Identity Starling Management One Identity Starling Two-factor Authentication for Active Roles Managing One Identity Starling Connect Azure AD, Office 365, and Exchange Online management
Configuring Active Roles to manage hybrid AD objects Managing Hybrid AD Users Unified provisioning policy for Azure O365 Tenant Selection, Office 365 License Selection, and Office 365 Roles Selection, and OneDrive provisioning Office 365 roles management for hybrid environment users Managing Office 365 Contacts Managing Hybrid AD Groups Managing Office 365 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 Configuration of Active Roles
Connecting to the Administration Service Adding and removing 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 Appendix A: Using regular expressions Appendix B: Administrative Template Appendix C: Communication ports Appendix D: Active Roles and supported Azure environments Appendix E: Enabling Federated Authentication Appendix F: Active Roles integration with other One Identity and Quest products Appendix G: Active Roles integration with Duo Appendix H: Active Roles integration with Okta

Configuring gMSA as an Active Roles Service account

Active Roles Configuration Center enables you to configure the gMSA account as a service account . Before you configure a gMSA account as an Active Roles Service account, the following pre-requisites must be met:

  • The Key Distribution Services (KDS) Root Key must be available in the KDS service on the Domain controller.
  • The computers and groups that have servers with Active Roles Service installed on them, must be added to the gMSA account.
  • The gMSA account must be available in the Local Administrators group where the Active Roles service is installed and in the built-in Administrators group of the domain.
  • The gMSA account must have an SQL login with db_Owner permission for Active Roles database.
  • The gMSA account name must be unique across domains.

NOTE: Exchange operations cannot be performed on the on-premises Exchange Server environment using the gMSA account. For example, Remote mailbox, User mailbox, or Contact.

For information on creating a new database see Configuring the Active Roles Service account to use a gMSA account.

For more information on managing gMSA accounts see Management of Group Managed Service Accounts in the Active Roles User’s Guide.

Configuring the Active Roles Service account to use a gMSA account

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 account 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 detailed instructions, 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 box, click Object Types.
  5. In the Object Types dialog box, select the Service Accounts object type along with the Users object type and click OK. 
  6. In the Service User or Service Account dialog box, click Check Names to select the required gMSA account, and click OK.

    The Configure Administration Service dialog box displays the new login name for the gMSA account. 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 account, then an error is displayed prompting you to check if the system is permitted to use the provided gMSA.

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

  8. If all the pre-requisites 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 use the same database.

    NOTE: When you create a new database, you can add the DB_owner permission to gMSA account 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 Administrative 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 complete 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 account

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

To change the Administration Service account to use a gMSA account 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 detailed instructions, 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 box, under Service Account, click Browse.
  4. In the Select User or Service Account dialog box, click Object Types.
  5. In the Object Types dialog box, select the Service Accounts object type along with the Users object type and click OK. 
  6. In the Service User or Service Account dialog box, click Check Names to select the required gMSA account, and click OK.

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

  7. Click Change to complete the changes to the service account.

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

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

    If all the pre-requisites are met, the service account is changed to GMSA account successfully and the success message is displayed.

Changing the Active Roles Admin account

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.

  1. In the Configuration Center main window, under Administration Service, click Manage Settings.
  2. On the Administration Service page, in the Active Roles Admin area, click Change.
  3. 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.

  1. Click the Change button on the Active Roles Admin page.

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.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen