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. For 32-bit (x86) it's UniversalTermsrvPatch-x86.exe and for 64-bit (amd64) it's UniversalTermsrvPatch-x64.exe. Step 3: Note While the patch program will automatically create a backup of the Termsrv.dll file, to be cautious you can manually save a copy yourself. Here you can download file ConcurrentRDPPatcher. 2shared gives you an excellent opportunity to store your files here and share them with others. Join our community just now to flow with the file ConcurrentRDPPatcher and make our shared file collection even more complete and exciting.
Windows 10 Rdp Patcher
Learning has never been so easy!
Microsoft offers the Remote Desktop Protocol (RDP) in Windows to allow remote desktop connections, and while most versions of Windows include a RDP client, only the Professional, Ultimate and Server editions offer the RDP server to accept incoming connections.
Unlike server editions of Windows, Microsoft limits the client editions of Windows to one concurrent user, whether remote or local. So if a remote desktop connection is made, no one physically at the PC can use it or even see the desktop without first kicking off the remote user.
However, we'll discuss how you can remove this limitation so that multiple users can log in simultaneously. Thus a remote user(s) can log in to their account while also allowing a local user to log in to their account when physically at the PC.
Concurrent Rdp Patcher Windows 10
This limitation can be bypassed by applying an unofficial modification called the Universal Termsrv.dll Patch, which is provided by a developer who goes by the handle DeepXW:
Find the patch program you should run based upon your processor. For 32-bit (x86) it's UniversalTermsrvPatch-x86.exe and for 64-bit (amd64) it's UniversalTermsrvPatch-x64.exe.
Step 3: Note
While the patch program will automatically create a backup of the Termsrv.dll file, to be cautious you can manually save a copy yourself. You'll find the file at WindowsSystem32, and to undo the Registry changes it makes, you can save the .reg file that's included with the download and manually edit the Registry to remove the changes shown in the .reg file. For Windows XP you'll want to save the xp.reg file, and for Windows Vista and 7 its vista.reg.
Step 4: Install
Right-click on the patch program and select to Run as administrator.
Step 5: Registry Change
On the program, click the Patch button and it will replace the Termsrv.dll file and perform the Registry modification. It will also save a backup so you can later undo the modification if desired.
Step 6: Restart
Next, restart your computer for the modification to take effect.
Step 7: Enable RDP
Right-click on Computer from the Start Menu and select Properties.
Step 8: Remote Settings
Click Remote settings on the left.
Step 9: Select Option
Under Remote Desktop, select one of the three options.
Step 10: Add Users
Administrators on the computer will automatically be added to the list of remote users, but if you need to add standard users, click Select Users.
Windows should automatically configure Windows Firewall to allow the RDP traffic to pass through, but if you have a third-party firewall installed on the PC, you may have to manually configure it to allow the traffic.
As with normal remote desktop connections, remember that to remotely connect over the Internet you must configure your router to forward incoming RDP connections to the desired PC. And unless you perform other RDP settings modifications to change the RDP ports in the Windows Registry you're basically limited to configuring one PC on the network for incoming connections via the Internet.
References
How to Enable Concurrent Remote Desktop Sessions in Windows
0 Comments
If you have never used concurrent remote desktop to support your Windows clients, this post is about to make your day! Concurrent remote desktop can allow you, as an admin, to interactively use a client OS while the main user is still actively logged in.
I’ve written about concurrent remote desktop before. The method that I used five years ago is completly different than the method that I prefer now.
Where the old version was a cumbersome and very OS version specific, this newer method is simple and scalable. With more than two million downloads, it also has a wide user base to provide some support. Today, we are going to deploy RDPWrapper in about ten minutes.
Start by downloading these two files:
Place the MSI on a network share and deploy it with Group Policy / SCCM / etc. As a general rule, do not deploy it to any computer where the primary user remotes in as it can lead to some strange session issues. For example, I deploy this MSI to my student and teacher machines, but I do not deploy it to IT computers. If you have used an alternative CRDP method in the past, you will want to ensure that the original termsrv.dll file is restored to the computer.
Once the MSI is installed, you’ll see just two new files in Program FilesRDP Wrapper. RDPWrap.dll sits between terminal services and provides concurrent use abilities. RDPWrap.ini contains the instructions and support for each client OS.
If you scroll to the bottom of RDPwrap.ini, you will see that it does not have information for the latest Windows 10 versions. That information is stored in the rdpwrap-master.zip file that you downloaded earlier.
Open the rdwrap-master.zip file and navigate to the res subfolder. Copy the rdpwrap.ini from that folder to your network share. Deploy it to your clients to enable support for the latest Windows 10 versions. Personally, I use Group Policy File preferences to deploy the ini file.
Set the preference action to replace and use Item Level Targetting to ensure that the newer file replaces the default file. While you are in the common options tab, set the preference to just apply once.
When future Windows 10 client versions are released, just grab the updated INI file and deploy it. It really is that easy! To test RDPWrapper, reboot the client machine and log on to that computer as a standard user. From your admin machine, launch a remote desktop session to that computer and you should be able to log on as well. If you open taskmgr, you should see that two users are actively logged in.
In the game Civilization, there is a quote that says, “Don’t reinvent the wheel. Just realign it.” At times, it might seem silly to go back and find another solution to the same problem. Those realigned solutions, such as using RDPWrapper, are simply so much better!