Tech Tip: Enable Concurrent Desktop Sessions in Windows

Can always use a different operating system that doesn't have the same EULA limitations. problem solved, without feeling guilty about buggering your DLL files. That is probably the best work-around.

Excellent Good work. Does exactly what is says.

Just FYI:
After patching Termsrv.dll with the .exe file, YOU NEED TO REGISTER THE DLL! To do this run the corresponding .reg file for your OS (e.g. xp.reg for WinXP and vista.reg for WinVista).

Cheers!

I changed my Win 7 Enterprise SP1 64 bit to concurrent user by running the termsrv.dll. But now I want to restore it back to the original setting with single user RDP access. I have the termsrv.dll.backup but it would not allow me to do anything. I cannot restore to a previous date before I made the system concurrent, since it has been 6 months and cannot restore to that point with other updates made in between then and now. Can someone please help me remove the concurrent setting to the original single user RDP setting?

Thanks, Ashley G

Despite not being very old, the mirror links to this .dll file now appear to be broken. They link to phishy-looking sites. (one Russian, one Chinese/Japanese/something, another just phishy)

Possible a coincidence, but after I applied the patch (which worked, by the way) I was unable to map to a drive on that computer from another computer. Is this a problem?

It is on Windows/7 - - even with cross-platform Mac accessing Windows
[ie no hack/patch required]

TCP.SYS get's backup then replaced with the one without the limiter which by default is 10. I've had these changes for years. Based on DIR-655 Router which could handle MCS of 200 the system would be set from 10 to 100. Base today on faster routers the system would go from 100 to 200. Most users could use setting of 50 instead. I only have one Windows 7 U-64-bit using the 200 setting. Another desktop running at 50. Considering running TCP Optimizer and running additional code name JASPER script I came up with will give you what Windows 8 gives you now TCP Global

Now that's only one part of the puzzle. Three is the TCP GLOBAL settings. Running a script could change that.

Windows 7 32/64-bit

Showing Prior Check the TCP/IP state PROCESS STARTED

Querying active state...

TCP Global Parameters
----------------------------------------------
Receive-Side Scaling State : enabled
Chimney Offload State : enabled
NetDMA State : enabled
Direct Cache Acess (DCA) : enabled
Receive Window Auto-Tuning Level : normal
Add-On Congestion Control Provider : ctcp
ECN Capability : disabled
RFC 1323 Timestamps : disabled


Press any key to continue . . .

Windows 8 Preview 32/64-bit

Windows 8

TCP Global Parameters
----------------------------------------------------
Receive-Side Scaling State : enabled
Chimney Offload State : disabled
NetDMA State : disabled
Direct Cache Access (DCA) : disabled
Receive Window Auto-Tuning Level : normal
Add-On Congestion Control Provider : none
ECN Capability : disabled
RFC 1323 Timestamps : disabled
Initial RTO : 3000
Receive Segment Coalescing State : disabled
-----------------------------------------------------

After on Windows 32/64-bit

TCP Global Parameters
----------------------------------------------------
Receive-Side Scaling State : enabled
Chimney Offload State : enabled
NetDMA State : enabled
Direct Cache Acess (DCA) : enabled
Receive Window Auto-Tuning Level : normal
Add-On Congestion Control Provider : ctcp ( experimental gives you a little more Mbps )
ECN Capability : disabled
RFC 1323 Timestamps : disabled
Initial RTO : 1000

Works fine!!
TY "a loottt", I was searching for this a "looonnngg" time!!
Congratulations!!