> 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 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 it and open it. The environment includes a Marketplace with applications for automated installation, but when you need a program that isn't on that list, you install it yourself manually by RDP. This guide covers the full process, with a focus 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 admin 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.](/docs-en/productos/remote-desktop/quickstart.md) * Having the application's installer copied to the server, if you are 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** and, in the window that opens, **Install new Application**. /\* ๐Ÿ“ธ SCREENSHOT 1 ยท Applications tab ยท New Application โ€บ Install new Application \*/ ![Applications section and creating a new application](https://REEMPLAZA-URL/escritorio-remoto-instalar-app-01.png) > #### ๐Ÿ“˜ Marketplace or manual installation > > If the application is in the Marketplace, it's better to install it automatically from that list. > > 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 by RDP and install If the application is not yet on the server, connect by RDP to install it. Use your usual RDP client or the button **RDP Connection**, which opens a web front end: log in to the user portal when prompted, download the file `.rdp` and run it, then 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 on any Windows system. Verify that it has been installed before returning to the panel. /\* ๐Ÿ“ธ SCREENSHOT 2 ยท RDP connection to the server to install \*/ ![RDP connection to the server to install the application](https://REEMPLAZA-URL/escritorio-remoto-instalar-app-02.png) > #### ๐Ÿšง If the RDP connection does not complete > > Log in to the user portal again, download the file again `.rdp` and run it. Enter the password only when the portal or the connection window asks for it. > #### ๐Ÿ“˜ The 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, whatever 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 one, right-click the application icon, open **Properties** and, in the **Shortcut**tab, copy the contents of the field **Target**. Then check that the executable is in that path. /\* ๐Ÿ“ธ SCREENSHOT 3 ยท Properties โ€บ Shortcut โ€บ Target field with the executable path \*/ ![Executable path in the shortcut properties](https://REEMPLAZA-URL/escritorio-remoto-instalar-app-03.png) > #### ๐Ÿšง Root and 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 Return to the **New Application** window 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 application type (Utilities, Databases, etc.). * **Working directory**: the **root** path of the application (not the executable folder). * **Executable path**: the **executable**path, which may be different from the directory. * **Executable arguments**: only if the application needs startup parameters. Click **Save**, or **Save and publish another application** if you are going to register several in a row. Progress appears in the alerts section and, when finished, the application appears in the list. /\* ๐Ÿ“ธ SCREENSHOT 4 ยท registration form with Name, Category, Directory, and Executable path \*/ ![Application registration with its paths](https://REEMPLAZA-URL/escritorio-remoto-instalar-app-04.png) ### Step 5. Assign access to users The application is already published, but nobody can see it yet: access is assigned manually. In the list, open the application's **(...)** menu and click **Users**. In the window, click **Add user**, select the users who should use it and click **Save**. /\* ๐Ÿ“ธ SCREENSHOT 5 ยท menu (โ€ฆ) โ€บ Users โ€บ user selection \*/ ![User assignment to the application](https://REEMPLAZA-URL/escritorio-remoto-instalar-app-05.png) Back in **Applications**, check that the application appears available and that the users column shows the people you granted access to. > #### ๐Ÿ‘ Before closing, validate > > The application appears in the Applications list, the users column shows the access, the Working directory points to the correct root, and the Executable path to the correct executable. ### Conclusion Publishing an application is about linking two worlds: the software installed on the server and its entry in the panel. If it's not in the Marketplace, you install it manually by connecting via RDP; if it is, you use its automated installation. In both cases, the part that matters most in the process 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.](/docs-en/productos/remote-desktop/how-to/how-to-bulk-upload-users.md) * Review the printing modes of the environment at [Printing.](/docs-en/productos/remote-desktop/details/printing.md) * Manage the rest of the environment from [How to manage your Remote Desktop environment.](/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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-install-and-publish-an-application.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.