Re: Terminal Server & CLI clients -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Terminal Server & CLI clients
From: rob@xxxxxxxxx
Date: Mon, 8 May 2006 14:52:15 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I liken Windows Terminal Server to having a twinax card in your i5.  Sure, 
Windows Server 2003 will let fat clients access data, applications, etc, 
quite well.  However to have thin clients run these same things often 
requires Terminal Server.  Understand?  These thin clients are more like 
terminals then they are full PC's or fat clients.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Terminal Server & CLI clients , Pat Barber

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.