I really should use Lookout (www.lookoutsoft.com) to search before I say I can't find things :-p
 
From the Sunbelt NTSYSADMIN list just last week:
 
<snip>
 
 
"Terminal Server for Windows Server 2003 (known as Application Server mode in Windows 2000 Server) provides application deployment and management for users on a variety of devices through its application server mode. Each device or user who initiates a session on a terminal server running Windows Server 2003 must be licensed with one of the following:
1. Windows Server 2003 Terminal Server Device Client Access License.
2. Windows Server 2003 Terminal Server User Client Access License.
3. Windows Server 2003 Terminal Server External Connector."
 
Which answers your first question (you have the right Cals).
 
Some other useful information in the doco;
 
  • A Windows 2000 Terminal server can authenticate against a Windows 2003 Terminal Server licencing server
  • A Windows 2003 Terminal server cannot authenticate against a Windows 2000 Terminal Server licencing server
Therefore: "...when upgrading terminal servers running Windows 2000, you need to install and activate a licensing server that runs Windows Server 2003, which communicates with terminal servers that run both Windows 2000 and Windows Server 2003"
 
Also in this document are numerous "Preferred Licence Server scripts" that perform various self-explanatory tasks like;
 
AddLicenceServer.vbs
DeleteLicenceServer.vbs
QueryLicenceServer.vbs
 
Apart from that you can always try the helpful links at the end;
 

            Windows Server 2003 Terminal Services

http://www.microsoft.com/windowsserver2003/technologies/terminalservices/ or  http://go.microsoft.com/fwlink/?LinkId=18340

            Microsoft Windows Server 2003

http://www.microsoft.com/windowsserver2003 or  http://go.microsoft.com/fwlink/?LinkId=17533

            Windows Server 2003 Terminal Server Licensing Issues and Requirements for Deployment  

http://support.microsoft.com/?id=823313 or http://go.microsoft.com/fwlink/?LinkId=23444

            Terminal Services FAQ

http://www.microsoft.com/windowsserver2003/community/centers/terminal/terminal_faq.mspx#XSLTfaqSection121123121120120 or http://go.microsoft.com/fwlink/?LinkId=23445

For additional information about the deployment and management of the Terminal Server Licensing service, see the Windows Server 2003 Resource Kit and the Deployment Planning Guide in the Microsoft® Windows® Server 2003 Resource Kit at http://www.microsoft.com/windowsserver2003/techinfo/reskit/deploykit.mspx or http://go.microsoft.com/fwlink/?LinkId=4298

 
</snip>
 
Thanks to Antonio Carrano for his post!!
 
Hope this is of help - I've not followed the links myself as we're not likely to go 2003 TS for some time yet - but I live in hope.....
 
Jack


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: 04 May 2004 16:18
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] 2000 Terminal Services Licensing Server and Windo ws Server 2003 TS

Mark,
 
I've read somewhere recently (although I'm not sure where :-]) that you do require 2003 Licensing servers for 2003 TS.... but 2003 Licensing servers can deal with 2000 TS..... I'll try and track down the article if I can...
 
Jack 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Creamer, Mark
Sent: 04 May 2004 15:48
To: [EMAIL PROTECTED]
Subject: [ActiveDir] 2000 Terminal Services Licensing Server and Windows Server 2003 TS

I haven’t been able to locate a definitive answer for this yet, so I wanted to make sure I have this right  before I pass on the info to the project manager.

 

We have no Windows 2003 domain controllers yet, only 2000. However, we are planning to start deploying some Windows 2003 terminal servers. My question is, can the 2003 terminal servers use the current Windows 2000 DC that acts as our TS licensing server to maintain their licenses, or do they require the licensing server to be 2003?

 

Thanks!

 

Mark Creamer

Systems Engineer

Cintas Corporation

Honesty and Integrity in Everything We Do

 

Reply via email to