Re: Terminal Server & CLI clients

["Jim Franz" <franz400@xxxxxxxxxxxx>]

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

----- Original Message ----- 
From: "Pat Barber" <mboceanside@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, May 08, 2006 2:48 PM
Subject: Terminal Server & CLI clients


> I spoke to a guy this morning about using CLI thin clients.
>
> He is pushing two different versions of CLI terminals.
>
> The basic model, which appears to be a 3488 and 5250 built
> in the device. This is a ethernet version of a 3488.
>
> The next model runs a "thin version" of Windows but in
> order to run any Windows products, he was recommending
> Terminal Server.
>
> I plead ignorance on this subject, but what's the deal
> with Terminal Server over something like Windows Server 2003 ???
>
> Is this any different than a normal server with windows apps
> on it ?
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.