Chat now with support
Chat with Support

Active Roles 8.0 LTS - 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 Managing One Identity Starling Connect Configuring linked mailboxes with Exchange Resource Forest Management Configuring remote mailboxes for on-premises users 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 Microsoft 365 Groups Managing Azure Security Groups Managing cloud-only distribution 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
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: Active Roles integration with other One Identity and Quest products Appendix F: Active Roles integration with Duo Appendix G: Active Roles integration with Okta Active Roles Language Pack

Deleting a shared mailbox

You can delete a shared mailbox in the selected Azure tenant with the Delete option of the Active Roles Web Interface.

To delete a shared mailbox

  1. Navigate to Directory Management > Tree > Azure > <azure-tenant-name> > Shared Mailboxes.

    Figure 212: Directory Management > Tree > Azure > <azure-tenant-name> > Shared Mailboxes — Listing the shared mailboxes in the tenant

  2. Select the shared mailbox that you want to delete.

  3. Click Delete.

  4. To confirm, click Yes.

Managing Configuration of Active Roles

This chapter covers the following management activities:

To manage the configuration of Active Roles, you must have the necessary permissions. It is sufficient to be a member of the Active Roles Admin account. The Active Roles Admin account is specified when configuring the Administration Service. It defaults to the Administrators group on the computer running the Administration Service.

The authority to modify the Active Roles configuration can be delegated by applying the Manage Configuration Access Template to the Server Configuration container.

Connecting to the Administration Service

To configure a particular Administration Service using the Active Roles console, you need to manually specify the Administration Service to connect to. Otherwise, the console automatically selects the Administration Service.

You can use the Connect to Administration Service dialog box to select the appropriate Administration Service. To display this dialog box, right-click Active Roles in the console tree and click Connect. The dialog box looks as shown in the following figure.

Figure 213: Connect to Administration Service

In the Service box, type or select the name of the computer running the Administration Service to connect to, and then click Connect. The Service box provides a list of names that were specified for previous connection sessions. The last selected name is displayed by default.

To select the Administration Service that is not in the list, click the Select button next to the Service box:

This displays the Select Administration Service dialog box, shown in the following figure.

Figure 214: Select Administration Service

The Select Administration Service dialog box lists the Administration Services that are available in the specified forest. You can choose a different forest by clicking Change. The list items are sorted according to priority, considering site location and service load (less loaded Administration Services are displayed at the top of the list). To add a certain Service to the Connect to Administration Service dialog box, click that Service and then click OK.

If you have connected to a specific Service, the console will attempt to automatically connect to that Service on every subsequent start. If you have selected <Any available Administration Service>, the console will attempt to connect to the nearest, least loaded Service in the specified forest, giving preference to the Services that belong to the same replication group as the Service to which the console was connected in the previous session.

By default, the console connects to the Administration Service in the security context of your logon account (that is, the user account to which you have logged on). This means that you can only use the console to perform the tasks that are delegated to your user account. You have the option to establish a connection using a different account, in order to change the scope of the allowed tasks. Click Options to expand the Connect to Administration Service dialog box, as shown in the following figure.

Figure 215: Connect to Administration Service

Click The following user and specify the user logon name and password of the account to be used for connection. By selecting the Remember password check box you can have the console automatically use the specified user name and password in the future connection sessions. Otherwise, on a subsequent start, the console will prompt you for a password.

Delegating control to users for accessing MMC interface

By default, on installing Active Roles, all users are allowed to log in to the MMC interface. To manage the MMC interface access for a user, you must configure the options using Configuration Center | MMC Interface Access| Manage settings. Selecting this option restricts all non Active Roles Administrators from using the console. All delegated users are affected, however, it does not apply to Active Roles Administrators.

To be able to log in to the MMC interface, the user must be delegated with the User Interfaces access rights on the User Interfaces container under Server Configuration. User Interfaces Access templates that provide the access rights are available as part of the Active Roles built-in Access templates in the User Interfaces container.

To delegate the control to users in the User Interfaces container you must apply the User Interface Access Template

  1. In the console tree, expand Active Roles | Configuration | Server Configuration.
  2. Under Server Configuration, locate the User Interfaces container, right-click it, and click Delegate Control.

  3. On the Users or Groups page, click Add, and then select the users or groups to which you want to delegate the control. Click Next.

  4. On the Access Templates page, expand the Active Directory | User Interfaces folder, and select the check box next to User Interface Management-MMC Full control.
  5. Click Next and follow the instructions in the wizard, accepting the default settings.

  6. After you complete these steps, the users and groups you selected in Step 3 are authorized to log in to the MMC interface.

  7. Click OK to close the Active Roles Security dialog box.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating