Category: General

By using the below command, we can remote login to machine even though a session is already opened.

mstsc /v:{server name} /admin

Inorder to start scripting the SAP applications using the Loadrunner tool, we have to enable the scripting mode available in the SAP application apart from the normal script enabling setting.

Please use the TCode – RZ11

Navigate to the page it allows and change the settings to ‘FALSE’ for the below mentioned parameters.

a. sapgui/user_scripting_set_readonly and set the value as “FALSE”
b. sapgui/user_scripting_force_notification and set the value as “FALSE”


Machine A : PC which you are using to active remote desktop connection in another PC

Machine B : PC for which remote desktop connection has to be activated.


 Step 1:

From Machine A :  Goto Start -> Run -> regedit. Open the Registry window of Machine A.

(Note: User ID logged in Machine A should have ADMIN rights in Machine B)

Step 2:

Click “Connect Network Registry“

Step 3:

Enter the computer name of Machine B, for which we have to change the settings and Click “OK”


The destination machine (Machine B) will be connected with our current logged in machine (Machine A).


Step 5:

Goto the below mentioned path and change the fDenyTSConnections to “0” and click “OK”.

 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services

 Step 6:

After doing the following changes, right-click the remote machine (Machine B) name and click Disconnect.

(NOTE: If suppose the above mentioned registry value is not found, then create a DWORD parameter with a value ‘0’.

To get Concurrent Sessions in Remote Desktop working, follow the steps below exactly:

  1. Download the file below and extract it somewhere. (You have to be registered to see the file)
  2. Reboot into Safe Mode. This is necessary to remove Windows File Protection.
  3. Copy the termserv.dll in the zip to %windir%System32 and %windir%ServicePackFilesi386. If the second folder doesn’t exist, don’t copy it there. Delete termserv.dll from the dllcache folder: %windir%system32dllcache
  4. Merge the contents of Concurrent Sessions SP2.reg file into the registry.
  5. Make sure Fast User Switching is turned on. Go Control Panel -> User Accounts -> Change the way users log on or off and turn on Fast User Switching.
  6. Open up the Group Policy Editor: Start Menu > Run > ‘gpedit.msc’. Navigate to Computer Configuration > Administrative Templates > Windows Components > Terminal Services. Enable ‘Limit Number of Connections’ and set the number of connections to 3 (or more). This enables you to have more than one person remotely logged on.
  7. Now reboot back into normal Windows and try out whether Concurrent Sessions in Remote Desktop works. It should!

If anything goes wrong, the termserv_sp2.dll is the original file you replaced. Just rename it to termserv.dll, reboot into safe mode and copy it back.

The termserv.dl_ file is provided in the zip is for you slipstreamers out there. Just replace that file with the corresponding file in the Windows installation disks.

I’ve added in extra information from the comments below… thanks for all who researched! 🙂

Other links of interest:

If anything doesn’t work with my procedure above though, post a comment here and I’ll try to help!

Attachment Size 357.92 KB

For Further Details, please look further (These details has been fully followed up with vishnu’s Blog)

HTTP Status Codes

Status Code Meaning 



100 – Continue; part of request received

101 – OK to switch protocols




200 – OK; all requested info returned

201 – Created; request filled

202 – Accepted; request received

203 – Source unknown; info came from 3rd party

204 – No new content; nothing to send back

205 – Reset content; OK to clear form

206 – Request only partially filled




300 – Header for 3xx codes

301 – Moved permanently; use new URL

302 – Moved temporarily; use same URL

303 – Redirected

304 – Not modified since; use cached copy

305 – Use proxy; URL is provided




400 – Did not understand request; try again

401 – Authorization required; needs password

402 – Payment required; needs payment data

403 – Request refused; may not give reason

404 – Not found; not sure of reason (typo, etc.)

406 – Content type not acceptable to request

407 – Browser must authenticate itself

408 – Timed out; send request again

409 – Update conflict; explanation provided

410 – Not found; resource permanently gone

411 – Content length missing in request

412 – Conditions on request failed

413 – Request too long to process

414 – Resource address too long to process

415 – Unsupported media type; bad format




500 – Internal server error

501 – Server cannot fill request

502 – Server cannot process gateway request

503 – Server overloaded or service over limits

504 – Gateway or proxy server timed out

505 – HTTP version not supported in server