Connecting to multiple RDP servers using a single Network Resource

Introduction

A common requirement when using RDP via a VPN is that you may wish to allow users to connect in to their own personal desktops in the office.

Ordinarily, this would mean that you would then have to create one Network Resource for every single user, which can very quickly cause some considerable administrative overhead.

This article explains how you can use Profile Attributes to create a single resource which will connect to each user's separate workstation.

 

1. Create a Profile Attribute

In the Hypersocket UI, as the admin user navigate to Access Control->Profile Attributes and click on the Custom Attributes tab. Click Create.

 

First, we are going to create a category to place this new attribute in. In the Attribute window that appears, click the Create Category button. Give this new category a name (in this case we'll call it RDP) and click Create.

 

Give the attribute a Name. In the category, start typing in the category name then select it from the list that appears.

Change the Type to Text, then enter a value for the Variable Name - this will be the internal name for the attribute and should be entered without any spaces. Lastly, type in a Description for the attribute which will be displayed to users.

 

 

Click the Options tab. Here you can set the Scope to either User or Admin, depending on if you want to define this attribute for users or allow them to set the value themselves. Here we will set the Scope to User.

 

Select the Roles tab and add the roles who will be given access to this attribute, then click Create to finish creating the attribute.

 

2. Create an Application resource

Now we can create an Application resource in Hypersocket.

Navigate to Network->Applications and click Search Templates.

 

Select the Microsoft RDP (Windows) template (assuming your users are using Windows clients - you can also create an application for OSX too). Click Next.

 

3. Create an Endpoint resource

Now navigate to Network->Endpoints and click Create.

Give the resource a name, here we've called it My Computer. For the Hostname, we can type in anything as this will be intercepted by the Hypersocket Client. In this case, every user's client will appear to be connecting to a host called mycomputer.

For Destination Host/IP, we need to type in the internal name of the hostname attribute created earlier, but in a special format. Our attribute is called myComputer, so we need to type in ${myComputer}.

 

Select the Protocols tab and add the RDP protocol.

Select the Applications tab and add the Microsoft RDP (Windows) Application we created earlier.

 

Select the Roles tab and add the roles who will be given access to this resource, then click Create to finish creating the resource.

 

4. Setting the User's attribute

Now before a user can use this resource, they need to have the value of the myComputer attribute set. This can be done in two ways.

 

Admin setting the attribute value

The admin can set the value of the attribute for a user directly. To do this, navigate to Access Control->Users and click the Edit icon next to a user account you want to change.

 

Click the Custom link in the user's account, the display updates to show the custom profile attribute we created. Set the hostname or IP address of the user's RDP target here then click Update to save the change.

User setting the attribute value

Because we set the attribute scope to user in this example, the user can set their own hostname. To do this log on to the Hypersocket UI as the user account, then navigate to My Profile, then click the RDP tab.

The user can then enter their hostname or IP address and click Apply.

 

5. Testing the resource

Launch the Hypersocket Client and connect to the server as a normal user.

As we called the Endpoint Resource 'My Computer', this appears in the list as an icon called MC. Click this to launch the application.

 

The RDP client then launches and connects to the user's own desktop

Have more questions? Submit a request

Comments