> 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/v2.1/configuration/deploying-features/setting-up-lithnet-laps/configuring-lithnet-laps-for-the-ams-directory.md).

# Setting the AMS directory for Lithnet LAPS clients

When using the Lithnet Access Manager Agent (AMA) on devices that are not joined to an Active Directory (non-windows devices, Azure AD devices, and standalone Windows devices), the agent stores passwords in the Access Manager Directory.

## Step 1: Enable the AMS directory

In order to support LAPS on these devices, ensure you have followed the steps in [Setting up the AMS directory](/ams/v2.1/configuration/deploying-features/setting-up-lithnet-laps/setting-up-the-ams-directory.md)

## Step 2: Create a password encryption certificate

From the `Directory configuration/Access Manager Directory/Lithnet LAPS` page, press the `Create new...` button, to create a new encryption certificate.

```
Backup this certificate when prompted and store it in a safe place. If you loose this certificate, you will not be able to decrypt any passwords stored in the directory. There are no other recovery options.
```

![](https://1174763835-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYKUIJoHjACu79Ekwwf7i%2Fuploads%2Fgit-blob-5fa5785cfa87471de2b49bf6733519bb07c32887%2Fui-page-directory-configuration-access-manager-directory-lithnet-laps.png?alt=media)

## Step 3: Adjust the default password policy

AMS uses password policy to instruct clients how to generate their LAPS passwords. You can create custom policies and assign them to groups of computers, and you can specify a default policy that applies when no matching group-based policies are found.

Set the default policy as the baseline for your environment, and create specific policies where circumstances require it.

You can create policies and assign them to either Azure AD or AMS groups containing computers.

![](https://1174763835-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYKUIJoHjACu79Ekwwf7i%2Fuploads%2Fgit-blob-c749095071ec46363b3523f23df39de52a740ca5%2Fui-page-directory-configuration-access-manager-directory-lithnet-laps-edit-default-policy.png?alt=media)


---

# 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/v2.1/configuration/deploying-features/setting-up-lithnet-laps/configuring-lithnet-laps-for-the-ams-directory.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.