- Windows Multiple Remote Desktop
- Cara Setting Remote Desktop Multi User Windows 10
- Windows 10 Pro Multi User Remote Desktop
- Windows 10 Multiple Remote Users
- Windows 10 Enterprise Multi Session
- Enable Multi User Remote Desktop Windows 10
Remote Desktop is great for connecting to a Windows computer from another part of the network. You can get access to local drives, printers, files, etc. as if you were sitting in front of it. While this is great, an issue arises when you have multiple computers on a network that you want access to from outside the network. Access from the inside is granted to every client with RDP enabled, but when you are outside the network and operating through a router, for example, connecting via RDP is only natively available for one computer. This is because all the computers in the network are using the same RDP port.
WVD helps deliver the best virtual desktop experience by providing remote access to modern desktop and applications from any device. Combined with Microsoft 365 and Azure, it offers users a multi-session Windows 10 and Microsoft 365 Apps for enterprise environment. Windows Virtual Desktop offers users a more secure computing experience that has. Alternative ways to add Remote Desktop users in Windows 10. There are two more ways to add or remove Remote Desktop users in Windows 10. You can use Local Users and Groups snap-in. You can use Local Users and Groups snap-in if your Windows edition comes with this app. Press Win + R shortcut keys on your keyboard and type the following in the. Use the Remote Desktop Client to Access Windows 10 Computers. If you used Remote Desktop on Windows Vista, 7, or 8.1, the Remote Desktop Client is the program you’ll recall using. If the newer Remote Desktop App doesn’t work for you, give the old client a try, and vice versa. The old client still comes with Windows 10.
The issue with multiple Remote Desktop Sessions on Windows 10 and 8. Attempting to initiate a second Remote Desktop session will cause any users working locally on the machine or logged in through an existing RDP session to be kicked out. The issue is not a result of the technical capabilities of Windows 10 but rather with the license agreement. On your local Windows 10 PC: In the search box on the taskbar, type Remote Desktop Connection, and then select Remote Desktop Connection. In Remote Desktop Connection, type the name of the PC you want to connect to (from Step 1), and then select Connect. On your Windows, Android, or iOS device: Open the Remote Desktop app (available for free.
Consider this: Your desktop is set up for remote connections via the default RDP port. You’re at a friends house and you need access to your desktop. You would connect as usual, implicitly defining the default 3389 port. Your router at home is set up to forward these remote requests to your desktop. All is well until you need access to your laptop. The natural idea would be to define another rule in the router to forward another RDP request to the laptop. This is impossible, however, to have the router forward RDP requests to two computers without defining a different port between the two.
This is why we have to then explicitly create a new RDP port on the laptop, make the changes necessary for the router, and then you’ll be able to connect to either the laptop or desktop without issue.
Let’s see how that’s done.
Change the RDP Port Number in the Registry
Step 1. Find Regedit from the Start menu to open the Registry Editor.
Navigate through the folders on the left to find the RDP-Tcp folder in this path:
HKEY_LOCAL_MACHINESYSTEMControlSet001ControlTerminal ServerWinStationsRDP-TcpWe’re looking to change the DWORD (32-bit) Value for PortNumber.
It’s best to save yourself from possible future issues by backing up your registry. See how to backup your registry here.Step 2. Double click PortNumber in the right pane and then select Decimal for the Base type. Selecting Hexadecimal would require you to know the equivalent hex value of the common decimal value.
The default value is 3389 but you can change it to anything you like. I find it useful to modify the digits up or down by only one value at a time for easy recall.
Note: If your ultimate plan is to make RDP port number changes to multiple computers on your network, it’s best to write down the computer and port number for later reference. These steps are the same for every computer you need to modify.Allow the Port Through the Firewall
The port has been set so now we need to let the Windows Firewall know it’s a safe port to communicate through. By default, 3389 is allowed but since we’ve changed it, we need to make this firewall change as well.
Step 1. Search for Windows Firewall in the Start menu and click on Windows Firewall with Advanced Security.
Step 2. Right-click Inbound Rules and choose New Rule.
Step 3. We need to go through this wizard to finish the addition of this rule. Select Port on the first step, then continue to the Protocols and Ports page.
Choose TCP and then enter the port you chose in the registry next to Specific local ports.
Click Next and choose Allow the connection in the Action window. The next page is for selecting the profiles in which this port should be allowed on. These will change according to your desire and necessity. I’ve kept all of these checked for myself.
The final step is to name the new rule. It’s helpful to indicate what this rule is for if you ever need to modify it in the future.
Follow these same steps on every machine that is undergoing the RDP port change.
Assign the Port Through the Router
Now that the port is set up and allowed through the firewall, the next task is to point the new port number to the specific internal IP address so that outside requests are understood properly.
Step 1. Open your router’s configuration page. Ours is http://192.168.1.2.
Step 2. Look for a Single Port Forwarding section like we did when setting up an FTP server.
Step 3. Enter a descriptive name for identifying the computer as well as the port number from the registry change.
For example, we’ve entered Desktop to indicate my computer and the External Port and Internal Port sections are filled in with the port number we changed above: 3388.
The local IP address is required for the destination address on the right, as seen in the above image. Find your local IP address by opening Command Prompt from the Start menu and entering ipconfig. Find the IPv4Address of each computer and assign it to the port number and description in the router accordingly.
Connecting With the New Port
When the port is changed, connecting to the remote computer via Remote Desktop is a tad different. By default, the port 3389 is used and therefore no extra text is required when connecting. Because we’ve changed this port, however, we also have to change the way we connect.
With Remote Desktop open, you’ll need to enter the computer name in this format:
COMPUTER:PORTHere are some examples from the port numbers we have changed and reflected in the router:
REMOTESERVER:3388SERVERNAME:3387
COMPUTER:3386
REMOTESERVER, SERVERNAME, and COMPUTER will be the name of the computer you’re connecting to.
Conclusion
These instructions are vital for anyone wanting to access their computer on a network with other RDP clients already configured. Set these up and you’ll be able to access all your home laptops and other computers remotely, from anyone’s network.
The above article may contain affiliate links which help support Guiding Tech. However, it does not affect our editorial integrity. The content remains unbiased and authentic.
Read Next
Windows Multiple Remote Desktop
How to Enable Remote Desktop in Windows 8
Learn How to Enable Remote Desktop in
Option 1 - Modifying termsrv.dll
To have concurrent user sessions working in Windows 10, you need to make small changes to termsrv.dll file. This file is located in C:WindowsSystem32 folder. Before modifying termsrv.dllfor the first time, you need to take ownership and assign yourself full permissions. You also need to stop Remote Desktop service (TermService) if it's running.
DLL files can be modified using any HEX Editor (for example Tiny Hexer). You can do this yourself by replacing strings shown below, or just download patched versions from this page.
Cara Setting Remote Desktop Multi User Windows 10
Windows 10 x64 v2004 - May 2020 Update (20H1)
After this update termsrv.dll is upgraded to version 10.0.19041.84 To get back concurrent remote desktop connections, make the following changes:
Find:
39 81 3C 06 00 00 0F 84 D9 51 01 00
replace with:
B8 00 01 00 00 89 81 38 06 00 00 90
The patched version can be download from here. The original, v10.0.19041.84 file can be found here.
Older Windows 10 versions
-----------------------------------------------------------------------------------------------------------------------------
Windows 10 x64 v1909 - November 2019 Update
After this update termsrv.dll is upgraded to version 10.0.18362.657. To get back concurrent remote desktop connections, make the following changes:
Find:
39 81 3C 06 00 00 0F 84 5D 61 01 00
replace with:
B8 00 01 00 00 89 81 38 06 00 00 90
The patched version can be download from here. The original, v10.0.17763.1 file can be found here.
-----------------------------------------------------------------------------------------------------------------------------
Windows 10 x64 v1903 - May 2019 Update
After this update termsrv.dll is upgraded to version 10.0.18362.53. To get back concurrent remote desktop connections, make the following changes:
Find:
39 81 3C 06 00 00 0F 84 5D 61 01 00
replace with:
B8 00 01 00 00 89 81 38 06 00 00 90
The patched version can be download from here. The original, v10.0.17763.1 file can be found here.
-----------------------------------------------------------------------------------------------------------------------------
Windows 10 x64 v1809 - October 2018 Update + Cumulative April 2019 Update
After this update termsrv.dll is upgraded to version 10.0.17763.437. To get back concurrent remote desktop connections, the make the following changes:
Find:
39 81 3C 06 00 00 0F 84 3B 2B 01 00
replace with:
B8 00 01 00 00 89 81 38 06 00 00 90
The patched version can be download from here. The original, v10.0.17763.437 file can be found here.
-----------------------------------------------------------------------------------------------------------------------------
Windows 10 x64 v1809 - October 2018 Update
Windows 10 October 2018 Update (1809) updates termsrv.dll to version 10.0.17763.1. To get back concurrent remote desktop connections, the make the following changes:
Find:
39 81 3C 06 00 00 0F 84 7F 2C 01 00
replace with:
B8 00 01 00 00 89 81 38 06 00 00 90
The patched version can be download from here. The original, v10.0.17763.1 file can be found here.
-----------------------------------------------------------------------------------------------------------------------------
Windows 10 x64 v1803 - Spring 2018 Update (March 2018)
Windows 10 Spring 2018 Update (1803) updates termsrv.dll to version 10.0.17134.1. To get back concurrent remote desktop connections, make the following changes:
Find:
8B 99 3C 06 00 00 8B B9 38 06 00 00
replace with:
B8 00 01 00 00 89 81 38 06 00 00 90
The patched version can be download from here. The original, v10.0.17134.1 file can be found here.
-----------------------------------------------------------------------------------------------------------------------------
Windows 10 Fall Creators Update (1709 - Redstone 3)
Updates termsrv.dll to version 10.0.16299.15. To get back concurrent remote desktop connections, make the following changes:
Find:
39 81 3C 06 00 00 0F 84 B1 7D 02 00
replace with:
B8 00 01 00 00 89 81 38 06 00 00 90
The patched version can be download from here. The original, v10.0.16299.15 file can be found here.
-----------------------------------------------------------------------------------------------------------------------------
Windows 10 x64 v1703 - Creators Update (April 2017)
Windows 10 Creators Update (1703 - Redstone 2) updates termsrv.dll to version 10.0.15063.0. To get back concurrent remote desktop connections, make the following changes:
Find:
39 81 3C 06 00 00 0F 84 53 71 02 00
replace with:
B8 00 01 00 00 89 81 38 06 00 00 90
The patched version can be download from here. Original, v10.0.15063.0 file can be found here.
-----------------------------------------------------------------------------------------------------------------------------
Windows 10 x64 Threshold 2 (November 2015)
Windows 10 Fall Update (also called 'Threshold Wave 2 Update') updates termsrv.dll to version 10.0.10586.0. To get back concurrent remote desktop connections, make the following changes:
Find:
39 81 3C 06 00 00 0F 84 3F 42 02 00
Windows 10 Pro Multi User Remote Desktop
replace with:
B8 00 01 00 00 89 81 38 06 00 00 90
The patched version can be download from here. Original, v10.0.10586.0 file is here.
-----------------------------------------------------------------------------------------------------------------------------
Windows 10 x64 RTM (August 2015)
termsrv.dll file version 10.0.10240.16384.
In termsrv.dll find:
39 81 3C 06 00 00 0F 84 73 42 02 00
and replace it with:
B8 00 01 00 00 89 81 38 06 00 00 90
The patched version can be downloaded from here. The original, untouched version of termsrv.dll v10.0.10240.16384 can be downloaded from here.
Option 2 - RDP Wrapper
Instead of modifying termsrv.dll file you can use RDP Wrapper which acts as a middleman between Terminal Services and Service Control Manager. This way you don't need to touch termsrv.dll file. Actually, if you already modified your termsrv.dll file, you need to revert to the original version before using this method.
Download and extract RDPWrap-v1.6.1.zip (or newer), then run install.bat as admin. After installation is completed, run RDPConfig.exe. If all items under Diagnostics are green, you should be good to go.
If 'Listener state' is 'Listening [not supported]', you will need to update the wrapper's configuration (.ini) file.
Windows 10 Multiple Remote Users
With the latest version of RDP Wrapper you no longer need to update rdpwrap.ini manually. Simply run update.bat and everything will be done automatically.
If update.bat doesn't add support to your Windows version, try checking Open Issues on RDP Wrapper GitHub page. You may find how to manually update rdpwrap.ini until official support is added.
Windows 10 Enterprise Multi Session
May 2017
Windows 10 64bit
Enable Multi User Remote Desktop Windows 10