

However, if a user disconnects from a session (which means the session is still available on the terminal server) and later attempts to reconnect, the NLB cluster may redirect the user to a different terminal server instance and thus a new session is created on that terminal server. The incoming connections are then automatically distributed to one of the terminal servers in the NLB cluster. Windows 10 Version 1903 (updated v2) Find:įeel free to write the comment if you need any support from my end.Imagine that you have multiple terminal servers and instead of letting users connect to one of them by individual name (which is problematic), you create a Network Load Balanced (NLB) cluster that collects all the terminal servers into a terminal server farm and users connect to the DNS name or the IP address of the NLB.

Install any HEX editor tool to modify the DLL file.After this, you have to stop Terminal Server before modifying it.First backup the DLL file to be on the safe side and take the ownership and provide full rights of termsrv.dll file for your profile.So the following solution would be convenient. I tried RDP Wrapper but it didn’t help for the newer version of Windows 10. Hereby, I modify the termsrv.dll file from the System32 folder to get it done. In the end, I manage to get it done and thought to share my step on my blog. I have seen few tools on the internet too but they are not working properly with the latest Windows update too. I googled and tried to come up with a solution.

It is an easy step for System Administrator on Windows Server, however, as being the normal operating system, it wasn’t easy to fulfill this requirement on Windows 10. I got up a requirement to setup Windows 10 in a cloud from where we want to have concurrent users on it at the same time.
