Attempting to remote control another user's terminal session causes them to be disconnected.



Attempting to remote control another user's terminal session causes them to be disconnected


Issue:

We have done extensive research into this issue and discovered that Microsoft have introduced a bug in Service Pack 1 for Windows Server 2008 and Windows 7 which causes clients to be disconnected when a remote control session is attempted.

It is possible to remote control a session that is connected to a Windows 2008 R2 server or a Windows 2003 server but fails if a remote control attempt is made from a Windows 2008 server.

The issue is caused by the fact that one of the buffers used by Windows 2008 Terminal Server is insufficient.  The only workarounds available from Microsoft at the moment are high risk options such as uninstalling the service pack which, as the issue is not cirtical, does not justify the risk involved.  We are currently waiting on a stable fix from Microsoft.

Workaround:

It is the version of the operating system that is making the remote control attempt that determines if this issue occurs so if you have more than one server and one of them is running Windows 2008 R2 or Windows 2003 it will be possible to remote control sessions on the Windows 2008 server remotely (although Windows 2003 will not remote control sessions on a Windows 2008 R2 server or later)

 

 

Cardium offer services including Cloud Computing using Microsoft Remote Desktop Services paid for monthly and per user, installation, consultancy and virtualisation best practises.

Company Registration 5135448 VAT registration 834 5840 16

Your Office Anywhere, Cardium Outsourcing, Unit 4, Dominion Court, Billington Road, Burnley, Lancashire, BB11 5UB, UK.


 © Your Office Anywhere 2011

Add Feedback