Re: Terminal Services Advanced Client
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 27 Jul 2005 13:38:44 -0700
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 ___
.
- Follow-Ups:
- Re: Terminal Services Advanced Client
- From: Fuji
- Re: Terminal Services Advanced Client
- From: Patrick Rouse
- Re: Terminal Services Advanced Client
- References:
- Terminal Services Advanced Client
- From: Fuji
- Terminal Services Advanced Client
- Prev by Date: Re: Cannot Connect - No Error Dialog!
- Next by Date: how to disable RDP
- Previous by thread: Terminal Services Advanced Client
- Next by thread: Re: Terminal Services Advanced Client
- Index(es):
Relevant Pages
|
