---
title: "How to register a RemoteApp"
slug: "pam-session-how-to-register-a-remoteapp"
updated: 2026-11-03T14:47:50Z
published: 2026-11-03T14:47:50Z
canonical: "docs.senhasegura.io/pam-session-how-to-register-a-remoteapp"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.senhasegura.io/llms.txt
> Use this file to discover all available pages before exploring further.

# How to register a RemoteApp

This document provides information about a step-by-step guide on how to configure a **RemoteApp** on Segura™.

## Requirements

- Be a user with the role of a system administrator, pam administrator or pam operator.

---

## Register RemoteApp

1. On Segura™, in the navigation bar, hover over the **Products menu** and select **PAM Core**.
2. In the side menu, select **Management** > **Sessions** > **RemoteApp**.
3. On the report screen, on the actions menu click **Add**. To change an existing RemoteApp, on its actions column click **Edit**. The fields and instructions are the same on both screens.
4. In the **RemoteApp** registration screen fill in the fields:
  1. **Name***: choose a name for this RemoteApp registration.
  2. **Tags (Comma separated)**: if you wish, create tags to identify the registration.
  3. **Application path**: type the path of the application to run.
  4. **Parameters**: enter the parameters.
  5. **Script**: preview of how the script runs with the actions you selected and their values. To build the script, use the **Actions** and **Properties** fields.
  6. **Description**: if desired, enter a description.
5. To publish this RemoteApp through a Remote Desktop Connection Broker, go to the **Connection Broker settings** section and enable **Connection Broker**. The section displays the remaining fields only after you enable it.

Review your **Application path** and **Parameters** values before you continue. With **Connection Broker** enabled, Segura™ sends the application and its arguments as separate values instead of a single command, so a registration that worked before may need adjusting.

Attention

Segura™ does not validate the values in the **Connection Broker settings** section and saves an incorrect value without any warning. The failure appears only when the operator starts the session.
  1. **Load balance info**: enter the routing information the broker uses to place the session on the correct collection host, in the format `tsv://MS Terminal Services Plugin.1.<Collection_Name>`. Replace `<Collection_Name>` with the name of your session collection. For example: `tsv://MS Terminal Services Plugin.1.Collection01`.
  2. **Remote app directory**: if desired, enter the working directory for the application.
  3. **Advanced options**: to send a custom setting to the remote session, click **+ Add** and complete the **Parameter** and **Value** fields of the new row. Repeat for each setting you want to send. To delete a row, check its checkbox and click **Remove selected**.
6. Click **Save**.

## Related topics

Segura™ saves the RemoteApp, but operators cannot use it yet: you still need to configure a credential to use this RemoteApp. More information in [How to configure a session for use with RemoteApp](/v4-2/docs/pam-session-how-to-configure-a-session-for-use-with-remoteapp).

When **Connection Broker** is disabled, the RemoteApp keeps the previous connection behavior. Registrations created before this field existed continue to work without any change. More information in [About RDP RemoteApp](/v4-2/docs/pam-session-about-rdp-remoteapp).