> 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/de/knowledge-base/how-to-articles/enable-the-server-side-synchronizer.md).

# Den serverseitigen Synchronizer aktivieren

Aktivieren Sie den serverseitigen Synchronizer in Devolutions Server, damit der Scheduler geplante Active Directory- oder VMware-Synchronizer-Einträge automatisch ausführt.

{% hint style="warning" %}
Der Devolutions Server Scheduler muss installiert sein und ausgeführt werden, damit diese Funktion aktiviert werden kann.
{% endhint %}

{% hint style="success" %}
Nur die Synchronizer-Eintragstypen Active Directory und VMWare werden von dieser Funktion unterstützt.
{% endhint %}

Die folgenden Schritte beschreiben, wie Sie den serverseitigen Synchronizer aktivieren, damit er vom Devolutions Server Scheduler ausgeführt wird.

1. Erstellen Sie in der Devolutions Server-Weboberfläche einen neuen Synchronizer-Eintrag.
2. Füllen Sie die Eigenschaften für den gewählten Synchronizer-Eintrag aus.
3. Gehen Sie zu ***Allgemein*** – ***Zeitplan***.
4. Aktivieren Sie das Kontrollkästchen ***Aktivieren*** und legen Sie die Häufigkeit und den Zeitpunkt der Ausführung des Synchronizers fest.
5. Diese Option kann auch unter ***Allgemein*** – ***Zeitplan*** aktiviert werden, wenn Sie [einen Active Directory-](https://docs.devolutions.net/rdm/de/knowledge-base/knowledge-base-articles/entry-settings/active-directory-synchronizer) oder VMware-Eintrag in Remote Desktop Manager konfigurieren.


---

# 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 dynamically 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/de/knowledge-base/how-to-articles/enable-the-server-side-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 `build a script that syncs our docs to a CMS` 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.