> 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/v3.0/help-and-support/advanced-help-topics/setting-up-agent-policies.md). # Setting up agent policies This guide will walk you through the steps to configure policies for the Lithnet Access Manager Agent. Agent policies are used to configure features such as *password management*, *RapidLAPS*, and *BitLocker recovery key backup*. The agent will periodically "check-in" with the Access Manager Server to retrieve the appropriate policy. ## Types of policies Agent policies are divided into three categories, based on the target operating system: *Windows*, *macOS* and *Linux*. Each operating system has a **default** policy, and a set of **custom** policies. You can create custom Access Manager Agent policies that are targeted at specific computers, groups and containers - from Active Directory, Microsoft Entra, or AMS. ## Policy precedence Policies are processed in the order they appear in the custom agent policy list. The first policy that matches a given computer is the policy that will be used. You should ensure that the most specific policies (eg policies that target individual computers and groups) are located at the top of the list. If no matching policy can be found, the default agent policy will be used. ## Default agent policy The default agent policy is the 'fallback' policy that will be used when a computer does not match any of the custom policies configured. It should contain settings that are applicable as a default base across your environment. If all computers should have the same policy settings, then there is no need to configure custom policies at all. ## Creating a new policy If you need to vary policy settings between devices, then you'll need to create a custom policy, and target it to those devices. ### Step 1. Navigate to an OS-specific policy page To create an agent policy, first select the operating system you wish to configure policy for in the sidebar under `Access Manager Agent/Agent policies`: ![](https://1500666603-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzPrDxVWpXXpSNTpkDVnR%2Fuploads%2Fgit-blob-2423850afb5c7c9e80fadbf102c3ca1684c663ed%2Fagent-policy-sidebar.png?alt=media) ### Step 2. Create a new custom agent policy Click the `Create new...` button at the bottom of the custom agent policy list. ### Step 3. Configure general policy settings ![](https://1500666603-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzPrDxVWpXXpSNTpkDVnR%2Fuploads%2Fgit-blob-a26236c28dd9d81483138f0915d8642065da0559%2Fagent-policy-edit-generic.png?alt=media) On the first page of the policy editor - configure a memorable name and a description for your custom policy. Next, configure the "Agent check-in interval". This setting determines how frequently the agent should attempt to check-in to the server - in minutes. When an agent checks in, it will receive policy updates, reset local administrator account passwords (if required), and backup disk encryption keys (if required). The default value is to check-in every to 60 minutes. Next, configure the "targets" for your custom policy. Policies can be targeted at specific computers, groups and containers - from Active Directory, Microsoft Entra, or AMS. To add a new target to a policy, simply click `Add...` at the bottom of the target list, and follow the prompts to select your target computer, group, or container. ### Step 4. Configure your policy settings Next, you can configure agent settings by selecting from the tabs on the left-hand side of the policy editor. For more details, visit the appropriate guide for setting up each feature * [Setting up Lithnet LAPS](/ams/v3.0/configuration/deploying-features/setting-up-laps/setting-up-lithnet-laps.md) * [Setting up RapidLAPS (Windows only)](/ams/v3.0/configuration/deploying-features/setting-up-rapid-laps.md) * [Setting up BitLocker backup (Windows only)](/ams/v3.0/configuration/deploying-features/setting-up-bitlocker/setting-up-bitlocker-ams.md) ### Step 5. Save the policy To save the custom policy and make it available for clients, simply click the `Save` button in the bottom right-hand corner of the policy editor. ## More information For more information on the different settings configurable in agent policies, see the corresponding help page: * [Windows agent policies page](/ams/v3.0/help-and-support/application-help-pages/access-manager-agent/agent-policies/access-manager-agent-policies-windows-page.md) * [macOS agent policies page](/ams/v3.0/help-and-support/application-help-pages/access-manager-agent/agent-policies/access-manager-agent-policies-macos-page.md) * [Linux agent policies page](/ams/v3.0/help-and-support/application-help-pages/access-manager-agent/agent-policies/access-manager-agent-policies-linux-page.md) * [Legacy (v2) agent policies page](/ams/v3.0/help-and-support/application-help-pages/access-manager-agent/agent-policies/access-manager-agent-policies-amsv2-page.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lithnet.io/ams/v3.0/help-and-support/advanced-help-topics/setting-up-agent-policies.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.