> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/autosync-for-mim/installation/management-agent-configuration.md). # Management agent configuration Each management agent in AutoSync must be configured before AutoSync will be able to manage it. ### General ![](https://2216211724-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXaBwZ6mZ5WbX108JiSsn%2Fuploads%2Fgit-blob-d67461ef022b875b8ccfb57d198d4f4fab0fd029%2Fma-config-general.png?alt=media) | 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 | This option ensures that at a minimum, an import is always performed at the specified interval. Usually [triggers](/autosync-for-mim/configuration/triggers.md) 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. | ### 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)`. ![](https://2216211724-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXaBwZ6mZ5WbX108JiSsn%2Fuploads%2Fgit-blob-c97d7d3535bf469080b3e37c84cac7bc8f4533a8%2Fma-config-runprofiles.png?alt=media) | 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 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 [triggers](/autosync-for-mim/configuration/triggers.md) to learn about the types of triggers available, and how to configure them. ![](https://2216211724-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXaBwZ6mZ5WbX108JiSsn%2Fuploads%2Fgit-blob-1eea2bda45c1b14337d125ae8b58730a1b29c041%2Fma-config-triggers.png?alt=media) ### Advanced ![](https://2216211724-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXaBwZ6mZ5WbX108JiSsn%2Fuploads%2Fgit-blob-edbc65bf70ff17ef2b4e3e84a93d36421ae924e1%2Fma-config-advanced.png?alt=media) | Setting | Description | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Execution controller script | 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 [execution controller scripts](/autosync-for-mim/configuration/execution-controller-scripts.md) for more information. | | 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 | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lithnet.io/autosync-for-mim/installation/management-agent-configuration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.