|
Posted: Jan. 13, 2003
This table outlines the various scenarios for accessing Windows .NET
Terminal Server with Terminal Server Client Access Licenses (TS CALs) and how these
scenarios have changed from Windows 2000 Terminal Server. Note that under Windows .NET
Terminal Server, TS CALs can be applied to either users or devices.
| Scenario |
Client
Type |
Windows
2000 Terminal Server |
Windows
.NET Terminal Server |
| Employees accessing applications
via terminal services |
Windows XP Professional without upgrade
rights, purchased before Windows Server 2003 ships |
No TS CAL purchase
required. |
TS CAL must be obtained (at no charge) from
Microsoft for each device or user. |
| Windows XP Professional without upgrade
rights, purchased after Windows Server 2003 ships |
TS CAL must be purchased for each device or
each user. |
| Windows desktop covered by an Enterprise
Agreement, Software Assurance, or Upgrade Advantage before Windows Server 2003
ships |
TS CAL must be obtained (at no charge) from
Microsoft for device or user. |
| Windows desktop covered by an Enterprise
Agreement, Software Assurance, or Upgrade Advantage after Windows Server 2003 ships |
TS CAL must be purchased. |
| Windows NT, 9.x |
TS CAL must be purchased for each
device. |
TS CAL must be purchased for each device or
each user. |
| Anonymous Internet users accessing
applications over the Internet via terminal services |
Any client |
Server must have Terminal Server
Internet Connector. Limited to maximum of 200 anonymous connections (authentication not
permitted). |
Server must have Terminal Server External
Connector. Unlimited number of authenticated connections. |
| Authenticated business partners accessing
applications over the Internet via terminal services |
Any client |
Scenario not supported. No CAL
available. |
Server must have Terminal Server External
Connector. Unlimited number of connections. Or, TS CAL can be
purchased for each external device or user. |
 |
|
