The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: [OT] Has anyone got a Ferguson DAB/FM radio ?


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [OT] Windows WTS


  • To: ukha_d@xxxxxxx
  • Subject: RE: [OT] Windows WTS
  • From: "K. C. Li" <li@xxxxxxx>
  • Date: Fri, 31 Oct 2003 16:58:13 +0000 (GMT)
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

On Fri, 31 Oct 2003, Rob Mouser wrote:

> >From memory:
>
> XP: 1 client connection
> 2000/2003 Server: 2 concurrent client connections
> Windows Terminal Server: Dependant on licensing and resources

That can't possibly be right, Rob, unless you are talking about a
different WTS than mine. The WTS I am referring to is the Citrix metaframe
software that allows multiple users to run programs remotely as if they
are using the Windows server locally. A kind of thin client set-up. In
effect, the clients can be on any hardware that is capable of
communicating with the Windows NT or XP server. eg. Linux, Windows 95,
etc.

I know WTS can handle at least 40 users on a single server from the
preliminary tests carried out but I would like to know the upper limits
and any performance bottlenecks. I know a project that has already
purchased two ML570R NT Servers with 200 Citrix software licences.
Hardware and software costs are not a primary concern but the maximum
number of users per server is. The project is aiming to support up to
1,500 users running on the minimum number of Windows servers. Each server
can be whatever specifications necessary to support the number.

Regards,

Kwong Li
li@xxxxxxx
Laser Business Systems Ltd.
http://www.laser.com



Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.