> 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/application-help-pages/access-manager-agent/agent-policies/access-manager-agent-policies-amsv2-page.md). # Access Manager Agent - Legacy AMSv2 policies page {% hint style="info" %} Access Manager Agent v2 is supported by servers running either Access Manager v2 or v3. However, [features introduced in Access Manager v3](/ams/v3.0/whats-new.md) are not available in these agents. Agent Policies configured under the `Legacy AMSv2 policies` page will only target devices running Access Manager Agent v2. For more information on planning your AMS v3 migration, see our [upgrading from Access Manager v2 to v3](/ams/v3.0/installation/upgrading-from-v2.md) guide. {% endhint %} The `Legacy AMSv2 policies` page in the `Access Manager Agent` area of Access Manager allows you to configure policies for devices running Access Manager Agent (version 2.0 *only*). You can create custom Access Manager Agent v2 policies that are targeted at specific computers, groups and containers defined AMS. If no policies are configured, or an agent does not match any of the custom policies configured, the "Default V2 agent policy" will be applied to the agent. You can view or edit the default policy for v2 agents by clicking `Edit default policy...` at the top of the page. ![](https://1500666603-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzPrDxVWpXXpSNTpkDVnR%2Fuploads%2Fgit-blob-8a30728a14166a50ee228546bbb4b5313e652d8c%2Fui-page-access-manager-agent-agent-policies-legacyv2-policies.png?alt=media) ## Create or edit an agent policy You can create a new Access Manager Agent policy for v2 devices by clicking the `Create new...` button at the bottom of the page. ### Policy settings ![](https://1500666603-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzPrDxVWpXXpSNTpkDVnR%2Fuploads%2Fgit-blob-87712df0e9f5234a0ecbf21720c05e5a75fe5a1c%2Fui-page-access-manager-agent-agent-policies-legacyv2-policies-edit-policy.png?alt=media) #### Policy name Specify the name for the custom agent policy. {% hint style="info" %} Note: This field is not configurable for the default policy. {% endhint %} #### Policy target group This list allows you to target specific computers, groups and containers that the policy will be applied to. {% hint style="info" %} It is important to note that Access Manager evaluates policies in the order they are presented in the UI. When an agent checks in to the Access Manager server, the server will evaluate each policy - in order - to determine if the policy is applicable to the agent (given the configured targets). The *first policy that matches* will be applied to the agent. If no policy is configured with a target that captures the given device, the device's policy will fall back to the default agent policy. For this reason, it is important to consider the order in which your policies are organized; as a rule of thumb, policies with more specific targets should be placed *higher* in the list than more generically-targeted policies. {% endhint %} {% hint style="info" %} Note: This field is not configurable for the default policy. {% endhint %} ### Password settings ![](https://1500666603-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzPrDxVWpXXpSNTpkDVnR%2Fuploads%2Fgit-blob-123c1518e54b6740e3d80a14d63b5f1fdc77cbdc%2Fui-page-access-manager-agent-agent-policies-linux-policies-edit-passwords.png?alt=media) #### History * **Maximum password age (days)**: The maximum number of days before the password must be rotated. For example, if this is set to 7, then the password would be rotated after 7 days. * **Number of previous passwords to keep**: The number of historical passwords to store in the Access Manager database. * **Number of days to keep previous passwords**: The number of days to keep historical passwords for; setting this field to "0" disables aging out of historical passwords. See [Password history and retention](/ams/v3.0/help-and-support/advanced-help-topics/password-history-retention.md) for more information how how these settings work to ensure you have the right number of passwords retained. #### Composition The following configuration options are available to configure how Access Manager Agent v2 generates passwords for the built-in Administrator account: * **Password length**: The length of passwords to be generated for local administrator accounts * **Password composition** * **Use lower-case letters**: If configured, generated passwords will contain lower-case letters * **Use upper-case letters**: If configured, generated passwords will contain upper-case letters * **Use numbers**: If configured, generated passwords will contain numbers * **Use symbols**: If configured, generated passwords will contain symbols --- # 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/application-help-pages/access-manager-agent/agent-policies/access-manager-agent-policies-amsv2-page.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.