> 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/cloud/da/concepts/advanced-concepts/services.md).

# Tjenester

Kør Devolutions Cloud Services i det lokale miljø for at hoste krypterings-, PAM- og rapporteringskomponenter, der understøtter Devolutions Cloud.

Tjenester henviser i denne sammenhæng til Devolutions Cloud Services, komponenterne i det lokale miljø, der forbinder Devolutions Cloud med lokal infrastruktur til kryptering, PAM og rapportering. Fordi Devolutions Cloud er cloudbaseret, installeres Devolutions Cloud Services lokalt for at hoste krypteringstjenesten, PAM-tjenesten og rapporteringstjenesten, som kommunikerer sikkert med Devolutions Cloud.

Vedligeholdelse af disse Windows-tjenester og deres logge er en del af at drive Devolutions Cloud pålideligt. Når de er sunde og versionsafstemte, fortsætter rotation af PAM-adgangskoder, formidling af privilegerede sessioner og planlagte rapporter med at køre, også mens selve Devolutions Cloud udvikler sig. Planlagte vedligeholdelsesvinduer omfatter typisk genstart eller opgradering af disse tjenester, mens deres logge overvåges for fejl.

#### Relaterede emner

* [Devolutions Cloud Services](/cloud/da/devolutions-cloud-services.md)
* [PAM med Devolutions Cloud](https://docs.devolutions.net/pam/pam-with-devolutions-cloud)
* [Planlagte rapporter](/cloud/da/web-interface/reports/scheduled-reports.md)


---

# 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/cloud/da/concepts/advanced-concepts/services.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.