RDP Manager Walkthrough


RDP Manager is an advanced feature that allows for full administration of Windows Remote Desktop Protocol, or RDP, a feature built into Windows that allows for remote desktop connections. The RDP Manager in LuminosityLink enables complete administration of Windows Remote Desktop Protocol, including multiple sessions under the same user, creating and managing Windows User Accounts, and more.

You may find more information about Remote Desktop Protocol here: https://en.wikipedia.org/wiki/Remote_Desktop_Protocol

Installing RDP Manager

To begin, open Luminosity RDP Manager by going to Machine List, right clicking a client, and going to Networking –> RDP Manager.

The first step to using the RDP Manager is to install the RDP Manager onto your client. This process is simple, although it does require administrator privileges. If you do not have administrator privileges, you may request administrator privileges by selecting “Request Admin Rights”. To install RDP Manager, simply click “Install RDP Manager” within the Luminosity RDP Manager (pictured above.) The installation process should take less than 60 seconds.

Managing Windows User Accounts

Windows RDP uses standard Windows accounts to manage users. After installing the RDP Manager, you will be able to login to an existing account under a new session, allowing for complete administration of your clients PC. This doubles as allowing you to use a single PC/workstation for numerous tasks.

Within the accounts tab, you have multiple options. They are:

-Add New Account: Creates a new administrator account with the specified username and password
-Change Password: Changes the password of an existing windows account
-Remove Password: Removes the password on an existing windows account. In addition, this enables RDP permission on the account.
-Delete Account: Removes an existing windows account entirely

Note: As of version 1.5.4, you can login to an account that does not have a password.

Connecting via Windows Remote Desktop

Now that you have installed RDP Manager and have an account ready to connect to, you are ready to connect to your clients PC through Remote Desktop Connection. However, note that RDP Connections take place through port 3389. If your client does not have port “3389” open, you must use the reverse proxy in LuminosityLink to properly connect. This tutorial will walk you through both scenarios – port 3389 is open on your client, and port 3389 is closed on your client.

Port 3389 is open

This works if you have forwarded 3389 on your clients PC, or the client PC is a PC on your local network. If your client is on your own network, you will be able to connect directly. I will be connecting to my local PC under the IP Address of “”. To connect, simply open Windows Desktop Connection, type in the computers IP Address, and click “Connect”. You will be prompted for credentials. Type in the credentials for the user account you wish to connect to — see the above “Managing windows User Accounts” for more information.

Port 3389 is closed

If your client does not have port 3389 open, you must use the Reverse SOCKS feature to administrate the clients network. From here, you can connect via Remote Desktop. However, this process is tricky, so be sure to read the full walkthrough to obtain a good understanding of the process.

To begin, you must start the SOCKS 5 Proxy server on your client. You may start the SOCKS Proxy by going to the “Advanced” tab within RDP Manager, and clicking “Start SOCKS Proxy”:

For the purpose of this tutorial, we will be using a third party application called “Proxifier” to enable the SOCKS 5 Proxy on Remote Desktop Connection, in order to connect to the client.

You may download Proxifier here: https://www.proxifier.com/download.htm

After downloading and installing Proxifier, open the software and click the “Proxy Servers” button at the top left:

On the window that appears, click “Add”

A Window to add a proxy server will appear. We’ll want to add the SOCKS 5 Proxy for our client within LuminosityLink. Go to Networking –> SOCKS 5 in LuminosityLink, find your client, right click the entry and select “Copy IP:PORT”. Now, paste or type in the IP and Port within Proxifier’s Proxy Server Settings. Be sure to select “SOCKS Version 5” within Proxifier, and keep Authentication disabled:

Click “OK”. You will be prompted to use this proxy by default. Hit “Yes”.

Your Proxy Servers Window should look something like below. The port is unique to your client. The address should be “”, and the Type “SOCKS5”.

On the above window, click “OK”.

Now, within Proxifier, navigate to Profile –> Proxifier rules (at the top):

On the “Proxification Rules” Window that appears, click “Add..” (Pictured Below)

We are going to create a rule for Remote Desktop Connection. On the “Proxification Rule” window that appears, type in “RDP Manager” under name. Ensure “Enabled” is checked. Within the “Applications”, type in “mstsc.exe“. This is the Remote Desktop process. Keep Target hosts and Target ports to “any”. At the bottom, under “Action”, select “Proxy SOCKS 5”.

Click “Ok” to close the Window.

We are now going to make a small adjustment to the “Proxification Rules” Window. Under the “Default” Rule Name, change the Action to “Direct”. In addition, you may remove the default “Localhost” rule. Your Proxification Rules should look like the window below:

Click “OK”. We are now ready to begin connecting.

Open Remote Desktop Connection. Within the Computer field, type in “”.

Click “Connect” and type in your credentials as you normally would. If any warning messages appear, click “Yes”. You will be connected shortly after!


Official LuminosityLink Blog

Get the latest news, updates, and tutorials on how to get the most out of LuminosityLink.

Need Assistance?

Support is provided free to all customers. You may email us for pre-sale questions, support, and licensing inquiries.

Subscribe to our newsletter!

Fields marked with an * are required

More from our blog

See all posts
    • Putin
    • December 22, 2016

    Just wondering..in the proxification rule window, what matters is what ‘Rule Name’ is checked, right? even if i decide not to delete the localhost.

      • Administrator
      • December 22, 2016

      I believe unchecking the rule disables it. You need to enable the rule set for mstsc.exe as the tutorial shows.

    • Vlad
    • December 16, 2016

    How to setup that Proxifier use client IP only for mstsc.exe and all another my processes are working with my ip. I hope you understood what i mean.

      • Administrator
      • December 16, 2016

      This tutorial covers that. Look at the “Proxification Rule” part of the tutorial.

Recent Posts


Leave a Comment