> 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/knowledge-base-articles/ssms-add-on-entry-password-injection-not-supported-for-version-18-and-later.md).

# Indsættelse af adgangskode i SSMS-tilføjelsesposten understøttes ikke fra version 18

Forstå, hvorfor indsættelse af adgangskode for SSMS-tilføjelsesposten holder op med at virke i Remote Desktop Manager, når De opgraderer til SSMS 18 eller nyere.

SSMS-tilføjelsesposten i Remote Desktop Manager bruger kommandolinjeargumenter til at starte SSMS og udfylde godkendelsesoplysningerne på forhånd, herunder brugernavn og adgangskode. Microsoft fjernede dog understøttelsen af indsættelse af adgangskode via kommandolinjeargumenter i SSMS 18 som led i deres sikkerhedsforbedringer.

For brugere, der er afhængige af indsættelse af legitimationsoplysninger i Remote Desktop Manager, medfører denne ændring et ekstra trin, når SSMS-forbindelser startes. Hvis De bruger SSMS version 17 eller tidligere, virker indsættelse af adgangskode stadig som forventet. Når De opgraderer til ***SSMS 18 eller nyere***, skal De dog angive Deres adgangskode manuelt.

*"Please note that SQL Server Management Studio version 18 or higher will not work when supplying the password. Do you wish to continue anyway?"*


---

# 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/knowledge-base-articles/ssms-add-on-entry-password-injection-not-supported-for-version-18-and-later.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.