Re: Terminal Services Advanced Client

This rumor came out in 2001, but I haven't seen anything that would lead me
to believe that the full Remote Desktop Client is going anywhere. On the
contrary, it's installed by default on every new Windows OS.

--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com


"Vera Noest [MVP]" wrote:

> comments inline
>
> "Fuji" <fuji.huynh@xxxxxxxxx> wrote on 27 jul 2005 in
> microsoft.public.windows.terminal_services:
>
> > I an new to Terminal Services and I am currently researching
> > this technology with a view to seeing how viable it is to
> > implement for my company's needs.
> >
> > My company is based in the UK and we have several partner
> > organisations based in Europe, Japan and the US. We have a VB
> > application that connects to a SQL Server database using ADO.
> > Our partners use the same application that we use in the office
> > except that the data they receive is filtered horizontally. The
> > experience our partners get is that operations that are often
> > instantaneous or take very little time to execute when running
> > the application in the office takes up to 20 minutes when
> > executed at the partner organisation. I feel that this could be
> > due to network latency issues as large datasets are being
> > transferred.
> >
> > So I'm hoping Terminal Services is a solution to this problem.
> > As I understand it because the application is running off the
> > server and all that is being transmitted are the keyboard/mouse
> > commands from the user and all the user receives in effect is a
> > bitmap that there will not be network latency issues or
> > certainly not to the same extent.
>
> Yes, that's correct. If the Terminal Server is located near the SQL
> server, on the LAN, then running the VB application on the TS should
> give comparable performance with running it from a workstation on the
> LAN.
> And as you write, the rdp connection from the client to the Terminal
> Server doesn't need much bandwidth.
> If I understand you correctly, then you are planning to deploy only
> this particular application through Terminal Services, is that
> correct? Users will *not* run Office or Internet Explorer through the
> TS? No Flash animations or other graphics-intensive programs?
> If that is so, it makes planning easier. The rough estimates are
> something like this:
> Minimum bandwidth for a useable RDP Session = 26.4Kbps
> 800x600 @16 bit color - 26.4Kbps per session
> 1024x768 @256 colors - 24.6Kbps per session
> each increase in screen resolution or color depth requires about 3-4
> Kbps more bandwidth.
> Printing to a redirected printer will also generate (a lot of)
> traffic, so you will have to take that into account. But with the
> assumptions above, you should be fine with 30 - 60 Kbps.
>
> > I have been informed though that 'Terminal Services Advanced
> > Client activeX control is the way forward' and that 'Microsoft
> > will be phasing out Terminal Services client as a desktop
> > application'. Does anyone know if this is the case: should I be
> > concentrating on Terminal Services Advanced Client activeX
> > control rather than the Terminal services client. I can't seem
> > to find much information about Terminal Services Advanced client
> > activeX and its implementation.
>
> This rumour hasn't reached my ears previously, and it would amaze me
> if it were true, but I can't say yes or no to this.
>
> Here is a link to information about the Remote Desktop Web Connection
> (as it is called officially; TSAC is the old name).
>
> Remote Desktop Web Connection
> http://msdn.microsoft.com/library/default.asp?url=/library/en-
> us/termserv/termserv/remote_desktop_web_connection.asp
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
>
.

Relevant Pages

  • Re: can someone help clear this up?
    ... Terminal Services Client Access Licenses are assigned to the client, ... The Terminal Services License Server ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Users Cant Log Into Local Machine That Is Attached To A Domai
    ... Are you trying to access to a T.S server? ... Are you trying to access via RDC (Remote desktop connection) to a Windows ... Terminal Services Client Error Message: You Do Not Have Access to Logon to ... You do not have access to logon to the Session. ...
    (microsoft.public.windows.server.active_directory)
  • RE: Terminal Services
    ... Only if Remote Desktop Connection or Terminal Services client installed on ... Configure the client computer running Windows XP Professional to ...
    (microsoft.public.windows.server.sbs)
  • Re: Time zone redirection
    ... Administration and full-blown Terminal Services. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... client connections:-O. ... Well - obviously that does not work in Remote Desktop Admin mode ...
    (microsoft.public.windows.terminal_services)
  • Re: Client behind a firewall!
    ... Microsoft MVP - Terminal Server ... Internet with Remote Desktop enabled when I'm at work, ... Remote Desktop client is blocked, and I just can't use it. ...
    (microsoft.public.windows.terminal_services)