> 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/prerequisites.md).

# Prerequisites

## Installation Prerequisites

AutoSync requires the following software components to work correctly

* Microsoft .NET Framework 4.6.1 or later
* Microsoft Forefront Identity Manager 2010 R2 version 4.1.3441 or later
* PowerShell 3.0 or later

The AutoSync service can only be installed on the same server as the FIM Synchronization Service

## Run profile configuration

A key feature of AutoSync is that it will run only the operations that are needed, when they are needed. In order to do so, AutoSync needs to be able to have full control over the specific run profiles that are being executed.

*AutoSync does not support multi-step run profiles for automatic operations*

If you do not have single-step run profiles created for your MAs, you will need to create them. Run profile names are not important (AutoSync will find them no matter what they are called), but the following can be used if you are stuck for ideas.

| Name | Type                  |
| ---- | --------------------- |
| DI   | Delta import          |
| FI   | Full import           |
| DS   | Delta synchronization |
| FS   | Full synchronization  |
| EALL | Export (all items)    |

AutoSync will detect management agents without import or export profiles, and appropriately treat them as read-only or write-only management agents.

## Service account and permissions

AutoSync requires a standard user service account that has the following permissions

* Membership in the **FIMSyncAdmins** group
* Optionally, if a MIM Service MA is in use, and change detection is required, the service account must have permissions to read from the request history. Read permissions on the `msidmCompletedTime` attribute of all 'Request' objects is required. When configuring the change detection trigger for the MIM Service MA, there is an option to create the sets and MPRs required automatically.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lithnet.io/autosync-for-mim/installation/prerequisites.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.