Iwn10 Non-server version in multiple users login, even if not the same user will let the current user offline online many methods are to first modify the group policy, and MY win10 version does not have those tutorial related items can be set later found this blog, can be used for reference solution reference this blog, Link blog.csdn.net/u010804317/ here… If reprint infringement, please contact me to delete reprint content as follows:
Windows10 2004 version is now supported!! Go straight to the update at the bottom of this article!!
Windows10 1909 version is supported!!
When it comes to implementing multi-user remote desktop connections on non-Windows Server versions, we all know about the well-known RDP Wrapper Library, but what do we know about it?
Sometimes what we think is a problem is not a problem at all!
Why do I say that? RDP Wrapper Library is an open source software, all secret authors are not kept, all problems are written clearly on GitHub, thanks to these great people!
Open the project on GitHub (github.com/stascorp/rd…) The first page reads that the latest version is V1.6.2. The last update was in December 2017, and now it’s 2020. Actually, no, but the project is almost perfect now. In the last version, the author split the software, separated the core module and the configuration file. By modifying the configuration file, the software can support the latest version of Windows. As long as one person updates the configuration file and upload or shares it to GItHub, then everyone who uses this version of Windows can use the configuration file directly. How convenient! In fact, if you look at the Issue of this project, we do! Long live sharing! It is this excellent design, so the author has not updated it!
What is the principle of this software? (From the project’s GitHub website, important, this is the core of this article)
RDP Wrapper works as a layer between Service Control Manager and Terminal Services, so the original termsrv.dll file remains untouched. Also this method is very strong against Windows Update.
To put it simply, RDPWrapper is an additional layer between the service control manager and the terminal service, or it is like a pipe that connects the service control manager and the terminal service, enabling concurrent RDP sessions (multi-user simultaneous remote desktop) in this layer. So it leaves the original termsrv.dll unchanged and does not make any changes to it, thus ensuring the stability of Windows, which is designed to handle Windows updates well.
RDP Wrapper does not patch termsrv.dll, it loads termsrv with different parameters.
RDPWrapper does not modify termsrV.dll, it loads termsrV.dll with different parameters.
So our question is: for the x version of Windows, we want to support multi-user remote desktop, after searching and trying to download a lot of software, RDPWrapper is not supported, how to do? Urgent, online wait! This is not a problem at all. First, look at our own version of Termsrv. DLL for Windows, then go to GitHub to find the configuration file for the RDPWrapper version or how to modify it (you must be sure you are not the only one), modify the configuration file, run RDPWrapper, OK!
How are configuration files updated?
So what is a configuration file and what’s in it?
In the second step of the following detailed steps, you need to install RDPWrapper by executing install.bat. Two Files will be generated under C: Program Files\RDP Wrapper: DLL (core module), rdpwrap.ini (configuration file), yes, this is the configuration file we need to modify.
OK! Long story short, speed speed! Let me get straight to it. Look at the contents of this configuration file, visible PatchCode, visible NOP, jump, familiar EDX, eax, all assembly, x64 and x86 is not what I need to say, point to the end. Also have a look at [10.0.17763.1-slinit] this part of the content, do you understand?
Well, as if nothing said, there is no way to speak clearly, only pull source code, but sorry I don’t have so much time, I dish very, there are a lot of things to learn, the most important thing has been mentioned above, interested friends to pull source code analysis, I tasted it.
Summary (the following content without in-depth analysis of the source code, all is my guess, look at the line, do not take it seriously, the most important thing is, do not come to me to verify, I am ignorant! :
If I am not mistaken, RDPWrapper puts the core function module implementation in rdpwrap.dll, which is the layer mentioned in the software principle (pipe), and hooks termsrv. DLL by loading the configuration file rdpwrap.ini. RDPWrapper does not modify termsrv. DLL, which loads termsrv. DLL with different parameters, and as I mentioned earlier, software split, which separates the core module from the configuration file. By modifying the configuration file rdpwrap.ini, the software can support the latest version of Windows. This involves assembly, Hook technology, Dll technology, I won’t go into the details.
So, the most important thing right now is the configuration file. Everything else is not important to us. Let’s look at this:
[
10.0.
17763.1-slinit] RDPWrapper can support termsrv. DLL version number bInitialized. X86 =CD798 x86 which is targeted at32X86 =CD7A0 bappServerallowed. x86= CD7A8 bremoteconnallowed. x86=CD7AC X86 =CD7B0 ulMaxDebugSessions. X86 =CD7B4 bFUSEnabled. X86 =CD7B8 bInitialized64X64 =ECAB8 bAPPServerAllowed. x64= ECAC0 bremoteconnallowed. x64=ECAC4 bMultimonAllowed.x64 =ECAC8 ulMaxDebugSessions.x64=ECACC bFUSEnabled.x64 =ECAD0Copy the codeIs that clear? RDPWrapper is not supported on Windows termsrv. DLL. It is not supported on Windows termsrv. DLL. What if RDPWrapper does not support the latest Windows10 1909 version? Go to the GitHub of RDPWrapper and look in the Issue to find a configuration code or file similar to the one above provided by someone else, copy it and add it to rdpwrap.ini on our own computer or replace it directly with rdpwrap.ini on our own computer. Bat, OK, off work, friends.
General idea:
First find out what version of TermsrV. DLL is on your computer or the machine you want to implement a multi-user remote desktop. (Regardless of the version of Windows on your computer, RDPWrapper is for termsrV. DLL.) Termsrv. DLL is not supported in the current configuration file. If it is not supported, go to GitHub of RDPWrapper and check the Issue. Find the configuration code or configuration file provided by others similar to the above, copy it and add it to the corresponding configuration file rdpwrap.ini on our own computer, or replace the configuration file rdpwrap.ini on our own computer, execute install.bat again, and check again. OK.
Detailed steps :(take my computer above the version of termsrv.dll [10.0.17763.1-slinit] as an example)
1. Download rdpwrap-v1.6.2. zip and decompress it. It contains the following files.
| The file name | describe |
|---|---|
RDPWSTST.EXE |
RDP wrapper library installer/uninstaller |
RDPCHECK.EXE |
Local RDP inspector (can check that RDP is working) |
RDPCON.EXE |
RDP wrapper configuration |
| install.bat | Quickly install batch files |
| uninstall.bat | Quickly uninstall batch files |
| update.bat | Update batch files quickly |
DLL (core module) and rdpwrap.ini (configuration file) will be generated under C:\Program Files\RDP Wrapper.
RDPWrapper supports the termsrv. DLL version of your current computer. If the RDPWrapper does not support the termsrV. The current configuration file does not support this version of termsrv.dll.
4. Go to the GitHub Issue of RDPWrapper and search for the corresponding version number to find the configuration code that supports the [10.0.17763.1] version provided by others. Add to the rdpwrap.ini configuration file located under C:\Program Files\RDP Wrapper\rdpwrap.ini. Of course, if someone provides a new version of the configuration file, just replace it. As a reminder, the configuration code must be formatted correctly, as described in the previous analysis section.
In this case, the following configuration code was found in GitHub and added to the rdpwrap.ini configuration file.
X86 =CD798 bserversku. x86 =CD79C lMaxUserSessions. X86 =CD7A0 bappServerAllowed.x86 =CD7A8 bRemoteConnAllowed.x86=CD7AC bMultimonAllowed.x86 =CD7B0 ulMaxDebugSessions.x86=CD7B4 bFUSEnabled.x86 =CD7B8
bInitialized.x64 =ECAB0
bServerSku.x64 =ECAB4
lMaxUserSessions.x64 =ECAB8
bAppServerAllowed.x64 =ECAC0
bRemoteConnAllowed.x64=ECAC4
bMultimonAllowed.x64 =ECAC8
ulMaxDebugSessions.x64=ECACC
bFUSEnabled.x64 =ECAD0
5. Run rdpconf. exe again to check whether rdpconf. exe is supported.
Not yet, there are still some computer local policies that need to be modified, as well as some issues and optimizations, such as maximum number of connections prompt when connecting? How to optimize remote desktop performance to automatically log out users? And basically, how do you create users? How do I replace the system file termsrv. DLL? Almost every problem you can have is written in detail. Check out my other blog post! (blog.csdn.net/u010804317/…).
I have not updated the configuration file on GitHub for the latest Version of Windows or RDPWrapper. What should I do? Always waiting? In this regard, I just want to say that this problem can be solved with money!
Throw the king directly to everyone:
Think of one of Windows’ enduring strengths, backward compatibility! Did you get it? The remote desktop module has been running for many years, and the bugs and bugs have been fixed for a long time. The latest Version of TermsrV. DLL in Windows is almost identical to the last version of TermsrV. DLL, and even the one before that. We can use a lower version of termsrv. DLL to replace the latest version of termsrv. DLL on the machine, of course, everything has to be a measure, the two file versions should not be too different. As long as the remote desktop works properly after the replacement, and someone on GitHub must have solved the problem, so the problem is solved. See my other blog for details! (blog.csdn.net/u010804317/…). .
Gentlemen, is this method 6?
Because this method is, after all, replacedTermsrv. DLL, may cause system instability! Attention! Attention! Attention! I am not responsible for any loss caused by this!
Attention! It’s a different approach! Not the way! For the standard easy way, see the blog post above! Direct use of RDPWrap this software, the execution of bat files, automatic crack into the patch can be perfect solution, very simple.
1. Finally, a successful screenshot that everyone loves! As for the screenshot of the RDPWrapper wrapper, it’s just a click away. It’s too easy.
Note the details. In the first image, Windows has been upgraded to the latest Version of Windows10 1909. This version of Termsrv. DLL is 18362.267 and dated 2020/01/03. I will directly replace the termsrv. DLL of the previous Windows version, which is 1773.1 in Windows10 1809 version. The time is 2018/09/15. Look at the second picture, OK! There is no problem in use, as steady as an old dog!
2. About the update support Win10 2004 version of the successful screenshots
Note the details, Windows has been upgraded to the latest Windows10 2004 version, this version of termsrv.dll is 10.0.19041.84, 2020/05/31, stable as an old doge!
For resource questions, RDPWrapper software and the latest configuration file rdpwrap.ini supporting the latest Windows version can be found on GitHub website (github.com/stascorp/rd…). Download. If you need termsrv.dll[10.0.17763.1] and the latest rdpwrap.ini please comment on my private message, thanks ~!