more importantly, you must be running a WIN32 client to use w2k term services.
no java client is available, no mac, no linux, no unix clients... at least not yet... -----Original Message----- From: John Roland Elliott [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 01, 2001 8:59 AM To: [EMAIL PROTECTED] Subject: Re: Terminal Server -- Comments First, unlike the NT version, which is a separate product (Windows NT Server Terminal Server Edition), and unlike Citrix Metaframe, which is an add-on to Windows 2000 Server, Windows 2000 Server (and Advanced Server, and Enterprise Server, but not Professional) has Terminal Services as a built-in capability which, at your option, can be enabled or disabled. Now, licensing ... Non-Windows Terminal Server clients are not mentioned explicitly in the references that follow, but it is inconceivable to me that the Microsoft legal staff has failed either to forbid them altogether or make them at least as expensive as Windows-based Terminals. Presuming that they have not made the illegal altogether, the list of what you will need for your hypothetical 20-Linux-desktop configuration would include: For each terminal server: either Windows NT Server Terminal Server Edition or some form of Windows 2000 Server For the 20 boxes that will render applications running on the terminal server: 20 Client Access Licenses - CALs (for NT or for 2000). About $40 each. plus either 20 NT Workstation or a Windows 2000 licenses (even though you're not running the software) or 20 Terminal Server CALs (these are separate from the common CALs) About $110 each. It would make sense to use the Workstation or 2000 Professional licenses instead of the TSCALs only if you already had them ... perhaps the Linux boxes came from the factory with NT or 2000 preinstalled. With Windows 2000 Terminal Services, there are two other choices for the client-side licenses: Internet Connector Licenses --- A maximum of 200 anonymous users connecting to the TS over the Internet. None of these users can be employees. Work at Home Terminal Services CALs --- These are upgrades to TSCALS that you have to have already bought. References: for NTS/TSE http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnntmag99/h tml/licensing.asp: Terminal Server Client Access Licenses WFW 3.11 and Win9x clients have two licensing options. In addition to CALs, these clients need either a full-blown NT Workstation 4.0 license or a new kind of license called a Terminal Server Client Access License (TSCAL). A TSCAL costs about $110, which is a bit cheaper than an NT Workstation license. You might want to opt for the NT Workstation license anyway if you think that you'll be going to NT Workstation on your desktop soon. Buying a copy of NT Workstation will provide you with a better desktop OS and give you access to your enterprise's Terminal Server machines. But either way, there's a catch. According to the price list on Microsoft's Web site, you can't simply buy one TSCAL; Microsoft sells TSCALs and CALs only in bundles, not individually. Dumb devices such as Windows terminals need CALs and TSCALs. Although you could opt to buy a copy of NT Workstation 4.0 for your Windows terminal, you'd be wasting money. You'll incur the minimum cost to attach a device to a Terminal Server system by buying a CAL and a TSCAL for the device. NT workstations are exceptions to the rule because they don't need TSCALs. Before you go out to buy licenses, however, remember that Microsoft sells TSCALs and combinations of CALs and TSCALs only in packs of five. A five-CAL/TSCAL combo retails for $749. Because CALs typically cost $40 apiece, Microsoft must figure that the retail value of a TSCAL is about $110 apiece. (Of course, volume customers pay less.) Plan to pay about $150 for most client licenses. for W2K/TS http://www.microsoft.com/windows2000/techinfo/reskit/en-us/default.asp?url=/ WINDOWS2000/techinfo/reskit/en-us/deploy/dgbm_win_nsbv.asp: Required Licenses Deploying Terminal Services and Terminal Services Clients on your network requires the following licenses: Windows 2000 Server License This license is included with the purchase of the product. Windows 2000 Server Client Access License This is required for each device connecting to Windows 2000 Server. Client Access Licenses permit clients to use the file, print, and other network services provided by Windows 2000 Server. The Terminal Services component of Windows 2000 Server requires Per Seat licensing for the Windows 2000 Server Client Access License, except when you purchase the Windows 2000 Terminal Services Internet Connector License. The Internet Connector License is described later in this chapter. Each client computer or terminal requires the following licenses: Windows 2000 Terminal Services Client Access License or Windows 2000 License The Client Access License provides each client computer or Windows-based terminal the legal right to access Terminal Services on a Windows 2000 Server. For example, this license is required to start a terminal session and run Windows-based applications on the server. The Windows 2000 license permits the installation of the Windows 2000 operating system, in addition to providing the legal right to access Terminal Services on a Windows 2000 Server. The Terminal Server Client Access License is not required for clients connecting only to Terminal servers in Remote Administration mode. Optional Terminal Services Licenses In addition to the required Terminal Services licenses, two optional licenses are available: the Windows 2000 Terminal Service Internet Connector License and the Work at Home Windows 2000 Terminal Services Client Access License. Windows 2000 Terminal Services Internet Connector License In place of the Client Access Licenses, you have the option to purchase the Windows 2000 Terminal Services Internet Connector License. This license is purchased separately as an add-on license to Windows 2000 Server. It allows a maximum of 200 concurrent users to connect anonymously to a Terminal server over the Internet. This is useful for organizations that want to demonstrate Windows-based software to Internet users without rewriting Windows-based applications as Web applications. All users who access a Terminal server with this license must not be employees. When you use the Internet Connector License with a specific Windows 2000 Server, Terminal Services only allows anonymous client access. You cannot use the Internet Connector License with other types of Terminal Services client access licenses on the same Windows 2000 Server. Work at Home Windows 2000 Terminal Services Client Access License For organizations that want to use Terminal Services to provide their employees home access to the Windows 2000 desktop and 32-bit Windows-based applications, the Work at Home Terminal Services Client Access license is available through the Microsoft Volume licensing programs. For each Windows 2000 Professional or Terminal Services Client Access License you purchase, you can purchase an additional Work at Home Windows 2000 Terminal Services Client Access License. ----- Original Message ----- From: "Justin Bennett" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 01, 2001 8:30 AM Subject: Re: Terminal Server -- Comments > This sounds good, but forgive me, I have very little knowledge of the M$ server > products/Liscensing Scams. I would need NT Terminal server, Does 2000 Advanced server > have the Terminal Server stuff, or is it a seperate product. I can't use The 2000 > Professional (desktop) product or NT 4.0 server? Will I then need licencing on the > Terminal Server side, If I have 20 Linux Clients do I need a Terminal Server with 20 > Access Lic? --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
