---
title: Adding RDP and VNC Hosts and Publishing RemoteApps
description: How to add Windows RDP and VNC hosts to MikroWizard, open them in the browser from the Connection Manager, and publish single applications as RemoteApps.
url: "https://mikrowizard.com/docs/add-rdp-vnc-hosts-publish-remoteapp/"
updated: "2026-10-15"
category: Getting started
---

# Adding RDP and VNC Hosts and Publishing RemoteApps

Browser RDP and VNC are part of MikroWizard Pro 2.1.0 and run on the Terminal Gateway addon v1.3.0 or later. If you haven't installed or updated the gateway yet, see [Installing Terminal Gateway Addon](/docs/installing-terminal-gatway-addon/) and [Updating Terminal Gateway server](/docs/updating-terminal-gateway-addon/) first.

## Add an RDP or VNC host

1. Open **Devices** and click **Add Device**.
2. Under **Connection protocol**, choose **RDP (Remote Desktop)** or **VNC**.
3. Enter the **Device Name** and **IP Address**. The port defaults to 3389 for RDP and 5900 for VNC; change it if the host listens elsewhere.
4. Choose the **Brand / Device Type** and a **Connection Template** (RDP and VNC have their own templates with display and acceleration settings).
5. Enter the **Username** and **Password**. For RDP you can also set an **Active Directory Domain**.
6. Optionally assign the host to device groups, then save.

Several hosts can share one public IP on different ports. MikroWizard treats devices as unique by IP and port, and the protocol badge shows the real port, for example `RDP:3390`.

[![MikroWizard device list with MikroTik, Cisco, Windows and Linux devices and protocol badges](https://mikrowizard.com/wp-content/uploads/2026/10/SCR-0082-devices-multi-protocol-inventory.webp)](https://mikrowizard.com/wp-content/uploads/2026/10/SCR-0082-devices-multi-protocol-inventory.webp)
RDP and VNC hosts in the device list, next to MikroTik and other devices.

## Open a session in the browser

Click **Connection Manager** in the header. RDP hosts are listed under **RDP Hosts (Windows)** and VNC hosts under **VNC Consoles**. Double-click a host to open it in a new tab. Sessions run in HTML5, so nothing needs to be installed on your computer.

[![Browser RDP session to a Windows Server in the MikroWizard Connection Manager](https://mikrowizard.com/wp-content/uploads/2026/10/SCR-0073-pam-rdp-windows-server-session.webp)](https://mikrowizard.com/wp-content/uploads/2026/10/SCR-0073-pam-rdp-windows-server-session.webp)
An RDP session opened from the Connection Manager.

## Publish a RemoteApp

1. In **Devices**, find the RDP host and click **+ App**.
2. Enter an **Application Name**.
3. Keep the launch mode **RemoteApp (Seamless Window)**.
4. Enter the **Application Executable or Alias**: an absolute path, or a published RemoteApp alias prefixed with `||`.
5. Optionally add **Application Arguments** and a **Working Directory**, then click **Publish Application**.

Published apps appear under the host in the device list and under **Applications** in the Connection Manager. They inherit the host's IP, credentials and security settings.

## Control what users can do: session DLP

Open **Terminal Policies** and edit a policy. The **GUI Session Guardrails (Session DLP)** section controls clipboard direction, file transfer, screen watermarking and forensic recording for graphical sessions. Session options resolve in four tiers: template, then host, then published app, then DLP policy.

[![MikroWizard policy editor with session DLP controls](https://mikrowizard.com/wp-content/uploads/2026/10/SCR-0081-pam-session-dlp-policy.webp)](https://mikrowizard.com/wp-content/uploads/2026/10/SCR-0081-pam-session-dlp-policy.webp)
Session DLP settings in a terminal policy.

## Recordings and sharing

RDP and VNC sessions appear in **Active sessions** and **Session history** with a protocol badge. Recordings can be replayed in the browser, and live sessions can be watched or shared like terminal sessions.