Re: can someone help clear this up?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Chris (Chris_at_discussions.microsoft.com)
Date: 01/08/05 

Date: Sat, 8 Jan 2005 14:07:03 -0800

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" wrote:

> 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.
>
>
>
> "Chris" <Chris@discussions.microsoft.com> wrote in message
> news:071AF2AC-F6DE-4737-B666-C6F3D4830CF9@microsoft.com...
> >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.....
>
>
>

Relevant Pages

  • RE: Remote connectivity problems
    ... do you mean you have added a remote client to SBS ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Services Remote Control
    ... You don't need the Remote Desktop Client on the server, ... how do I get Remote Control ...
    (microsoft.public.win2000.termserv.apps)
  • Re: RWW Disconnecting
    ... I have been connected from a remote site for about 3 ... DHCP server and even a wireless access ... the key codes to for Internet access. ... Client Workstations} ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW Disconnecting
    ... Server to test the issue. ... I understand that remote client encounts following error message when RWW ... I strongly suggest that we rerun the Configure E-mail and Internet ...
    (microsoft.public.windows.server.sbs)
  • Re: can someone help clear this up?
    ... Terminal Services Client Access Licenses are assigned to the client, ... The Terminal Services License Server ...
    (microsoft.public.win2000.termserv.clients)