Chatta subito con l'assistenza
Chat con il supporto

Active Roles 8.2 - Administration Guide

Introduction Getting started with Active Roles Configuring rule-based administrative views Configuring role-based administration Configuring rule-based autoprovisioning and deprovisioning
Configuring Provisioning Policy Objects
User Logon Name Generation E-mail Alias Generation Exchange Mailbox AutoProvisioning Group Membership AutoProvisioning Home Folder AutoProvisioning Property Generation and Validation Script Execution O365 and Azure Tenant Selection AutoProvisioning in SaaS products
Configuring Deprovisioning Policy Objects
User Account Deprovisioning Group Membership Removal User Account Relocation Exchange Mailbox Deprovisioning Home Folder Deprovisioning User Account Permanent Deletion Office 365 Licenses Retention Group Object Deprovisioning Group Object Relocation Group Object Permanent Deletion Script Execution Notification Distribution Report Distribution
Configuring entry types Configuring a Container Deletion Prevention policy Configuring picture management rules Managing Policy Objects Checking for policy compliance Deprovisioning users or groups Restoring deprovisioned users or groups Configuring policy extensions
Using rule-based and role-based tools for granular administration Workflows
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 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
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 Migrating Active Roles configuration with the Configuration Transfer Wizard Managing Skype for Business Server with Active Roles
About Skype for Business Server User Management Active Directory topologies supported by Skype for Business Server User Management User Management policy for Skype for Business Server User Management Master Account Management policy for Skype for Business Server User Management Access Templates for Skype for Business Server Configuring the Skype for Business Server User Management feature Managing Skype for Business Server users
Exchanging provisioning information with Active Roles SPML Provider Monitoring Active Roles with Management Pack for SCOM Configuring Active Roles for AWS Managed Microsoft AD Azure AD, Microsoft 365, and Exchange Online Management
Azure tenant types and environment types supported by Active Roles Using Active Roles to manage Azure AD objects Unified provisioning policy for Azure M365 Tenant Selection, Microsoft 365 License Selection, Microsoft 365 Roles Selection, and OneDrive provisioning Changes to Active Roles policies for cloud-only Azure objects
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 Configuring federated authentication Communication ports and URLs used by Active Roles Integrating Active Roles with other products and services Active Roles Language Pack Active Roles Diagnostic Tools Active Roles Add-on Manager

Joining the EC2 instance to AWS Managed Microsoft AD

After you created your AWS Managed Microsoft AD service and your EC2 instance(s), you must join the configured Amazon Elastic Compute Cloud (EC2) instance(s) to AWS Managed Microsoft AD.

Complete the procedure in Amazon Web Services (AWS) as described in Join an EC2 instance to your AWS Managed Microsoft AD directory in the AWS Directory Service documentation.

NOTE: Consider the following when joining the EC2 instance(s) to AWS Managed Microsoft AD:

TIP: If the domain join process ends with an error, check the specified DNS addresses and Domain Admin credentials in the AWS console.

Creating the RDS instance for the Active Roles SQL Server

If you manage AWS Managed Microsoft AD with Active Roles in Amazon Web Services (AWS), you must store the Active Roles Management History and Configuration databases in an Amazon Relational Database Service (RDS) instance.

Configure the RDS instance in AWS as described in Setting up for Amazon RDS in the Amazon RDS documentation.

NOTE: Consider the following when creating the EC2 instance:

  • Make sure that the connectivity requirements listed in Deployment requirements for AWS Managed Microsoft AD support are met.

  • Select the SQL Server edition that suits your needs the most. For most Active Roles use cases, SQL Server Standard Edition is an optimal choice.

  • Take note of the Master username and Master password, as these credentials will be required later.

  • For Storage type, select General Purpose SSD (gp2), and allocate a minimum storage of 60 GiB.

  • Consider selecting Enable storage autoscaling. Selecting this setting is useful if the SQL Server is utilized with a heavy load most of the time, but it might incur additional operational costs.

  • For Certificate authority, select the rds-ca-2019 certificate, as it is required for Microsoft OLE DB Driver 19 for SQL Server to function properly.

Verifying connectivity between the EC2 and RDS instances

After you created the RDS instance, you can test in the EC2 instance with the telnet client or Microsoft SQL Server Management Studio (SSMS) if the RDS connectivity was successfully configured.

To verify RDS connectivity in the EC2 instance

  1. Log in to the EC2 instance created for Active Roles.

  2. To test connectivity to RDS, install the telnet client. To do so:

    1. Open Windows Server Manager.

    2. On the Dashboard, click Add roles and features.

    3. In Installation Type, select Role-based or feature-based installation, then click Next.

    4. In Server Selection, choose Select a server from the server pool, and make sure that the local server (the EC2 instance) is selected.

    5. In Server Roles, just click Next.

    6. In Features, select Telnet Client.

    7. In Confirmation, click Install, then Close the application.

  3. To verify connectivity to the RDS instance, open the Windows Command Prompt, and run the following command:

    telnet <rds-server-endpoint> <port-number>

    To find the RDS server endpoint and port to specify, open the entry of the RDS instance in the AWS console, and check the values under Connectivity & Security > Endpoint & port.

    NOTE: If the command returns an empty prompt, that indicates connectivity between the EC2 instance and the RDS instance.

  4. Download and install Microsoft SQL Server Management Studio (SSMS) on the EC2 instance.

  5. To test the connection with SSMS, start the application, then in the Connect to Server dialog, specify the following attributes:

    • Server type: Select Database Engine.

    • Server name: The same RDS instance endpoint used in the telnet command.

    • Authentication: Select SQL Server Authentication, then specify the admin user name and password created when configuring the RDS instance.

  6. After you specified all connection properties, click Connect.

Installing and configuring Active Roles on the EC2 instance

After you checked the connectivity between the EC2 and RDS instances, you can deploy and configure Active Roles on the EC2 instance.

Prerequisites

Before starting the procedure, make sure that the following requirements are met:

To install Active Roles on the EC2 instance

  1. Download the Active Roles installation media to the EC2 instance.

  2. Run the setup and install Active Roles with all required prerequisites as described in Installing Active Roles in the Active Roles Installation Guide.

    NOTE: Starting from Active Roles 8.2, make sure that you install Microsoft OLE DB Driver 19 for SQL Server and all its prerequisites from the Redistributables folder of the installation media.

    Also, to make sure that the connection to the SQL Server is properly encrypted, download and install the latest AWS RDS Root Certificate by adding it to the Trusted Root Certification Authorities container of the certmgr (Manage User Certificates) utility. For more information, see Using SSL/TLS to encrypt a connection to a DB instance in the Amazon RDS documentation.

After installing Active Roles, configure the Active Roles Administration Service.

To configure Active Roles Administration Service for managing AWS Managed Microsoft AD in SQL Server Management Studio

  1. Start Microsoft SQL Server Management Studio (SSMS) and connect to the RDS for SQL Server instance as described in Verifying connectivity between the EC2 and RDS instances.

  2. Under the Databases node of the Object Explorer, create two new empty databases to be used later for configuring Active Roles:

    • A database for the Management History database. Name it, for example, ARMH.

    • A database for the Active Roles Configuration database. Name it, for example, ARConfig.

  3. Create a new user that Active Roles will use to connect to the SQL database in the RDS instance. To do so, right-click the Security > Logins node of the Object Explorer, then select New login and specify the following details:

    1. Under General > Login name, enter the name of the user (for example, sql-activeroles). Then, select SQL Server authentication.

    2. Under User Mapping, select the databases that you created (in this example, ARMH and ARConfig), and assign the db_owner role to both of them.

To configure Active Roles Administration Service for managing AWS Managed Microsoft AD in Active Roles Configuration Center

  1. Start the Active Roles Configuration Center.

  2. On the Dashboard, under Administration Service, click Configure.

  3. In Service Account, enter the user name and password of the Active Roles Service account. This can be, for example, the domain admin account supplied by Amazon Web Services (AWS).

  4. In Active Roles Admin, specify the security group or administrator user in the EC2 instance who will hold Active Roles Admin permissions.

  5. In Configuration Database Options, select New Active Roles database and Use a pre-created blank database.

  6. In Connection to Configuration Database, configure the following settings:

    • Database type: Select On Premise. In the context of Active Roles, the Amazon RDS for SQL Server instance functions like an on-premises SQL Server.

    • Database Server name: Specify the endpoint URL of the RDS instance. This is the same endpoint you specified during Verifying connectivity between the EC2 and RDS instances.

    • Database name: Specify the name of the blank database that you created as the Active Roles Configuration database (in this example, ARConfig).

    • Connect using: Select SQL Server authentication, and enter the user name and password of the user created as the owner of the database.

  7. In Management History Database Options, select New Active Roles database and Use a pre-created blank database.

  8. In Connection to Management History Database, specify the same Database type, Database Server name and connection settings that you set for the Configuration database. However, for Database name, enter the name of the blank database that you created for use as the Active Roles Management History database (in this example, ARMH).

  9. In Encryption Key Backup, specify the file name and save location of the Active Roles database encryption key.

  10. (Optional) Still in Encryption Key Backup, specify a password for additional protection. To continue, click Next.

  11. Review your settings. Then, to apply your changes, click Configure.

After you configured the Active Roles Administration Service, you can also configure the Active Roles Console to manage your AWS Managed Microsoft AD instance.

To configure Active Roles Console for managing AWS Managed Microsoft AD

  1. Start the Active Roles Console.

  2. Due to limitations with Service Connection Points (SCPs) in the Amazon cloud, Active Roles Console is likely unable to automatically discover the Administration Service instance you configured previously.

    To manually connect to the Administration Service, in the Connect to Administration Service dialog, under Service, specify localhost. Under Connect as, select Current user, then click Connect.

    NOTE: If you cannot connect to the Administration Service by specifying localhost, then specify the full Device name as indicated in the Settings > About page of the operating system.

  3. After you connected, in the Active Roles Console landing page, click Add Domain.

  4. In the Add Managed Domain Wizard, in Domain Selection, click Browse and select the domain configured by AWS for the EC2 instance.

  5. In Active Roles Credentials, select The service account information the Administration Service uses to log on.

  6. To finish adding the domain, click Next, then Finish.

  7. To make sure that the contents of the AWS Managed Microsoft AD domain appear in the Active Roles Console, click Refresh or right-click the Active Roles node, then click Reconnect.

    NOTE: The connected AWS Managed Microsoft AD environment will contain several built-in and AWS-specific containers with read-only access. You can create and manage AD objects only in the Organizational Unit whose name matches the shortname of the connected domain's name (specified during Creating the AWS Managed Microsoft AD instance).

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione