> 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/da/knowledge-base/how-to-articles/enforce-domain-containers.md).

# Gennemtving domænebeholdere

Gennemtving domænebeholdere i Devolutions Server ved at gennemgå konfigurerede organisationsenheder, så alle brugere og grupper beholder den rette adgang og de rette tilladelser.

Domænebeholdere gennemtvinges i Devolutions Server. I tidligere versioner kunne brugere og brugergrupper stadig bruges, selv om de lå uden for disse beholdere, så længe de administrative legitimationsoplysninger havde rettigheder til andre organisationsenheder (OU'er) i domænet. Det er ikke længere tilfældet.

Sørg for, at alle brugere og brugergrupper kan bruges:

1. Log på webgrænsefladen for Devolutions Server med en administratorkonto.
2. Gå til ***Administration – Serverindstillinger – Godkendelse – Domæner***.
3. Klik på ***Rediger*** ud for domænet.
4. Gå til ***Avancerede indstillinger***.
5. Under ***Domænebeholdere*** skal De kontrollere, om der er valgt OU'er. Hvis der er konfigureret nogle, skal De sikre, at alle brugere og brugergrupper er med her. Ellers kan brugere og grupper uden for disse beholdere ikke oprette forbindelse eller få de rette tilladelser. De kan også fjerne begrænsningerne for domænebeholdere, hvis Active Directory ikke er stor.
6. Klik på ***OK*** og derefter på ***Opdater*** for at gemme ændringerne.


---

# 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/da/knowledge-base/how-to-articles/enforce-domain-containers.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.