Administrator Guide
  1. APPLICATIONS
  2. RDP

Adding an RDP Application

An RDP profile allows the deployment of Remote Desktop Connection settings to users.

📘

Important

Axis Security recommends allowing application traffic through the firewall by port number, when possible, to avoid incorrect classification of the traffic by the firewall; for example, if you are using RDP, use port 3389.

Adding an RDP Application:

  1. In the Management Console, click Settings -> Destinations
  1. Click New Application
  1. Under Server Access, select RDP-Remote Desktop Server.
  1. Enter a meaningful Name for the application.

Local Address and Port

  1. Add Domain or IP address. Specify the application’s Local Domain/FQDN/IP address that is visible to the connector from the network segment.
  2. In the Port, ensure 3389 is entered for Remote Desktop. (Note: 3389 is the default Port number.)
  3. Use the Server Type drop-down menu to select a server type.
📘

Note

For legacy servers, use the default server type.

  1. Use the Connector Zone drop-down menu to select a Connector Zone within the same network segment or that has access to the application. For more information about Connector Zones, click here.
  2. Click Next.

Remote Desktop Credentials

  1. Enter the default domain for this remote desktop. Leave it blank if there is none.
  2. Select Allow users to save their credentials in the Axis Cloud for a seamless login to allow the Axis Cloud to remember the users' credentials when they connect to the RDP.
📘

Note

  • Currently this is only relevant for web-based RDP applications.
  • This is a limited release feature.
  1. Click Next.
📘

Note

  • Allow only remote connections with Network Level Authentication (NLA) is a restricted feature that requires support to enable. By default, NLA is enforced, aligning with best security practices.

If you disable Prompt users to log in with their personal desktop credentials you will need to enter the Desktop Username and Desktop Password before clicking Next.

Note

Browser-based RDP sessions treat "${...}" in a credential as a placeholder, not as literal characters. If a predefined password contains "${", followed by letters, digits, or underscores, followed by "}" the login fails with the error message Wrong credentials, please try again.

Recommended – Change the password on the target machine to one that doesn't contain "${...}".
If you can't change it, in the predefined credentials, type one extra $ before each ${. For example, Ab$${x}12! becomes Ab$$${x}12!.

Alternative – Users can connect with their native RDP client through the HPE Networking SSE agent instead of the browser.

Single Sign-On

  1. Use the Identity Provider drop-down menu to select an identity provider that will manage authentication for this application.
  2. Click Next.

Application Tags (Optional)

  1. Tags help create policy rules fast and efficiently for groups of applications. Click here ] to learn about creating application tags.
  2. Start typing to create new tags, or choose from the drop-down menu.
  3. Click Submit.
  1. In the Management Console, click the Apply Changes dropdown and click Commit changes.
  1. Next Steps: Adding an RDP Profile.

Updated about 23 hours ago

What’s Next

Did this page help you?
Copyright © 2025 HPE Aruba Networking SSE. All rights reserved.