Thread: Microsoft Terminal Services Advanced Client (TSAC)

I spent days trying to find info on TSAC and I was hoping one of you might be able to answer a question for me:

Has anybody ever managed to figure out how to force a console port when using TSAC (Microsoft Terminal Services Advanced Client) ?

I know when connecting via a shortcut (or via command line) you can use this for example to force a console connection (using remote desktop connection):

WINDOWS XP SP2 and earlier
mstsc /v:111.222.333.444 /console


WINDOWS XP SP3 and VISTA
mstsc /v:111.222.333.444 /admin


But can that be done with TSAC ?


If you know how, and if that is possible can you tell me how to do that with TSAC web client please?


Thank you

Which version of the TSAC web client are you using?

The original TSAC ActiveX control that was included in Windows 2000 Service Pack 1 (SP1) can connect only over TCP port 3389.

To configure the TSAC ActiveX control to connect to other ports, you need the version of the TSAC that Microsoft released as security update 327521.

Instruction for working with this are in How to Change the Listening Port in the Windows Terminal Server Web Client.

Excuse me if I wound ignorant, but how do i check the version of TASC?

Quick update, I am using the Windows 2003 Server (enterprise edition).
How do i check the version so you could help me please?

It might be easier to update to the latest release than to check the version number.

If you're using Windows 2003 Server, I think you're good.

To change the Terminal Server listening port in Windows Server 2003 clients, follow these steps:

1. Locate the Default.htm file in the %system root%\Web\TsWeb folder.
2. Open Default.htm in Notepad or in another text editor.
3. Locate the entries that start with "MsRdpClient.AdvancedSettings2".
4. Add the following line after these entries
   MsRdpClient.AdvancedSettings2.RDPPort = xxxx
   where xxxx is the new port.
5. To make sure that you can connect with the new setting, append the port number to that of the published URL (that is, www.xxx.xxx.xxx:PortNumber).

Hi Tom,

Thank you, but in this case I am not looking to change the listening port, but to force a console session when logging in via TSAC.

If I find out how, i will post it up here for everyone else. (i know it can be done as i have seen it a few years ago i just completly forget how to).

Who knows..maybe it will help someone here in the future..

thanks

MCSA/MCSE Exam 70-290: Managing and Maintaining a Windows Server 2003 Environment says:

Only the Remove Desktop MMC snap=on and the mstsc /console command can be used to connect to the console session of a Terminal Services computer. However, an administrator actually sitting at the server and using the console session can request help by using the Remote Assistance functionality in Terminal Services. It is important to note that for security reasons, a console session cannot be viewed using Remote Control.

I'm sorry, I thought you were just talking about changing the TSAC port, which is possible.

SecurityFocus Microsoft: Changing Terminal Server port in TSAC ActiveX Web Control says:

The way the TSWeb access works is by simply loading an ASP page (CONNECT.ASP) that calls the MSRDP.OCX ActiveX Object. For those of you that want to use the ActiveX control to connect to a different listening port, all you have to do is edit the CONNECT.ASP page, and add the following line before the MsTsc.Connect method:

MsTsc.AdvancedSettings2.RDPPort=X

- - where is X is the custom port your TS is listening on (in decimal). When the ActiveX control attempts to connect to the TS, it will now use this port.

Hi Tom,

Actually you were wrong there (not worry mate, I can be wrong too).

anyway to get to the point here is how you can get the console port (also known as session zero) , via TSAC:

The sample default.htm page doesn't support the option to logon to the console session by default. So in the default.htm you need to add the following:

5. B.1. Above the code for the checkbox that already exist add:

<p class=topspace>&nbsp;<input type="checkbox" name="CheckBoxConsole" ID=CheckC value="OFF"><label for="CheckC" ID=ConnectToConsole accesskey="c"><ID id=consoleinfo><u>C</u>onnect to console session&nbsp;</ID></label><br>

5. B.2. Under the sub called "BtnConnect" add:

if Document.all.CheckBoxConsole.checked then
MsRdpClient.AdvancedSettings2.ConnectToServerConso le = TRUE
end if


Thats it and then from there on you can click the box "connect to console" , and then when you login via TSAC you will be "session zero"

I hope this helps other people as this drove me crazy for over a week. I needed a solution you see to force one session per person.


Cheers

I'm glad to hear you got it working!