> 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/help-and-support/advanced-help-topics/group-policy-configuration.md).

# Group policy configuration

{% hint style="info" %}
The Access Manager v3 agent no longer gets its password settings from group policy. V3 agents obtain their password settings from the AMS server via [agent policy](/ams/help-and-support/advanced-help-topics/setting-up-agent-policies.md)
{% endhint %}

If your agents are joined to an Active Directory domain, you can use Group Policy to configure the agent.

When you install the Access Manager Agent on a computer, the group policy ADMX files get automatically installed. However, if you are using a central policy store, you'll need to manually copy the ADMX and ADML files to the store.

The following files need to be copied

* `C:\Windows\PolicyDefinitions\lithnet.admx`
* `C:\Windows\PolicyDefinitions\lithnet.accessmanager.agent.admx`
* `C:\Windows\PolicyDefinitions\lithnet.accessmanager.agent.password.admx`
* `C:\Windows\PolicyDefinitions\en-US\lithnet.adml`
* `C:\Windows\PolicyDefinitions\en-US\lithnet.accessmanager.agent.adml`
* `C:\Windows\PolicyDefinitions\en-US\lithnet.accessmanager.agent.password.adml`

The central policy store is located at `\\<domain>\sysvol\<domain>\Policies\PolicyDefinitions`

Using the group policy editor, create a new group policy object, and link it to the OU containing your computer objects. Open the policy and navigate to `Administrative Templates`, `Lithnet`, `Access Manager Agent`.

![](https://3858442128-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq1NRJ1mSUxsI5xgqtLGt%2Fuploads%2Fgit-blob-8285e0e3a8fad2c2fbbbe5850aef306a1c4f1305%2Fgroup-policy-agent.png?alt=media)

Edit the `Enable the Lithnet Access Manager Agent` policy, and specify the server name. Note that the Agent check interval only applies to the v2 agent. The v3 agent's check in interval is configured in its agent policy defined on the AMS server.

### v2 Agent settings

The settings contained under `Administrator password management (Legacy v2.0 agent)` are not used at all by the v3 agent, and are provided for backwards compatibility with the v2 agent. The v3 agent does not store it's passwords in Active Directory and gets it agent policy from the AMS server directly.

For information on configuring these settings for the v2 agent, please see the [v2 agent documentation](https://docs.lithnet.io/ams/v2.0/configuration/deploying-features/setting-up-lithnet-laps/setting-up-lithnet-laps-for-active-directory#step-5-configure-the-access-manager-agent-group-policy).


---

# 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/help-and-support/advanced-help-topics/group-policy-configuration.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.