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

# Habilitar el sincronizador del lado del servidor

Habilite el sincronizador del lado del servidor en Devolutions Server para que el Scheduler ejecute automáticamente las entradas de sincronizador de Active Directory o VMware programadas.

{% hint style="warning" %}
El Devolutions Server Scheduler debe estar instalado y en ejecución para que esta función esté habilitada.
{% endhint %}

{% hint style="success" %}
Esta función solo admite los tipos de entrada de sincronizador de Active Directory y VMWare.
{% endhint %}

Los siguientes pasos describen cómo habilitar el sincronizador del lado del servidor para que lo ejecute el Devolutions Server Scheduler.

1. Desde la interfaz web de Devolutions Server, cree una nueva entrada de tipo Synchronizer.
2. Rellene las propiedades de la entrada Synchronizer elegida.
3. Vaya a ***General*** – ***Schedule***.
4. Marque la casilla ***Enable*** y establezca la frecuencia y la hora de ejecución del Synchronizer.
5. Esta opción también se puede habilitar en ***General*** – ***Schedule*** al [configurar una entrada de Active Directory](https://docs.devolutions.net/rdm/es/knowledge-base/knowledge-base-articles/entry-settings/active-directory-synchronizer) o de VMware en 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 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/es/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.