• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 272
  • Last Modified:

O/S license requirements for a thin client connecting to Windows 2003 Server Terminal Services

In my enviroment I have windows 2003 Servers with Terminal Services running, providing Desktop sessions to my users via Thin Clients.  I am trying to double check my licensing.  I have my W2k3 server CAL's and my W2k3 Terminal Services Cal's, but do I need a actual workstation O/S license for each thin client?
0
rongillis
Asked:
rongillis
  • 2
1 Solution
 
centrepcCommented:
Each thin client will come with its own licensed operating system.  Usually winCE linux or if they are more expensive ones they can come with 2000 pro or XP Pro embedded.  

If they have XP Pro embedded then you don't even need a 2003 tcal.  You only need tcals for clients that are not running xp pro.  

If you are asking about regular client access licenses on the server you do need as many client access licenses on the the server as you will have simultaneous connections to the server in addition to the tcals for clients that are not XP Pro.

example  if you have 30 users total, 20 wince thin clients, 10 winxp pro workstations, you will need 30 cals and 20 tcals
0
 
oBdACommented:
Server 2003 in Application Mode requires one TS CAL for *every* client, no matter which OS. TS CALs were only included in W2k/XP pro for access to a Terminal Server running Windows 2000.
Furthermore, TS CALs are NOT concurrent; depending on the licensing mode, you need one license for each user/device accessing the terminal server; you can only re-assign TS CALs if a device is taken off completely, or the user doesn't access the terminal server anymore.

The Ultimate Guide to Windows 2003 Terminal Server Licensing
http://www.brianmadden.com/content/content.asp?ID=154

The Function of Terminal Server CALs in Windows Server 2003
http://support.microsoft.com/?kbid=822134

Windows Server 2003 Terminal Server Licensing
http://www.microsoft.com/windowsserver2003/techinfo/overview/termservlic.mspx

Windows Server 2003 Terminal Server Licensing Issues and Requirements for Deployment
http://support.microsoft.com/?kbid=823313

What's New in Windows Server 2003 Licensing
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/overview.mspx
0
 
rongillisAuthor Commented:
I understand what you are all saying and perhaps I am crazy, but..... From what I remember back with NT 4.0 Terminal Server,  each thin client connecting had to have a NT Workstation license.  Not for the right to connect to the terminal server, but because the terminal server was providing the thin client user with a NT Workstation Desktop.   Thus MS felt there were not getting screwed out of selling a workstation O/S license because you were using terminal server.  Does this still hold true, or was it never the case?
0
 
oBdACommented:
That's what the TS CAL is for ...
Read the "Ultimate Guide"; it's the most comprehensive explanation of TS licensing you can find. Quoted from there:
"[...] To legally access a Windows 2003 Terminal Server, each client seat requires each of the following licenses:
Windows Server 2003 Client Access License.
Windows Server 2003 Terminal Server Client Access License."
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now