Re: Terminal Server

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hi,
I run 110 users at 23 branches all using Wyse terminals with 4 x Windows
2003 terminal servers
connected via a VPN over the internet - all sounds very complicated - but
its not as difficult as you think.

We worked out that we needed approx 25 users per server, we use I.E., VB 6
programs connected to a SQL database server, so for 40 users best use 2 x
terminal servers.
Don't get sucked into using Citrix its not as fantastic as they make it out
to be.

Printers
Make sure that you use as little different printer drivers as possible, use
all the same make if you can.
don't use printer drivers like Epson or Brother that have little 'monitor's
program that sit
in the system tray - they can cause problems. Use good laser printers,
Kyocera, Xerox, Canon
etc that have drivers made for terminal servers, bit of investment now in
printers can
save a lot of problems later.

Licences
What a mind filed, we had to get a expert in to sort out the licences, but
even now
the terminal server give out temporary licenses ! We never did get this
working correctly !

Terminals
We use Wyse S30 with a 17" LCD monitor, for office based apps this is fine,
if all the
terminals and servers are on the same LAN then you will not have speed
issues.
We don't use graphically challenging programs,so not sure how Visio will get
on. We use
MS Office, word Excel etc - all work fine.

Server
On you PDC set up your active directory with all your users in one unit
you can then allocate profile limitations in one place.

C: drive
Word of warning, make sure on your Terminal servers you have a big C: drive
as this is where each user profile is stored. We set up a profile rule to
clear the users
IE temporary files when they exit from IE - just to save space.

Okay that's all for now - have fun !

Mike.

PS
These are my own thoughts - sorry if I have upset any Citrix users !


"sifrah" <sifrah@xxxxxxxxx> wrote in message
news:1166318087.985223.122160@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi all,

By boss asked me to check the option of using terminal server for
users.

The requirement are:

1. It should host 40 users with full desktop application (office,
IE,Visio, etc)
2. The users will use terminals and monitors from their end

The main reason for this is apparently to save money as there are a lot
of temp users for short time.

Will it be cheaper doing so then buying 40 computers?

Thanks Simon



.



Relevant Pages

  • Re: Terminal Server
    ... I think now i'll be able to give my boss a better ... terminal servers. ... Make sure that you use as little different printer drivers as possible, ... The main reason for this is apparently to save money as there are a lot ...
    (microsoft.public.windows.server.general)
  • Re: BUG in CreateCompatibleBitmap with VC++.NET/2003
    ... I feel the limit is much lower in case of terminal servers. ... server kernel limit for printer drivers was very low. ... Kernel mode paged pool is limited to around 192 MB ... > number of DDBs that counts here, ...
    (microsoft.public.win32.programmer.gdi)
  • NLB cluster and Session Directory Troubles
    ... I deploy the NLB cluster consisting of two terminal servers (Win2K3 R2 Ent. ... Users have a roaming terminal servers profiles, ... (for example: for user UserName the profile path: ...
    (microsoft.public.windows.terminal_services)
  • RE: outlook setting
    ... Setup a file share on a server (not on one of the Terminal Servers) called something like TSProfile. ... Users should also be owners of their profile directories. ... Roaming Profiles Alternative ... Can you summarize me how we can set roaming profile, ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Local Drives in TS session
    ... I recommend you download and install the latest version of ... I have two terminal servers that are load balanced and the users in my ... roaming profile from the terminal servers when they log out. ... server session and they open 'my computer' the local drives appear as ...
    (microsoft.public.windows.terminal_services)