New Switch for RDP 6.0

Topics: Developer Forum
Feb 4, 2008 at 5:51 PM
Hi,

It seems, from a Vista client to a Windows 2003 Server I must use a NEW switch in RDP 6.0 to access the console of the server. I can't use /console I must use /admin to access the console. This change does not allow me to access the console of Windows Server 2003 from Terminals when on Vista.

Is this a known issue? Is there a workaround to this issue in the current Terminal version?

Link with detail on this change from MS:
http://blogs.msdn.com/ts/archive/2007/12/17/changes-to-remote-administration-in-windows-server-2008.aspx

Feb 22, 2008 at 10:20 PM
Yeah, I noticed this too.

This is the relevant portion for the Terminals devs.

_Developer resources – Changes to APIs

If you are using RDC 6.1, you can no longer use the ConnectToServerConsole property of the IMsRdpClientAdvancedSettings interface to specify whether the Remote Desktop ActiveX control should attempt to connect to the server for administrative purposes. Instead, you must use the ConnectToAdministerServer property of the IMsRdpClientAdvancedSettings6 interface to connect to the physical console session on a Windows Server 2003-based server, or to the session that is used for administrative purposes on a Windows Server 2008-based server.

For more information about the ConnectToServerConsole property, see http://go.microsoft.com/fwlink/?LinkId=106203.

For more information about the ConnectToAdministerServer property, see http://go.microsoft.com/fwlink/?LinkId=106204._
Feb 22, 2008 at 10:21 PM
Yeah, I noticed this too.

This is the relevant portion for the Terminals devs.

Developer resources – Changes to APIs

If you are using RDC 6.1, you can no longer use the ConnectToServerConsole property of the IMsRdpClientAdvancedSettings interface to specify whether the Remote Desktop ActiveX control should attempt to connect to the server for administrative purposes. Instead, you must use the ConnectToAdministerServer property of the IMsRdpClientAdvancedSettings6 interface to connect to the physical console session on a Windows Server 2003-based server, or to the session that is used for administrative purposes on a Windows Server 2008-based server.

For more information about the ConnectToServerConsole property, see http://go.microsoft.com/fwlink/?LinkId=106203.

For more information about the ConnectToAdministerServer property, see http://go.microsoft.com/fwlink/?LinkId=106204.
Feb 22, 2008 at 10:22 PM
Whoops, sorry for the multiple clicks, first time here.


Sanketh wrote:
Yeah, I noticed this too.

This is the relevant portion for the Terminals devs.

Developer resources – Changes to APIs

If you are using RDC 6.1, you can no longer use the ConnectToServerConsole property of the IMsRdpClientAdvancedSettings interface to specify whether the Remote Desktop ActiveX control should attempt to connect to the server for administrative purposes. Instead, you must use the ConnectToAdministerServer property of the IMsRdpClientAdvancedSettings6 interface to connect to the physical console session on a Windows Server 2003-based server, or to the session that is used for administrative purposes on a Windows Server 2008-based server.

For more information about the ConnectToServerConsole property, see http://go.microsoft.com/fwlink/?LinkId=106203.

For more information about the ConnectToAdministerServer property, see http://go.microsoft.com/fwlink/?LinkId=106204.

Mar 8, 2008 at 2:04 AM

/Admin /Console Feature Workaround!

There is a workaround that is pretty easy.
Only drawback is that it only seems to work if the console session is already logged in to by someone.

If you log onto a non-console remote session and want to actually be on the console session you can:

  1. open cmd prompt as an administrator
  2. type either "tscon 1" or possibly "tscon 0" on older version servers.
  3. try "tscon /?" for more detailed info.
Since when connecting to client OSs you are allways connected to the console (default) this command is only a valid on servers.

Hope this helps untill the great peeps at Terminals add this feature. :)

Developers: BTW, if mstsc is expecting "/admin" it will ignore "/console" completely. The reverse is also true.
So you can provide both /admin & /console at the same time if you want to cover all your bases!

-Rick