> 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/de/concepts/intermediate-concepts/synchronizer.md).

# Synchronizer

Devolutions Cloud-Synchronizer in Remote Desktop Manager importieren und aktualisieren automatisch Einträge aus Active Directory und anderen externen Verzeichnisquellen.

Ein Synchronizer importiert und aktualisiert automatisch Einträge in Remote Desktop Manager, indem er Verbindungsdaten aus externen Systemen in Tresore überträgt. Anstatt Konten oder Server manuell neu zu erstellen, halten Synchronizer die Strukturen mit Quellen wie Active Directory, Cloud-Verzeichnissen oder Virtualisierungsplattformen abgeglichen.

Wenn diese Tresore von Devolutions Cloud unterstützt werden, werden die synchronisierten Einträge und Anmeldeinformationen sicher in Devolutions Cloud gespeichert, während Remote Desktop Manager die Synchronisierungslogik übernimmt. Dieses Modell ermöglicht es Teams, Devolutions Cloud für zentralisierte Speicherung, Auditing und Berichterstattung zu nutzen, während Synchronizer in Remote Desktop Manager verwendet werden, um die manuelle Datenerfassung zu reduzieren und Inventare aktuell zu halten.

#### Verwandte Themen

* [Synchronizer](https://docs.devolutions.net/rdm/de/concepts/advanced-concepts/synchronizers)
* [Active Directory-Synchronizer](https://docs.devolutions.net/rdm/de/knowledge-base/knowledge-base-articles/entry-settings/active-directory-synchronizer)


---

# 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/de/concepts/intermediate-concepts/synchronizer.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.
