Results 1 to 10 of 10

Thread: Microsoft Terminal Services Advanced Client (TSAC)

  1. #1
    Aquinas is offline Newbie Net Builder
    Join Date
    Jan 2009
    Posts
    59
    Thanks
    1
    Thanked 8 Times in 4 Posts

    Exclamation 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
    Last edited by Aquinas; 22 January, 2009 at 20:33 PM. Reason: forgot a spacing and added "bold"

  2. #2
    Tom's Avatar
    Tom
    Tom is offline Net Builder
    Join Date
    Dec 2008
    Posts
    171
    Thanks
    12
    Thanked 111 Times in 57 Posts
    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.

  3. #3
    Aquinas is offline Newbie Net Builder
    Join Date
    Jan 2009
    Posts
    59
    Thanks
    1
    Thanked 8 Times in 4 Posts
    Excuse me if I wound ignorant, but how do i check the version of TASC?

  4. #4
    Aquinas is offline Newbie Net Builder
    Join Date
    Jan 2009
    Posts
    59
    Thanks
    1
    Thanked 8 Times in 4 Posts
    Quick update, I am using the Windows 2003 Server (enterprise edition).
    How do i check the version so you could help me please?

  5. #5
    Will.Spencer's Avatar
    Will.Spencer is offline Retired
    Join Date
    Dec 2008
    Posts
    5,033
    Blog Entries
    1
    Thanks
    1,010
    Thanked 2,329 Times in 1,259 Posts
    It might be easier to update to the latest release than to check the version number.
    Submit Your Webmaster Related Sites to the NB Directory
    I swear, by my life and my love of it, that I will never live for the sake of another man, nor ask another man to live for mine.

  6. #6
    Tom's Avatar
    Tom
    Tom is offline Net Builder
    Join Date
    Dec 2008
    Posts
    171
    Thanks
    12
    Thanked 111 Times in 57 Posts
    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).

  7. #7
    Aquinas is offline Newbie Net Builder
    Join Date
    Jan 2009
    Posts
    59
    Thanks
    1
    Thanked 8 Times in 4 Posts

    Microsoft Terminal Services Advanced Client (TSAC)

    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

  8. #8
    Tom's Avatar
    Tom
    Tom is offline Net Builder
    Join Date
    Dec 2008
    Posts
    171
    Thanks
    12
    Thanked 111 Times in 57 Posts
    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.

  9. #9
    Aquinas is offline Newbie Net Builder
    Join Date
    Jan 2009
    Posts
    59
    Thanks
    1
    Thanked 8 Times in 4 Posts

    Talking TSAC - How to connect to the console port via TSAC

    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

  10. Thanked by:

    Tom (5 February, 2009)

  11. #10
    Tom's Avatar
    Tom
    Tom is offline Net Builder
    Join Date
    Dec 2008
    Posts
    171
    Thanks
    12
    Thanked 111 Times in 57 Posts
    I'm glad to hear you got it working!

Similar Threads

  1. Advanced Footer Encryption techniques
    By Dr. Teeth in forum Programming
    Replies: 5
    Last Post: 3 May, 2010, 13:43 PM
  2. Free ebook: Advanced SEO Techniques
    By DotComBum in forum eBooks
    Replies: 0
    Last Post: 20 July, 2009, 12:32 PM
  3. Replies: 1
    Last Post: 30 June, 2009, 04:22 AM
  4. Replies: 1
    Last Post: 14 May, 2009, 09:17 AM
  5. Need help with Advanced Placement classes?
    By CoreyFreeman in forum General Chat
    Replies: 0
    Last Post: 1 May, 2009, 23:17 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •