Terminal Service Licensing

[owensdj]

I need to add a new Windows Server 2003 machine to an Active Directory domain dedicated to being a Terminal Server for 2 Windows XP Pro clients who will connect over a VPN. If I get Windows Server 2003 OEM with 5 clients, will that allow 5 Terminal Server clients? I wasn't sure of CALs and TSCALs were interchangable or if TSCALs were a different type of license.

 

[spyordie007]

well I'm not sure if 2003 is differant from 2000 or not, but assuming it hasnt changed drastically than you will not need to purchase additional TSCALs if you are using Windows XP Pro. or Windows 2000 Pro. Just select "client licensing" when you set it up.

The times you need to get TSCALs is when you have thin clients that will be accessing your terminal server (and not running XP/2K pro.)

http://www.microsoft.com/windows2000/server/howtobuy/pricing/tsfaq.asp

-Spy

EDIT: looks like it's changed a little with Windows 2003 Server, you can only use XP Pro. without buying additional TSCALs:
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ts2003.mspx

 

[stash]

^^
Thats not quite correct. ALL clients connecting to a 2003 TS require a TSCAL. Built-in CALS do not work on 2003 Terminal Servers.

Edit: Let me expand on that a little. If you are running a WS2003 terminal server, you WILL need to buy separate TSCALS for any type of OS connecting to the TS. Remember you need to run a license server for TS in app mode. When you install a TS in application mode, you have a 120 grace period to install a license server. Once you install a license server, you have another 120 days to install TSCALS on it.

 

[spyordie007]

ahh I see what you mean:

With Windows 2000 TS licensing, if a client device is running the most recent version of the Windows desktop operating system (OS), a TS CAL is not required to satisfy the licensing requirement. However, with Windows Server 2003, a TS CAL will be required for each Device or User using TS functionality, irrespective of which desktop operating system is running on the Device.

I stand corrected, you will indeed need at least 2 tscals.

 

[stash]

Yeah, trust me, I understand the confusion. TS licensing is one of the most popular calls at PSS.

 

[owensdj]

STaSh, thanks for the explaination. That clears up the confusion for me.

Isn't the Terminal Service licensing different with Windows 2000 Server when you're connecting to the Terminal Server using a Windows 2000 or XP Pro client running Remote Desktop Connection? Isn't it true that these clients can connect to the Terminal Service on a Windows 2000 Server without having to buy a TSCAL for them?

 

[stash]

Yes that's right. Windows 2000 terminal servers allowed 2000 and XP clients to connect using the built in CALS--no additional purchase was necessary for these clients. This was changed for 2003 terminal servers.

Some other things to remember that we get a lot of calls on: If you are running a 2003 terminal server in application mode, you MUST use a 2003 license server. So if you currently have 2000 terminal servers, and a 2000 license server and you decide to upgrade or add a 2003 TS, you must also upgrade the license server to 2003. 2003 license servers can give out both 2003 and 2000 CALS; 2000 license servers can only give out 2000 CALs...they do not know what 2003 CALs are.

In 2000, you had to put the license server on a domain controller. (There are ways around this, but thats another topic). In 2003, this is no longer a requirement, and you can now put the license server on any member server or domain controller.