Skip to main content

Concurrent Desktop Sessions in Windows

Professional and Ultimate editions of Windows come with a built in Remote Desktop (RDP) feature that allows you to access your machine remotely while away from home or the office. Unfortunately, it is limited by default to one concurrent user per session, meaning that if someone remotely connects to the computer, whoever was logged in at the moment will be automatically logged off, even if the user is physically at the computer.



This is not a technical limitation but rather a licensing one. Case in point, Remote Desktop in server editions of Windows by default supports two concurrent connections to remotely troubleshoot or administer a computer. More users can connect simultaneously, too, as long as the machine can handle it with the resources it has available and you have the required client access licenses for that particular server.

The Windows 2003 and windows 2008 support the Multiple Concurrent Remote Desktop, but Win 7 does not support Multiple Concurrent Remote Desktop by default. In serever 2003, Remote Desktop allows for 2 administrative connections without the need to purchase additional licenses. If you want multiple people to connect to the server, then you can install terminal services on that machine and purchase the required licenses.

 if you are sharing a computer with other users, concurrent Remote Desktop sessions will allow more than one person use that system under a different or even the same user account, without kicking each other off. By patching a file called termsrv.dll, located in %SystemRoot%System32, this is possible in all editions of Windows 7, Windows Vista and Windows XP.

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:

Download the file for  Concurrent Desktop Sessions in Windows

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.

Crack termsrv.dll, remove the Concurrent Remote Desktop sessions limit, allow multi-user login in XP/Vista at the same time.

This is only a file patch for termsrv.dll.
More setting for RDP, please google it.

The meaning of the last number of checksum:
1 - Original file, without any modification.
9 - The file has been modified.

Notes:
1, Can oprate in normal mode. Do not need to enter safe mode.

2, Choose the corresponding patcher based on you Windows:
   For 32bit(x86):   UniversalTermsrvPatch-x86.exe
   For 64bit(amd64): UniversalTermsrvPatch-x64.exe

3, Require administrator rights. Right-click the exe file, select Run as Administrator.

4, After patch, Restart computer to take effect.

5, Backup file: \windows\system32\termsrv.dll.backup.


Comments

Popular posts from this blog

Checking operating system version: must be 5.0, 5.1 or 5.2 Actual 6.1 Failed

This error occurred when we are installing old oracle software in latest OS (Operating System).   Basically Its’s occurring on windows platform.

Oracle forms 11g default configuration file formsweb.cfg

#formsweb.cfg defines parameter values used by the FormsServlet # formsweb.cfg defines parameter values used by the FormsServlet (frmservlet) # This section defines the Default settings. Any of them may be overridden in the # following Named Configuration sections. If they are not overridden, then the # values here will be used. # The default settings comprise two types of parameters: System parameters, # which cannot be overridden in the URL, and User Parameters, which can. # Parameters which are not marked as System parameters are User parameters. # SYSTEM PARAMETERS

Windows 8 boot loader corrupted

Problem:     Installed Windows 7 and Windows 8 in EFI mode on a hard disk some days past. Today, the boot loader is absent or corrupted. At present have the Windows 8 installer on a flash drive and tried using the Automatic Repair option to repair the boot loader but it didn't do anything. The Startup Repair option is also absent in the Windows 8 installer. How I can repair or recreate the EFI boot loader from the Command Prompt? BCDEDIT   returns the following message: The requested system device cannot be found. Solution: Firstly, boot from a UEFI Windows 8 recovery disk (CD/DVD/USB) - I found that the automated recovery process didn't find the correct Windows partition, nor when I managed to add it to BCD settings would it make it reliably boot-able e.g. using BCDEDIT I got it to find and launch the Windows partition but it refused to cold boot or would not "keep" the settings after a 2nd reboot or power off. Go into the Advanced option