> 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/password-protection/help-and-support/troubleshooting.md). # Troubleshooting steps ### The group policy settings do not appear when I open the group policy editor If you have installed the group policy templates on the computer, but they do not appear under `Computer Configuration\Policies\Administrative Templates\Lithnet\Password Filter` when you open the group policy editor, then your domain is likely using a [central policy store](https://support.microsoft.com/en-au/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra). See the steps in [configuring the group policy](/password-protection/setup/configure-group-policy.md) for instructions on how to copy the group policy template files to the central policy store. ### Password changes are not being rejected as expected If the password change was not blocked as expected, run the [Get-PasswordFilterConfig](/password-protection/advanced-help/powershell-reference/get-passwordfilterconfig.md) and [Get-PasswordFilterPolicy](/password-protection/advanced-help/powershell-reference/get-passwordfilterpolicy.md) cmdlets on the server that processed the password change, and ensure the correct configuration and policy is applied. ### Passwords are being rejected, but no event log from LPP is present If the password was rejected, but there was no event log entry from LithnetPasswordProtection explaining the reason for the password change, there are two likely reasons for this 1. It may be because another password filter, or Windows itself rejected the password. If you use the built-in Windows password policy, those settings are always processed before LPP can review the password. In this case, LPP will never see the password to evaluate it. 2. The event log from LithnetPasswordProtection will only appear on the server that processed the password change. This could be any writable domain controller in the domain. Ensure that you check all domain controllers for the event log entry. --- # 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/password-protection/help-and-support/troubleshooting.md?ask=&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.