> 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/rdm/knowledge-base/knowledge-base-articles/entry-settings/proxmox-synchronizer.md).

# Proxmox synchronizer

Configure the Proxmox synchronizer in Remote Desktop Manager, including authentication, realm, credential, nodes, resource types, templates, and schedule.

This article details the many settings and options available for ***Proxmox*** synchronizer entries in Remote Desktop Manager.

{% hint style="info" %}
The ***Schedule*** tab is shown only when the data source is Devolutions Server.
{% endhint %}

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr><tr><td><strong>Synchronize automatically</strong></td><td>Run the synchronizer automatically.</td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>URL</strong></td><td>The URL of the Proxmox server. Required.</td></tr><tr><td><strong>Ignore certificate errors</strong></td><td>Connect to the Proxmox server even when its certificate is not valid.</td></tr><tr><td><strong>Authentication mode</strong></td><td><p>Choose how the synchronizer authenticates to Proxmox:</p><ul><li><strong>Ticket</strong> — authenticate with a <em><strong>Username</strong></em> and <em><strong>Password</strong></em>.</li><li><strong>Token</strong> — authenticate with a <em><strong>Username</strong></em>, a <em><strong>Token id</strong></em>, and a <em><strong>Secret token</strong></em>.</li></ul></td></tr><tr><td><strong>Realm</strong></td><td>The Proxmox authentication realm. The list is retrieved from the server set in <em><strong>URL</strong></em> when the entry is opened. Click the <em><strong>Refresh</strong></em> button to retrieve it again. Required.<br><br>Single sign-on is not supported for synchronization, because the synchronizer runs unattended and cannot display the browser sign-in. When <em><strong>Authentication mode</strong></em> is <em><strong>Ticket</strong></em> and the selected realm uses single sign-on, a warning is displayed and the entry cannot be saved. Use an API token instead.</td></tr><tr><td><strong>Username</strong></td><td>The Proxmox username. Required.</td></tr><tr><td><strong>Password</strong></td><td>The Proxmox password. Shown and required when <em><strong>Authentication mode</strong></em> is <em><strong>Ticket</strong></em>.</td></tr><tr><td><strong>Token id</strong></td><td>The ID of the Proxmox API token. Shown and required when <em><strong>Authentication mode</strong></em> is <em><strong>Token</strong></em>.</td></tr><tr><td><strong>Secret token</strong></td><td>The secret of the Proxmox API token. Shown and required when <em><strong>Authentication mode</strong></em> is <em><strong>Token</strong></em>.</td></tr><tr><td><strong>Credential</strong></td><td>Select or add a Proxmox credential. Synchronized sessions require this credential to connect to Proxmox resources. Only <em><strong>Proxmox</strong></em> credential entries are listed. Click the <em><strong>Add credential</strong></em> button to create one. This field is required.</td></tr><tr><td><strong>Destination folder</strong></td><td>The folder where the synchronized entries are created. Click the browse button to select a folder, or click the add (<em><strong>+</strong></em>) button to create a new one.</td></tr><tr><td><strong>Sync mode</strong></td><td><p>Choose which nodes to synchronize:</p><ul><li><strong>All nodes</strong></li><li><strong>Specific node</strong></li></ul></td></tr><tr><td><strong>Node</strong></td><td>The node to synchronize. Click the browse button to select it from the server. Shown and required when <em><strong>Sync mode</strong></em> is <em><strong>Specific node</strong></em>.</td></tr><tr><td><strong>Type</strong></td><td><p>Choose which resources to synchronize:</p><ul><li><strong>All</strong></li><li><strong>Virtual machines</strong></li><li><strong>Containers</strong></li></ul></td></tr><tr><td><strong>Virtual machine template</strong></td><td>The template applied to the entries created for virtual machines. Shown when <em><strong>Type</strong></em> is <em><strong>All</strong></em> or <em><strong>Virtual machines</strong></em>.</td></tr><tr><td><strong>Container template</strong></td><td>The template applied to the entries created for containers. Shown when <em><strong>Type</strong></em> is <em><strong>All</strong></em> or <em><strong>Containers</strong></em>.</td></tr></tbody></table>

### Fields

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Fields list</strong></td><td><p>Check the fields to synchronize, and clear the ones to leave untouched. Use the <em><strong>Search</strong></em> box above the list to filter it by name. The available fields are:</p><ul><li><strong>Session name</strong></li><li><strong>Description</strong></li><li><strong>Folders</strong> (cleared by default)</li></ul></td></tr><tr><td><strong>Session name prefix</strong></td><td>Text added before the name of each synchronized entry. Shown when <em><strong>Session name</strong></em> is selected in the list.</td></tr><tr><td><strong>Session name suffix</strong></td><td>Text added after the name of each synchronized entry. Shown when <em><strong>Session name</strong></em> is selected in the list.</td></tr></tbody></table>

### Schedule

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Enabled</strong></td><td>Run the synchronizer on a schedule.</td></tr><tr><td><strong>Every</strong></td><td><p>Enter the interval between two runs (minimum 1), then choose its unit:</p><ul><li><strong>Days</strong></li><li><strong>Hours</strong></li></ul><p>Available when <em><strong>Enabled</strong></em> is checked.</p></td></tr><tr><td><strong>At</strong></td><td>The time of day at which the synchronizer runs, in 24-hour format. Shown when the interval unit is <em><strong>Days</strong></em>, and available when <em><strong>Enabled</strong></em> is checked.</td></tr></tbody></table>

### Advanced

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Silent mode</strong></td><td>Run the synchronizer without displaying the synchronization result message.</td></tr><tr><td><strong>Duplicate check</strong></td><td><p>Choose where the synchronizer looks for existing entries to avoid creating duplicates:</p><ul><li><strong>Root</strong></li><li><strong>Destination folder</strong></li></ul></td></tr><tr><td><strong>Action on entry mismatch</strong></td><td><p>Choose what happens to entries previously created by the synchronizer that no longer match the source:</p><ul><li><strong>None</strong></li><li><strong>Delete</strong></li><li><strong>Move to</strong></li><li><strong>Make expired</strong></li></ul></td></tr><tr><td><strong>Destination folder</strong></td><td>The folder where mismatched entries are moved. Shown when <em><strong>Action on entry mismatch</strong></em> is <em><strong>Move to</strong></em>.</td></tr><tr><td><strong>Expiration message</strong></td><td>The message set on mismatched entries when they are marked as expired. Shown when <em><strong>Action on entry mismatch</strong></em> is <em><strong>Make expired</strong></em>.</td></tr></tbody></table>

### See also

* [Synchronizers](https://docs.devolutions.net/rdm/concepts/advanced-concepts/synchronizers.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/rdm/knowledge-base/knowledge-base-articles/entry-settings/proxmox-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.
