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

# Enable the server-side synchronizer

Enable the server-side synchronizer in Devolutions Server so the Scheduler runs scheduled Active Directory or VMware synchronizer entries automatically.

{% hint style="warning" %}
The Devolutions Server Scheduler must be installed and running to have this feature enabled.
{% endhint %}

{% hint style="success" %}
Only Active Directory and VMWare synchronizer entry types are supported by this feature.
{% endhint %}

The following steps describe how to enable the server side synchronizer to be run by the Devolutions Server Scheduler.

1. From the Devolutions Server web interface, create a new Synchronizer entry.
2. Fill in the properties for the chosen Synchronizer entry.
3. Go in ***General*** – ***Schedule***.
4. Check the ***Enable*** box and set the occurrence and the time of the execution of the Synchronizer.
5. This option can also be enabled in ***General*** – ***Schedule*** when [configuring an Active Directory](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/active-directory-synchronizer) or VMware entry in 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/server/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 `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.