> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-install-and-publish-an-application.md).

# How to Install and Publish an Application in Remote Desktop

Install an application on the environment server, publish it in the dashboard with its paths, and grant access to the users who should use it.

Publishing an application in Remote Desktop has two sides: installing it on the server that serves the sessions and registering it in the panel so your users can see and open it.

The environment includes a Marketplace with apps that install automatically, but when you need a program that isn't in that list, you install it yourself manually via RDP.

This guide covers the full process, focusing on manual installation, and ends by assigning access. GVim is used as an example, but the flow is the same for any application.

> #### 👍 What you get
>
> An application installed on the server, published in the environment with its correct paths and assigned to the users who need to use it.

### Before you start

* Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions on the environment.
* Have an active Remote Desktop subscription. If you don't have one yet, set it up with the [Remote Desktop Quick Start.](https://docs.plenit.com/docs-en/productos/remote-desktop/quickstart.md)
* Have the application's installer copied to the server if you're going to install it manually.
* Use a user with administrative privileges on the server and Remote Desktop access.

### Step 1. Open application creation

In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → Remote Desktop** and enter the environment subscription. Open the **Applications**, where you can see the already provisioned applications, with their name, category, installation type, users with access, and the actions menu **(...)**.

At the top right, click **New Application**. The application catalog opens: to register one you are going to install yourself, click **Publish new application**.

![Applications section and creation of a new application](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fg1NZrElWiAqHd0erWWFQ%2Fescritorio-remoto-instalar-app-01.png?alt=media\&token=368027c3-d162-455f-b20e-b0c1bd8b1f49)

> #### 📘 Marketplace or manual installation
>
> If the application appears in that catalog, select it and use its automatic installation.
>
> The rest of this guide covers the opposite case: a program that doesn't appear there and that you have to install yourself via RDP.

### Step 2. Connect to the server via RDP and install

If the application is not yet on the server, connect via RDP to install it. Use your usual RDP client or the **RDP Connection**, which opens a web front end: log in to the user portal when prompted, download the `.rdp` file and run it, and enter the password again to complete the connection.

Once on the server desktop, run the program installer with a user with administrative privileges and complete the installation as you would on any Windows. Verify that it is installed before returning to the panel.

![RDP connection to the server to install the application](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FsAK5rOoJdZ54Rradf0cF%2Fescritorio-remoto-instalar-app-02.png?alt=media\&token=fb91957a-fd64-43c8-b442-bde3c7775468)

> #### 🚧 If the RDP connection doesn't complete
>
> Log in to the user portal again, download the `.rdp` file again and run it. Enter the password only when the portal or the connection window asks for it.

> #### 📘 Software installation depends on each application
>
> This guide does not detail the internal installation, because it changes depending on the software. What you do need afterward, regardless of the application, are its two paths (Step 3).

### Step 3. Locate the two paths you need

To publish the application, the panel will ask you for two server paths:

* The **root path** (working directory) where the application is installed.
* The **executable path** associated.

For the executable, right-click the application icon, open **Properties** and, in the **Shortcut**, copy the contents of the **Target** (Shortcut and Target if Windows is in English), without quotes or arguments. The root path usually matches the Start in field. Check afterward that the executable is in that path.

![Executable path in shortcut properties](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F4M8A3Crg1Og1ODD0cqZz%2Fescritorio-remoto-instalar-app-03.png?alt=media\&token=0694ea57-dfbe-427e-93e3-806f1b5e6e36)

> #### 🚧 The root and the executable do not always match
>
> The executable does not have to be in the same folder as the application's root. Verify both values separately before continuing, because in the registration they go in different fields, and an incorrect executable path will prevent the application from opening.

### Step 4. Register the application in the panel

Go back to the panel, to the **Publish new application**screen, leave the option for whether it is already installed on your server set to Yes and fill in the fields:

* **Logo**: the icon with which the application will be displayed.
* **Name**: the name with which it will be displayed in the environment.
* **Category**: the type of application (Utilities, Databases, etc.).
* **Working directory**: the path of the application's **root** (not the folder of the executable).
* **Executable path**: the path to the **executable**, which may be different from the directory.
* **Executable arguments**: only if the application needs startup parameters.

Click **Save**. The progress appears in the alerts section and, when finished, the application appears in the list.

![Application registration with its paths](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FsrYX1woqn7hNiG9h1UUO%2Fescritorio-remoto-instalar-app-04.png?alt=media\&token=ca7da6f7-f931-448a-817c-526b691779c2)

### Step 5. Assign access to users

The application is already published, but no one can see it yet: access is assigned manually. In the list, open the application's **(...)** menu and click **Users**. Select the users who should use it and click **Save**.

![User assignment to the application](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FdeBXnMnmT3EAn9SzGjwy%2Fescritorio-remoto-instalar-app-05.png?alt=media\&token=7de7bd22-6f1c-472e-8865-291d7eba35af)

Back in **Applications**, check that the application appears available and that the users column shows the people you gave access to.

> #### 👍 Before closing, validate
>
> The application appears in the Applications list, the users column shows the accesses, the Working Directory points to the correct root and the Executable Path to the correct executable.

### Conclusion

Publishing an application is connecting two worlds: the software installed on the server and its record in the panel. If it is not in the Marketplace, you install it manually by connecting via RDP; if it is, you use its automatic installation.

In both cases, the part that the process takes most care with is the paths, because the application's root and the executable's root may not match, and the panel asks for them separately.

Once registered, remember that access is not automatic: you manually assign the users who should see it. With that, the application is centralized on the server and available only to whoever needs it.

### Next steps

* Register or assign users in bulk with the [Bulk User Upload.](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-bulk-upload-users.md)
* Review the environment's printing modes in [Printing.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/printing.md)
* Manage the rest of the environment from [How to manage your Remote Desktop environment.](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-administer-your-remote-desktop.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.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-install-and-publish-an-application.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.
