> 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/installing-and-upgrading.md).

# Installing and upgrading

Install the management agent on a MIM Synchronization Service server, or upgrade an existing installation.

Download the MSI from the [releases page](https://github.com/lithnet/okta-managementagent/releases) and run it on the MIM Synchronization Service server, signed in as a local administrator. Confirm the [system requirements](/okta-ma/installation/system-requirements.md) first.

## Install

1. Close Synchronization Service Manager.
2. Run the MSI as an administrator and complete the wizard.
3. Restart the MIM Synchronization Service.

Then confirm the management agent type is registered:

1. Open Synchronization Service Manager and select **Management Agents**.
2. Select **Create** and look for **Okta (Lithnet)** in the list.
3. Cancel the wizard.

![The Okta (Lithnet) management agent type in Synchronization Service Manager.](https://2206708376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0u5rDWCokdBire3bUPyS%2Fuploads%2Fgit-blob-5987e31c9f43b207e5b7cae34f0f6ef7b560af2a%2Fmim-create-management-agent.png?alt=media)

If it is not listed, close and reopen Synchronization Service Manager, then restart the MIM Synchronization Service.

Next, prepare Okta using the guide for your [authentication method](/okta-ma/authentication/choosing-an-authentication-method.md), then continue with [Creating the management agent](/okta-ma/configuration/creating-the-management-agent.md).

## Upgrade

Existing management agents upgrade in place, including ones created with version 2. Do not delete and recreate a management agent unless the release notes tell you to.

Before you start, read the release notes for the target version and note the version you are upgrading from.

{% hint style="warning" %}
If the management agent uses API-token authentication, keep the current token handy. MIM requires every encrypted parameter to be re-entered whenever its configuration page is saved, so you'll need the token again the first time you save the Connectivity page.
{% endhint %}

1. Stop any scheduled run profiles that use the management agent.
2. Close Synchronization Service Manager and stop the MIM Synchronization Service.
3. Run the new MSI as an administrator and complete the wizard.
4. Start the MIM Synchronization Service and reopen Synchronization Service Manager.
5. Apply any version-specific steps from the release notes. Retrieve the schema if the release changed object types or attributes.

Validate the upgrade before resuming the schedule: run Full Import, check errors and object counts, run Full Synchronization, and review the pending exports.


---

# 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/installing-and-upgrading.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.