> 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/agent/readme.md).

# Overview of Devolutions Agent

Devolutions Agent is a background process that performs remote management tasks such as jump sessions, PEDM elevation, and Gateway updates.

Devolutions Agent is a versatile background process used by many Devolutions products to perform various remote management tasks.

{% hint style="info" %}
Devolutions Agent can only operate against Windows-based hosts.
{% endhint %}

### Installation

Download Devolutions Agent from [Devolutions’ website](https://devolutions.net/agent/), and install it on the remote computer. Devolutions Agent must be configured to automatically start when a Windows session is established. Consult the documentation of your operating system for details.

To install Devolutions Agent on many machines at once, see [Deploy Devolutions Agent silently](/agent/deploy-devolutions-agent-silently.md).

The installer displays the following features. ***Devolutions Agent*** is always installed and cannot be deselected. ***Devolutions Gateway Updater***, ***Agent Tunnel***, and ***PowerShell Universal Agent*** are sub-features of ***Devolutions Agent***. The feature ID is the value used to select features during a [silent installation](/agent/deploy-devolutions-agent-silently.md).

<table><thead><tr><th width="200">FEATURE</th><th width="130">FEATURE ID</th><th width="130">DEFAULT</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Devolutions Agent</strong></em></td><td><code>F.Agent</code></td><td>Selected (required)</td><td>Installs the Devolutions Agent service.</td></tr><tr><td><em><strong>Devolutions Gateway Updater</strong></em></td><td><code>F.Updater</code></td><td>Selected</td><td>Enables the Devolutions Gateway updater. This update module updates Devolutions Gateway and Devolutions Cloud Services on the machine, as well as Devolutions Agent itself. It is required to update Devolutions Gateway remotely from Devolutions Server (see <a href="#updating-remote-devolutions-gateways-via-devolutions-agent">Updating remote Devolutions Gateways via Devolutions Agent</a>).</td></tr><tr><td><em><strong>Agent Tunnel</strong></em></td><td><code>F.Tunnel</code></td><td>Not selected</td><td>Connects the agent to a Devolutions Gateway. Requires an enrollment string from your gateway operator, entered in an additional step of the installer. See <a href="https://docs.devolutions.net/gateway/knowledge-base/knowledge-base-articles/agent-tunnel">Agent tunnel</a>.</td></tr><tr><td><em><strong>PowerShell Universal Agent</strong></em></td><td><code>F.PsuAgent</code></td><td>Not selected</td><td>Enables the PowerShell Universal remote agent. Requires the PowerShell Universal server URL and an app token, entered in an additional step of the installer.</td></tr><tr><td><em><strong>Devolutions PEDM</strong></em></td><td><code>F.Pedm</code></td><td>Not selected</td><td>Enables PEDM features and installs the shell extension that adds the <em><strong>Run elevated</strong></em> option to the right-click context menu. Marked as <em><strong>Experimental</strong></em> in the installer. See <a href="/agent/configure-pedm-local-elevation.md">Configure PEDM local elevation</a>.</td></tr><tr><td><em><strong>RDP Extension</strong></em></td><td><code>F.Session</code></td><td>Selected</td><td>Enables RDP session features such as remote execution, jump sessions and remote logoff. Installs the component that opens the RDP virtual channel used by Remote Desktop Manager to communicate with Devolutions Agent during an RDP session.</td></tr></tbody></table>

{% hint style="warning" %}
The ***RDP Extension*** feature is required for Jump connections from Remote Desktop Manager through Devolutions Agent, and for running commands on remote hosts from Remote Desktop Manager. Keep it selected on every [jump host](/agent/jump-host.md) and on every machine where these features are used.
{% endhint %}

New users using this technology may wonder why a full installation of Remote Desktop Manager is required. There are three factors that make this a good solution:

* Remote Desktop Manager on the remote host does not require a workspace, it’s an empty shell.
* The logging of the activity is brought back to your workspace.
* Every technology supported by Remote Desktop Manager can be used remotely.

### Usage

#### Running commands on multiple remote hosts

Devolutions Agent can be used to run scripts from another Remote Desktop Manager installation. Since it uses an RDP channel for communication, it saves you from remote management headaches such as opening various ports in your firewall.

#### Executing commands on remote hosts using RDM MCP server

Devolutions Agent allows users with access to RDM MCP server to run commands on remote hosts via text-based prompts. Read [MCP server (experimental)](https://docs.devolutions.net/rdm/ribbon-menu-bar/tools/all-tools/mcp-server) to learn about RDM MCP server.

#### Leveraging Remote Desktop Manager's PEDM module

With Devolutions Agent, users can obtain elevated privileges for specific actions as defined in Remote Desktop Manager's PEDM module. To use this method, someone with administrator privileges must first configure a PEDM profile and assign it to one or more users. From then on, they should be able to select the profile in Devolutions Agent, and use the ***Run elevated*** option when attempting to access resources requiring admin rights (right-click context menu). See [Privileged elevation and delegation management](https://docs.devolutions.net/pam/concepts/privilege-elevation-and-delegation-management) for more details.

#### Updating remote Devolutions Gateways via Devolutions Agent

{% hint style="info" %}
The [Devolutions Cloud Services](https://docs.devolutions.net/pam/pam-with-devolutions-cloud/install-the-devolutions-cloud-services-to-enable-pam-and-encryption-integration) must be configured on the Devolutions Cloud to enable Devolutions Gateway updates with the Devolutions Agent.
{% endhint %}

Devolutions Agent enables administrators on Devolutions Server to remotely update Devolutions Gateway instances and farms, provided the Agent is installed on the systems hosting them (with the ***Devolutions Gateway Updater*** feature checked during installation).

The updating process can be initiated in a few clicks by toggling the ***Bulk update*** option in ***Administration*** – ***Devolutions Gateway***, selecting the desired gateways and/or farms, and clicking on ***Update***. The ***Update version*** and ***Bulk update*** windows allow for further customization of the process, including options to defer updates, specify versions, etc.

### See also

* [Devolutions Academy – Configure a Jump Host with Devolutions Agent in Remote Desktop Manager](https://academy.devolutions.net/student/activity/3541611-configure-a-jump-host-with-devolutions-agent-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/agent/readme.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.