> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/reference-and-developer-docs/microsoft-windows-security-auditing-setup/enable-ldap-server-events-logging-1644/enable-ldap-server-events-logging-using-gpo.md).
# Enable LDAP server events logging using GPO
Enable LDAP server event logging using Group Policy.
1. On a domain controller or a system with Remote Server Administration Tools (RSAT) installed, open the **Group Policy Management Console** (GPMC).
2. Create a new Group Policy Object (GPO): Right-click on the domain or organizational unit (OU) where your domain controllers reside, then select **Create a GPO in this domain, and Link it here...**. Give it a descriptive name, e.g. Domain Controller Registry Settings.
3. Edit the GPO.
1. Right-click on the newly created GPO and select **Edit**.
2. In the **Group Policy Management Editor**, navigate to **Computer Configuration** → **Preferences** → **Windows Settings** → **Registry**.
3. Add Registry Items: Right-click on **Registry** and select **New** → **Registry Item**.
4. Configure Registry Keys: For each of the registry keys you want to set, create a new Registry Item.
\[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics\]
```
Create the following Registry item:
**15 Field Engineering**
- **Action:** Update
- **Hive:** HKEY_LOCAL_MACHINE
- **Key Path:** SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics
- **Value name:** 15 Field Engineering
- **Value type:** REG_DWORD
- **Value data:** 5
```
---
# 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://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/reference-and-developer-docs/microsoft-windows-security-auditing-setup/enable-ldap-server-events-logging-1644/enable-ldap-server-events-logging-using-gpo.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.