can someone help clear this up?

[Guest]

I have two Windows 2003 servers (standard 5 CAu, Enterprise 25 CAU), and I'm
a developer accessing them with a Windows 2K client.
I've read the difference in how TS was used in Win2K but am still confused.
Do I need to install TS to access remotely these server to perform my
duties, or do I use remote desktop?
If I have the above mentioned servers, do they come with CAU for TS
automatically )i.e. like Win2K sever did)??? Do I have to then purchase on
top of the server CAU's I have more for TS? Or do I just activate ones that I
have via the win2003 OS purchase?
Do I need to make the Domain Controller server the TS licensing server?
I've been accessing them until just recently, one has locked me out
"Terminal Service has ended the conntection" and the hotfix Ijust applied
didn't do the trick. I assume something else is going on???
Help.....

 

[Bruce Sanderson]

1) The Remote Desktop Client that comes with Windows XP or that is
downloadable from the MS web site
(http://www.microsoft.com/windowsxp/downloads/tools/rdclientdl.mspx) is a
Terminal Services Client and replaces the older TS client - you don't need
to install any additional software on the client computer.

2) not sure what you mean by a CAU. A Windows 2003 Server Client Access
License (Server CAL) is not the same thing as a Windows 2003 Terminal
Services Client Access License (2003 TS CAL).

3) No MS operating system comes with built-in Windows 2003 Terminal Services
Client Access Licenses (TS CAL) - they must be purchased seperatly. This is
a change from Windows 2000 Terminal Services. However, if you bought
Windows XP licenses prior to April 24, 2003, you may be eligible to get
Windows 2003 TS CALs for free - see
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/overview.mspx#transition.

4) Windows 2003 Terminal Services License Server can be installed on any
Windows 2003 Server - it does not have to be installed on a Domain
Controller. The document at
http://www.microsoft.com/windowsserver2003/techinfo/overview/termservlic.mspx
is a very good document about Windows 2003 Terminal Services License
Server - how to install and configure etc.

5) Windows 2003 comes with the equivalent of "Windows 2000 Terminal Services
in Remote Administration Mode" already installed. Up to two administrators
can concurrently connect to a Windows 2003 Server without having "Terminal
Services" actually installed - no TS CALs are required for this.

6) as to the "...ended the connection" I suggest looking in the Event Log on
the Windows 2003 Server for relevant entries.

--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.

 

[Guest]

Thanx.

what was confusing, and correct me if I'm wrong, that Win2K Servers have the
TS CAU's available for use (typically 5 CAL's, but of course the admin
account can always login through TS). And the activation of those TS licenses
was pretty straight forward.
Now it appears that MS has allowed, as you say and I have configured now,
two remote admin desktop users at the same time. But stripped the parellel TS
licenses (with the OS CAU's) as in Win2K.
Interesting. I do like remote desktop.
As for the client, I just installed the 2 floppies disks that are created
via a Win2K server for TS, and then access my Win2003 servers through remote
desktop using that client software.
I believe that XP allows this through either win explorer or IE?

So isn't it a server license, not client, since it's the "account" that
access the services.
And for the error, I uninstalled the TS licensing server and I'm fine now.

Thanx Bruce for your information and links.

 

[Bruce Sanderson]

1) Terminal Services Client Access Licenses are assigned to the client, not
the Server running Terminal Services. The Terminal Services License Server
hands out the license tokens to clients and manages how many of what kind
have been handed out and to which clients. For Windows 2003 a "client" can
be a Device or a User (Windows 2000 TS only has Per Device licensing). You
decide at the time of TS License Token installation whether the License is
for Per User or Per Device.

2) Windows 2000 (and Windows 2003) Server does not ship with any Terminal
Services CALs. For Windows 2003 Terminal Services, that means that no
client computers or users can use Terminal Services without acquiring
Windows 2003 Terminal Services Client Access Licenses. If I recall
correctly, the basic Windows Server license includes 5 SERVER Client Access
Licenses which allows five client computers to use the Server's basic
functions (authentication, file sharing, printer sharing etc.), but NOT
Terminal Services. The 5 you have for the 2003 Standard Server and 25 for
the Enterprise Server are most likely SERVER CALS, not Terminal Services
CALs, unless you specifically acquired Terminal Services CALs. Terminal
Services CALs have always been seperate. To use Terminal Services, a client
needs both a SERVER CAL and a Terminal Services CAL. Terminal Services
provide for Temporary Licenses 120 days) before a License Server Service is
installed and License Tokens added.

3) Windows 2000 Professional and Windows XP Professional licenses
essentially "include" a Windows 2000 Terminal Services CAL, so these client
OSs can use Windows 2000 Terminal Services without additional cost. There
is no equivalent "included" license for Windows 2003 Terminal Services (but
see item 3 in my previous post).

4) The Remote Desktop Client package (from
http://www.microsoft.com/windowsxp/downloads/tools/rdclientdl.mspx) can be
installed on any Windows version, including Windows 2000 Professional. An
earlier version of this client is included with Windows XP.

5) To connect to another computer from a Windows XP computer, or any
computer with the RDP client (see 4 above):
Start, All Programs, Accessories, Communications, Remote Desktop
Connection
This RDP client can connect (with appropriate permissions and licenses)
to:
- Windows XP Pro (no license required)
- Windows 2000 Server with Terminal Services installed in Remote
Administration Mode (no license required)
- Windows 2000 Server with Terminal Services installed in Application
Mode - TS CAL required but built in to 2000 and XP Pro
- Windows 2003 Server without Terminal Services installed (no license
required)
- Windows 2003 Server with Terminal Services installed - 2003 TS CAL
required - must be purchase seperately

6) If you actually have Windows 2003 the Terminal Services component
installed (it will show up in Control Panel, Add or Remove Programs,
Add/Remove Windows Components with a check mark beside it) on your Windows
2003 servers and had a Windows 2003 Terminal Services License Server
installed, Activated and working, then uninstalled the Windows 2003 License
Service, you are most likely working on borrowed time because Per Device
license tokens handed out to client computers will expire after about 120
days. See
http://www.microsoft.com/windowsserver2003/community/centers/terminal/tsfaq_matrix.mspx.
If you are using Per User licenses, connection will be refused if a License
Server is not available.

Other TS Licensing links:
http://www.microsoft.com/windowsserver2003/community/centers/terminal/terminal_faq.mspx
- see in particular the answer to How do I configure Terminal Services
Licensing (TSL) servers for redundancy or high availability?
http://support.microsoft.com/?id=822134
http://support.microsoft.com/?id=823313
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ts2003.mspx
http://www.microsoft.com/technet/pr.../technologies/security/ws03mngd/22_s3trm.mspx

--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.