> 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/rdm/da/knowledge-base/how-to-articles/configure-sql-server-for-protected-users-with-integrated-security.md).

# Konfigurer SQL Server til beskyttede brugere med integreret sikkerhed

Konfigurer SPN'er for SQL Server til Kerberos-godkendelse, så beskyttede brugere kan oprette forbindelse via den integrerede sikkerhed i Remote Desktop Manager.

Her er trinnene til at konfigurere Deres SQL Server, så Deres ***Beskyttede brugere*** kan oprette forbindelse til databasen med godkendelsesmetoden Integreret sikkerhed.

Ifølge Microsoft blokerer ***Beskyttede brugere*** brugen af [NTLM-hash](https://docs.microsoft.com/en-us/windows-server/security/credentials-protection-and-management/protected-users-security-group#domain-controller-protections-for-protected-users). Det er dog muligt at konfigurere SQL Server til også at bruge [Kerberos til integreret sikkerhed](https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/register-a-service-principal-name-for-kerberos-connections). Det understøttes som standard af Remote Desktop Manager.

For at SQL Server kan understøtte Kerberos-godkendelse, skal der oprettes SPN'er. Som standard kører tjenesten under konti, der mangler de nødvendige tilladelser. De kan få følgende meddelelser, når SQL Server starter (De kan se loggene i SSMS under ***Administration – SQL Server-logge***): "The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service."

De skal konfigurere SQL Server-tjenesten til at køre under ***Netværkstjeneste***, da den har de [nødvendige tilladelser](https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/register-a-service-principal-name-for-kerberos-connections?view=sql-server-ver15#Permissions). Ifølge [denne artikel](https://dba.stackexchange.com/questions/180064/what-should-my-spn-entries-look-like-for-each-sql-instance/180147#180147) er det også muligt at give en tjenestekonto tilladelse til at oprette SPN'er. De skal også ændre kontoen i SQL Server Configuration Manager.

SQL Server kan dog stadig rapportere, at den ikke kunne registrere SPN'erne. [Microsoft Kerberos Configuration Manager for SQL Server](https://www.microsoft.com/en-ca/download/details.aspx?id=39046) kan bruges til at rette SPN'erne. Det viser knapper, der kan klikkes på, i kolonnerne Handling.

Når De har genstartet SQL Server-tjenesten, bør De se “The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) \[ **MSSQLSvc/vdownsrv-sql3.downhill.loc:1433** ] for the SQL Server service.” i loggene.

På dette tidspunkt bør forbindelsen fungere igen i Remote Desktop Manager.


---

# 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/rdm/da/knowledge-base/how-to-articles/configure-sql-server-for-protected-users-with-integrated-security.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.