Originally posted by: PlatinumGold
i'm 100% sure i'm correct. i've been over this 1000 times with the MS rep on the phone.
One of us has it backwards, fer sure. And it's not me...and I have ALSO been over it (what seems like) 1000s of times with MS.
another way to look at it is, you buy win 2000 server with 5 cal's, those cal's only apply to os's that don't have lan cal's built in (win 9x, win me, win xp Home) other Os's don't use those cal's (win 2000 pro and win xp pro).
This is completely wrong. If the server is in PER-SERVER licensing mode, then those CALS license a TOTAL of 5 concurrent connections for Server services (file, print, etc.) from that particular Server at any given time. However, if the server is in PER-SEAT mode, then those 5 licenses can be permanently "assigned" (not an actual installation process, BTW) to any 5 workstations REGARDLESS of desktop OS (and including W2K Pro!!!), and those 5 machines can then access ANY Windows 2000 Server they ever wish to.
How do I know this? IMHO, it doesn't get spelled out any plainer (this from MS' own website):
Q. If I have licensed a client operating system already, do I need a CAL in order to connect to a Windows 2000 Server?
A. Yes, CALs are separate from the desktop operating system used to connect to Microsoft server products. Licensing an operating system (Windows 2000 Professional, Windows 98, Windows 95, Windows for Workgroups, and so on) does not give you a license to connect to a Windows 2000 Server product.
As for:
i have many networks setup where they have more than 5 workstations logging into the same win 2k server with only 5 cal's because all the clients have win 2k pro os's. the only lans where i have problems w/ cals are those that have more than 5 clients w/ OS's other than win2k pro or win xp pro.
Again...not to cast aspersions, but that doesn't prove anything. Are you sure those servers without problems are ACTUALLY running in PER-SERVER mode? If a Server is in PER-SEAT mode, then the Server does not limit connections in any way (well, not EXACTLY true, but for the services we are talking about, it is).
As far as TS is concerned...here goes:
Q. What licenses are required to run Terminal Services in Windows 2000?
A. Three product licenses are associated with Terminal Services in Windows 2000.
[skip...already determined, not relevant to topic anymore]
[skip...already determined, not relevant to topic anymore]
A Windows 2000 Terminal Services CAL, a Windows 2000 Professional license or a Windows XP Professional license is required to run applications on a Windows 2000 Server via Terminal Services.
Additionally, you are required to ensure that the applications you are running on the terminal server are properly licensed. For instance, Microsoft Office applications are licensed per-device. Each device that runs Office via a terminal server must have a license for Microsoft Office.
And yes I know that the issue of application licensing is a COMPLETELY separate issue, and not on-point to the current discussion, but it MUST also be taken into account when setting up Terminal Services to serve applications, so I left it in as a reminder.
There is a clarification about the "built-in" TS licenses for W2K Pro and WXP Pro. They aren't really "built-in" at all, it is simply that the Windows 2000 Server OS doesn't "charge" (by assigning a permanent CAL) to desktops running W2K Pro or WXP Pro:
I Q. Do Windows XP and Windows 2000 Professional have built-in Terminal Services CALs?
A. No, Microsoft's desktop operating system products (including Windows XP and Windows 2000 Professional) do not have a "built-in" Terminal Services CAL. Rather, the Windows 2000 server issues machines running Windows 2000/XP Professional with a ?free? Terminal Services CAL from its built-in pool (and its use is permitted under the Windows 2000 Server EULA). Windows XP Professional is a successor to Windows 2000 Professional, and as a result does not need a Terminal Services CAL to access a Windows 2000 Server running Terminal Services. However, Windows XP Home Edition is not a successor to Windows 2000 Professional (rather, it is a successor to Windows Millennium Edition) and therefore does require a Terminal Services CAL in order to access Windows 2000 Terminal Services.
Here's the thinking behind the TS CAL:
* Terminal Services offer a Windows 2000 Professional "desktop" to TS clients.
* MS figures that folks NOT running a Windows 2000 Professional "desktop" OS (or its successor, Windows XP Professional) need to pay a license (the TS CAL itself) to get the benefits of running that newer, better "desktop," since they HAVEN'T paid for it yet.
* MS figures that folks who ARE running a Windows 2000 Professional "desktop" OS (or its successor, Windows XP Professional) do NOT need to pay a license (the TS CAL itself) to get the benefits of running that newer, better "desktop," since they have ALREADY paid for that particular OS once.
And TS CAL licensing IS based on machine, NOT user, not only because it fits with the logic above (do you license a desktop OS to a user? No...it's licensed to THE MACHINE!) as explained here:
Q. Why do I need to allocate Terminal Services CALs to each device that connects to the terminal server? Why can't I allocate Terminal Services CALs to the server and use them concurrently?
A. Microsoft?s licensing for desktop applications and Windows terminal servers has always been on a per-device/per-seat basis. Windows 2000 Terminal Services is no different from Terminal Server 4.0 in that respect. This licensing model is appropriate for what the majority of Microsoft's customers are doing?deploying line-of-business applications to their users? desktops.
This can be a boon if you have multiple employees using the same desktop machine for TS access (only one TS CAL needed), or a bane if you have an employee using many different desktop machines for TS access (TS CAL needed for EACH desktop)
the ts license is only needed for each ts USER, not machine but USER. when you got to ts manager you will see a list of seats. that is filled not by machines but USERS, so it doesn't matter what the OS of the incoming client is as long as there is an available slot.
Wrong again. In fact, the previous quote addresses that VERY issue, since you are talking about something more akin to concurrent usage, which is expressly not supported by TS licensing (MS makes no provision for that kind of licensing for TS).
TS CALS ARE assigned per MACHINE. Look in the Terminal Server Licence Manager, and you will see it. The CALs are assigned to machines, since the machine name is listed. Also, if TS CALS were assigned by user and NOT by machine, then why would the following even be an issue at all:
License Transfer and Token Recovery
Q. What happens to the license token if I have to re-install the client's operating system?
A. If you upgrade the client's operating system, the license token is preserved?unless you reformat the client machine, or reset local flash memory on a Windows-based terminal. (If you do this, the license token will be lost). If the license token was issued to the device after the Terminal Services license token re-issuance hotfix was applied to the terminal server and the license server, the license token will automatically be recovered in either of the following ways:
If there are no more license tokens available, a temporary license token will be issued, which is valid for 90 days. The ?lost? token will become available on the license server 52-89 days after it was originally issued. After this period, the license token will be issued to the device the next time it connects to the terminal server.
If license tokens are available, a new license token will be issued to the newly formatted device. The ?lost? token will become available on the license server 52-89 days after it was originally issued, for another device to acquire.
or this:
Q. I need to transfer a Terminal Services CAL internally in my company from one client device to another. How do I accomplish this?
A. The Terminal Services CAL end user license agreement (EULA) is a per-seat license. It allows for a one-time, permanent transfer of the license to another client device. The transfer of any license token that was issued to a device after the license token re-issuance hotfix was applied will occur automatically.
or this:
Q. My device failed, and then failed again! Can I use the Terminal Services CAL again?
A. Yes. License tokens that were issued after the re-issuance hotfix will be automatically re-issued to a new device each time an existing device breaks. You will need to contact the customer services center to ask for a re-issue for any license tokens that were issued prior to the installation of the re-issuance hotfix.
Notice how in those three items only the words "DEVICE" or "DEVICES" are used? That's because--AGAIN--TS CALS are issued per device/machine, not per user!
the cal's that come with win2k pro have NOTHING to do with terminal services licensing.
You are EXACTLY right about that one thing.
Facebook
Twitter