Missing /Admin /Console Feature - Partial Workaround

Topics: Developer Forum, User Forum
Mar 8, 2008 at 3:11 AM

Missing /Admin /Console Feature - Partial Workaround!

This workaround is very simple.
The only drawback is that it only seems to work if the console session is already logged in to by someone.

So, if you log onto server's non-console remote session and want to actually be on the server's 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

Apr 30, 2008 at 11:32 AM
when are you guys implementing this workaround? It would be very helpful if you just provide both parameters /admin /console...nobody gets hurt and it works...
Coordinator
Apr 30, 2008 at 5:30 PM

Its not as easy as command line parameters on some executable. Remember we are actually the application which is hosting the control which does all the heavy RDP lifting (we replace mstsc.exe itself).

On that control's API we see a setting which instructs it to connect to the console session. Microsoft decided to change that on us. They pulled a fast one. :/ So right now we are torn between supporting the legacy RDP protocol and the slew of OS's it is available for vs the new RDP protocol and features like the one above.

here is the exact line of code in RDPConnection.cs

axMsRdpClient2.AdvancedSettings3.ConnectToServerConsole = Favorite.ConnectToConsole;

Microsoft decided to no longer honor that flag.
Coordinator
Apr 30, 2008 at 5:31 PM
Edited Apr 30, 2008 at 5:57 PM
http://www.codeplex.com/Terminals/WorkItem/View.aspx?WorkItemId=14694
Coordinator
Apr 30, 2008 at 5:33 PM
Edited Apr 30, 2008 at 5:56 PM

This might actually be good news...

http://msdn.microsoft.com/en-us/library/aa380863.aspx

ConnectToServerConsole Property of the IMsRdpClientAdvancedSettings Interface
This property is available for use in the operating systems listed in the Requirements section. It is unavailable as of Windows Server 2008, Windows Vista Service Pack 1 (SP1) and Windows XP Service Pack 3 (SP3).

They are actually phasing this out in XP SP3. Once that sucker gets into the wild (and propagates widly) we will need to just do a compelte upgrade and the older/unpatched OS's will have to live on a previous version of the Terminals app. --I smell a good reason to have a v2 release of terminals....
Coordinator
Apr 30, 2008 at 5:56 PM
Edited Apr 30, 2008 at 5:56 PM

For all those that are concerned:

https://connect.microsoft.com/WindowsServerFeedback/feedback/ViewFeedback.aspx?FeedbackID=341289

use the "Rating" stars (set it to max), and then "Validation" (add).

Hopefully if enough people create enough noise on the issue...
May 1, 2008 at 12:56 PM
i voted, but i would appreciate it if you make a release for the vista peeps out there...
Coordinator
May 1, 2008 at 5:26 PM

defsquad..you could always nab the source, and get ahead start on it for me :)