> 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-xsiam/reference-and-developer-docs/reference/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
Configure LDAP server Event ID 1644 logging through Group Policy for Cortex XSIAM.
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
| [](https://docs-cortex.paloaltonetworks.com/viewer/attachment/5CAbsl8idaK8R43ZLhoTOw/vEZJTcCs9lKn5Amq5W3xRg-5CAbsl8idaK8R43ZLhoTOw) |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters]
Create the following Registry items:
Expensive Search Results Threshold
* Action: Update
* Hive: HKEY\_LOCAL\_MACHINE
* Key Path: SYSTEM\CurrentControlSet\Services\NTDS\Parameters
* Value name: Expensive Search Results Threshold
* Value type: REG\_DWORD
* Value data: 1
| [](https://docs-cortex.paloaltonetworks.com/viewer/attachment/5CAbsl8idaK8R43ZLhoTOw/2HpxdNC8WZhPpJH2eq4eSg-5CAbsl8idaK8R43ZLhoTOw) |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
Inefficient Search Results Threshold
* Action: Update
* Hive: HKEY\_LOCAL\_MACHINE
* Key Path: SYSTEM\CurrentControlSet\Services\NTDS\Parameters
* Value name: Inefficient Search Results Threshold
* Value type: REG\_DWORD
* Value data: 1
| [](https://docs-cortex.paloaltonetworks.com/viewer/attachment/5CAbsl8idaK8R43ZLhoTOw/NbalKIbhQXzRh44l6w2tTQ-5CAbsl8idaK8R43ZLhoTOw) |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
Search Time Threshold (msecs)
* Action: Update
* Hive: HKEY\_LOCAL\_MACHINE
* Key Path: SYSTEM\CurrentControlSet\Services\NTDS\Parameters
* Value name: Search Time Threshold (msecs)
* Value type: REG\_DWORD
* Value data: 1
| [](https://docs-cortex.paloaltonetworks.com/viewer/attachment/5CAbsl8idaK8R43ZLhoTOw/K7YtRnvJDve3NnJv4HSaKg-5CAbsl8idaK8R43ZLhoTOw) |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
4. Close the Group Policy Management Editor.
5. To link the GPO to the OU where your domain controllers reside, in Group Policy Management, right-click the OU, select Link an Existing GPO, then select the GPO you just created.\
6. Force Group Policy Update: Force a Group Policy update using the `gpupdate /force` command on each domain controller or by restarting them.
---
# 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-xsiam/reference-and-developer-docs/reference/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.