> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/knowledge-base/troubleshooting-articles/domain-group-membership-is-not-retrieved-properly.md).

# Domain group membership is not retrieved properly

Walks through diagnosing and fixing domain group membership not retrieving correctly from Active Directory in Devolutions Server authentication settings.

This is a solution for when the domain group membership is not retrieved correctly from Active Directory. Here are the steps the follow:

1. Access the Devolutions Server web interface and connect using an administrator account.
2. Head over to the ***Administration*** tab, and go to the ***Server settings*** – ***Authentication*** – ***Domain*** page.
3. Click on the ***Diagnostics*** button of the desired domain.
4. Set the ***Diagnostic type*** option to ***Get groups by user***.
5. Enter a username from the problematic group in the ***Parameter*** field.
6. Set the ***Strategy*** option to ***Directory entry token group***.
7. Click on ***Get Diagnostic***.

{% hint style="info" %}
If this fails, instead use ***Directory entry token group (Legacy)*** or ***Recursively*** in the ***Strategy*** dropdown.
{% endhint %}

8. Close this window by clicking on ***Close***.
9. Go to the domain and click on the ***Edit*** button.
10. Click on ***Advanced Settings***.
11. Under ***Strategy***, change the ***Get groups by user*** option to the one selected in step #7.
12. Click on ***OK*** to save the changes.


---

# 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.devolutions.net/server/knowledge-base/troubleshooting-articles/domain-group-membership-is-not-retrieved-properly.md?ask=<question>&goal=<user_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.