Re: Terminal Server & CLI clients

Thank you for making up my mind on this subject...

I think you hit the "high notes" quite well.

Based on what you have seen, what would you do when
you "only" need two products (a)5250 (b)Word  and NO
other products...no surfing,no e-mail, just the two
products.

It doesn't appear that the "thin clients" are up to that,
even though CLI appears to have a client that runs a
"thin" version of XP. I assume you need some way to serve
up any other products to the terminal device.


Jim Franz wrote:

I have one customer using Terminal Server, 22 users (but with pc's with Client Access).

Three different win Tech's have managed this, all at least MCSE,
and one was one of the smartest techs I've met.
All have had trouble keeping it "always up".
Some of it had to do with other pc products on the server used by the users,

and not "certified" for Terminal Server. Client Access has run most of the time.

There are specific limits of xx memory per user, and zz users per server.

They put a big IBM x-series dual processor server in and still had through-put

problems. At least once a week it gets rebooted for just bogging down.

I will admit current tech is least of the three, and there could be lots of reasons

for the problems, but it has not been a happy network.

I think anyone managing this must be Terminal Server certified (if such a thing),

and absolutely have proper training for Term Server.
jim franz