Chat now with support
Chat with Support

Active Roles 7.4.1 - 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 License Management Office 365 Roles Management 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_Overview
Config ARS to Manage Hybrid AD Objects Managing Hybrid AD Users Office 365 roles management for hybrid environment users Managing Office 365 Contacts Managing Hybrid AD Groups Managing Azure O365 or Unified Groups
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 delegation for Federated Authentication

Replication Agent schedule

By default, Active Roles schedules the Replication Agents to run as follows:

  • The Snapshot Agent starts every day at 12:00 a.m. at the Publisher.
  • The Merge Agents start automatically when SQL Server Agent starts, and runs continuously at the Publisher.

To verify the Snapshot Agent schedule

  1. Open SQL Server Management Studio.
  2. In Object Explorer, connect to the instance of the SQL Server Database Engine that holds the Publisher role, and then expand that instance.
  3. Right-click the Replication folder, and click Launch Replication Monitor.
  4. In the left pane of the Replication Monitor window, expand your Publisher SQL Server, and click AelitaReplica.
  5. In the right pane of the Replication Monitor window, on the Warnings and Agents tab, right-click the Snapshot Agent in the Agents and jobs related to this publication list, and click Properties.
  6. In the left pane of the Job Properties window, click Schedules.
  7. Review the replication agent schedule settings in the right pane of the Job Properties window.
  8. Click the Edit button to examine the replication agent schedule settings in detail.

To verify the Merge Agent schedule

  1. Open SQL Server Management Studio.
  2. In Object Explorer, connect to the instance of the SQL Server Database Engine that holds the Publisher role, and then expand that instance.
  3. Right-click the Replication folder, and click Launch Replication Monitor.
  4. In the left pane of the Replication Monitor window, expand your Publisher SQL Server, and click AelitaReplica.
  5. In the right pane of the Replication Monitor window, on the All Subscriptions tab, right-click the subscription whose Merge Agent you want to examine, and click View Details.
  6. In the Subscription window, on the Action menu, click Merge Agent Job Properties.
  7. In the left pane of the Job Properties window, click Schedules.
  8. Review the replication agent schedule settings in the right pane of the Job Properties window.
  9. Click the Edit button to examine the replication agent schedule settings in detail.

Monitoring replication

In order to identify replication-related problems, you can use the Active Roles console connected to the Publisher Administration Service. If there are any replication failures, a red triangle is displayed on the Server Configuration and Configuration Databases containers in the console tree. In the details pane, the same icon is used to highlight the database affected by a replication failure.

If you have encountered a replication failure, you should ensure that the SQL Server Agent service is started on the computer running the Publisher SQL Server, and then use SQL Server Management Studio to get more information on that failure:

  1. In Object Explorer, connect to the instance of the SQL Server Database Engine that holds the Publisher role, and then expand that instance.
  2. Right-click the Replication folder, and click Launch Replication Monitor.
  3. In the left pane of the Replication Monitor window, expand your Publisher SQL Server, and click AelitaReplica.
  4. In the right pane of the Replication Monitor window, on the Warnings and Agents tab, look for a red icon under Agents and jobs related to this publication. This icon indicates a Snapshot Agent error:
  5. Right-click the agent that has encountered an error and then click View Details.
  6. In the Snapshot Agent window, view the error description under Error details or message of the selected session.
  7. In the right pane of the Replication Monitor window, on the All Subscriptions tab, look for a red icon in the list of subscriptions. This icon indicates a Merge Agent error:
  8. On the All Subscriptions tab, right-click the subscription that has encountered an error and then click View Details.
  9. In the Subscription window, view the error description under Last message of the selected session.

Some typical errors are discussed later in this document (see the Troubleshooting Replication failures section). The Troubleshooting Replication failures section also provides information on how to resolve such errors.

Viewing database connection settings

The most common reasons for replication problems are access failures that Replication Agents encounter when attempting to connect to the Publisher or Subscriber SQL Server. Given that security credentials of Replication Agents depend on authentication mode of the Administration Service, you may need to examine Administration Service database connection settings in order to see which mode is actually used—Windows authentication or SQL Server authentication.

You can view connection settings in the Active Roles console:

  1. In the console tree, select Configuration | Server Configuration | Administration Services.
  2. In the details pane, right-click the Administration Service you want to examine, and click Properties.
  3. In the Properties dialog box, go to the Configuration Database tab.

The Configuration Database tab displays the following information:

  • SQL Server  Identifies the SQL Server instance used by the Administration Service.
  • Database  The name of the Administration Service database.
  • Use Windows authentication  When selected, indicates that the Administration Service uses Windows authentication mode when connecting to SQL Server.
  • Use SQL Server authentication  When selected, indicates that the Administration Service uses SQL Server authentication mode when connecting to SQL Server.
  • Login name  The name of the SQL Server login that the Administration Service uses to access SQL Server; only applies to the Use SQL Server authentication option.

Modifying database connection settings

You may need to modify Administration Service database connection settings if the login of the Administration Service for SQL Server authentication is no longer valid, or has the password changed. If you change the login, you also need to change it for Replication Agents, as described in the Modifying Replication Agent credentials section later in this document.

You can modify connection settings by using Active Roles Configuration Center:

  1. Start Configuration Center on the computer running the Administration Service, or connect Configuration Center to that computer.

You can start Configuration Center by selecting Active Roles 7.4 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” in the Active Roles Administrator Guide.

  1. On the Dashboard page in the Configuration Center main window, click Manage Settings in the Administration Service area.
  2. On the Administration Service page that opens, click Change in the Active Roles database area.
  3. Use the Change Active Roles Database wizard that appears to view or change the login or password of the Administration Service for SQL Server authentication: Type the appropriate login name and password in the fields under the SQL Server authentication option on the Connection to Database page.
Related Documents