> 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/ams/v1.0/installation/installing-access-manager/installing-the-access-manager-agent.md).

# Access Manager Agent

## Prerequisites

In order to install the Access Manager Agent, the following prerequisites must be met

1. Windows 8.1 or Windows Server 2012 R2 or later
2. [.NET Framework Runtime](https://dotnet.microsoft.com/download) 4.7.2 or later installed

We recommend using a configuration management tool such as SCCM to deploy the agent to your fleet.

## **Download and install the Access Manager Agent**

1. Download the latest version of the agent from the [releases](https://github.com/lithnet/access-manager/releases/latest) page. Take note that you must install the x64 version on 64-bit machines, and the x86 version on 32-bit machines.
2. Run the AMA installation package. Follow the prompts to install the application.

## **Configure the agent via Group Policy**

The Access Manager agent doesn't do anything until it's configured via a group policy. Follow the [password encryption and history setup guide](/ams/v1.0/configuration/deploying_features/setting-up-password-encryption-and-history.md) for the correct process of setting up the relevant group policy settings.


---

# 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/ams/v1.0/installation/installing-access-manager/installing-the-access-manager-agent.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.