> 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/okta-ma/installation/system-requirements.md).

# System requirements

What the MIM server needs before you install the management agent.

The management agent is installed on the server that runs the MIM Synchronization Service. You'll need:

* MIM 2016 Synchronization Service, version 4.1.3441 or later
* 64-bit Windows Server
* .NET Framework 4.8
* Local administrator rights to install or upgrade
* Outbound HTTPS to your Okta org

The installer locates the Synchronization Service from the registry, so there's no installation path to choose, and it won't run on a server that doesn't have the service installed. The .NET runtime used by the connector ships inside the MSI, so there's nothing else to install.

The MIM Synchronization Service account needs:

* Write access to the directory holding the management agent log file
* Read access to the private JWK file, if you use private JWK authentication
* Use of the certificate private key, if you use X.509 certificate authentication

If the server reaches the internet through a proxy, set that up before you retrieve the schema. See [Configuring an HTTP proxy](/okta-ma/installation/configuring-an-http-proxy.md).


---

# 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/okta-ma/installation/system-requirements.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.