Lithnet AutoSync for Microsoft Identity Manager
Documentation Home
  • Home
  • installation
    • Prerequisites
    • Installing AutoSync
    • Configuring the AutoSync service
    • Management agent configuration
    • Settings
  • Configuration
    • Triggers
      • Active Directory change detection trigger
      • MIM service change detection trigger
      • Repeating interval trigger
      • Scheduled interval trigger
      • Powershell script trigger
      • Powershell script trigger gallery
    • Settings
      • Run history settings
      • Mail settings
      • Advanced settings
    • Execution-controller-scripts
  • help and support
    • Frequently asked questions
Powered by GitBook
On this page
  • General
  • Run Profiles
  • Triggers
  • Advanced
  1. installation

Management agent configuration

PreviousConfiguring the AutoSync serviceNextSettings

Last updated 3 years ago

Each management agent in AutoSync must be configured before AutoSync will be able to manage it.

General

Setting
Description

Disable automation of this management agent

Prevents AutoSync from interacting with the management agent. Other settings cannot be configured if the management agent is disabled

Schedule an import if it has been longer than x minutes since the last import operation

Run Profiles

AutoSync must know which run profiles should be used for the various operations it needs to perform. When initially configuring the management agent, AutoSync will take a best-guess at working out which profiles should be used. You should check to ensure these profiles are correct.

AutoSync only supports single-step run profiles

You will need to create single-step run profiles for each of your MAs if they do not already exist. AutoSync needs to have full control of what run profiles execute in order to ensure accurate locking and triggering of the correct follow up run profiles.

You can leave certain profiles blank if you don't want AutoSync to perform that function. For example, if you don't want AutoSync to ever perform an export, set the export profile name to (none).

Setting
Description

Confirming import

Called automatically by AutoSync after an export has been performed

Delta import

Called by certain triggers when changes have been detected in a connected system. If the management agent doesn't support delta imports, specify a full import profile

Delta sync

Called automatically by AutoSync after an import operation has been performed

Export

Called automatically by AutoSync when staged exports are detected on a management agent

Full import

Not called by AutoSync automatically. Only called by custom PowerShell script triggers

Full sync

Not called by AutoSync automatically. Only called by custom PowerShell script triggers

Scheduled import

Called automatically by AutoSync when the Schedule an import if it has been longer than x minutes since the last import operation option has been specified

Triggers

Advanced

Setting
Description

Execution controller script

Lock management agents

This field should contain a semi-colon separated list of other management agents that should not run at the same time as the selected management agent. AutoSync will wait for a lock these management agents before running any run profile

This option ensures that at a minimum, an import is always performed at the specified interval. Usually are used to fire import operations on a management, but if this has not happened within the specified interval, an import will be performed. The run profile specified as the Scheduled import run profile is executed.

Triggers are used by AutoSync to detect changes in connected systems and schedule import operations, and to execute run profiles outside of the standard delta import, delta sync, export, confirming import cycle. See the topic on to learn about the types of triggers available, and how to configure them.

This optional, advanced feature allows you to use a PowerShell script to determine if a run profile should be executed, and provides the ability to assess the results of a run profile upon completion. See the topic on for more information.

triggers
triggers
execution controller scripts