Re: TS Licensing problem

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

W2K Pro and XP Pro clients that connect to a W2K terminal Server
*do* get a free TS CAL, but this TS CAL is *not* included in the
client OS. Instead, they receive a free TS CAL from the built-in
pool of "Existing Windows 2000 Per Device TS CAL tokens" on the TS
Licensing Server. That's why you have to install and activate a TS
Licensing Server. But you don't have to buy or install TS CALs on
it for these clients.

When connecting to a 2003 Terminal Server, *all* clients need a
purchased TS CAL. There is no free TS CAL for W2K Pro or XP Pro
clients connecting to a 2003 TS.

Check the EventLog on the Terminal Server to see the cause of the
problem. Check if the TS can locate the Licensing Server.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?R2lsbGVzNTU=?= <Gilles55@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 09 jun 2006 in microsoft.public.win2000.termserv.apps:

Using the following architecture:
- One NT4 Server (SP6) as Primary Domain Controller
- One Windows 2000 Server (SP3) as standard server with Terminal
Server - One Windows 2000-Pro workstation as remote desktop
client - One Windows XP-Pro SP2 as remote desktop client

Software licences: 99 users on the NT4 and 20 users Client
Access Licences for the W2000 server.

My first test installation has been done using a Windows 2000
SP2 server. The terminal licensing server was NOT activated:
everything went fine, remote connections OK for both clients.
naturally, I got the 90 days limitation problem, but when I read
Microsoft TS licensing info, they write about the FREE access to
TS when the remote client is a W2000 and/or XP-Pro (the "newest"
MS platforms) . So I did the upgrade from SP2 to SP3 and also
the TS activation. It has been properly activated... but when I
try to connect from my remote clients, I get the "infamous"
message "The client could not connect to the remote computer"!

What did I do wrong ? What is the exact position on Microsoft
about these remote clients ? Should I buy (again) additionals TS
CALs, and when yes, is it absolutely sure that this TS will
finally works ?

For information, I repeated the same procedure on another test
machine with W2000 Server SP3, TS not activated... and it's OK,
the client's certificates are placed in a temporary folder in TS
licensing server. The last step will be to activate this test
machine and check if the clients have still connection and now
are NO MORE in "temporary" folder ???

Many thanks to help me in this issue.
.

Relevant Pages

  • Re: Terminal Server 2000 in Workgroup to 2003 Domain
    ... state office kept logging on without pulling CALS or Built In Licenses. ... The MS Support person was not able to fix the problem of XP Pro clients ... Now we have an existing client with a temporary license. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: TS Licensing problem
    ... And is the server OS in Per Seat or Per Server ... client could not connect to the remote computer. ... Remote clients are W2000 ... but it wasn't my intention to mix up CALs ...
    (microsoft.public.win2000.termserv.apps)
  • Re: TS Licensing problem
    ... I don't see why my activated W2000 TS server does't ... the remote computer. ... Remote clients are W2000 Pro and XP-Pro machines. ... but it wasn't my intention to mix up CALs and TS CALs! ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Terminal Service License Server in sbs 2003
    ... You can also get free TS CALs for 2003 for every XP Pro for which ... a Terminal Server running windows 2000 without have to have purchase a TS ... temp license expires, which is why your clients work...for now. ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to log on to term servers from specific clients
    ... The licensing server is also ... a group of thin clients from ... > licensing server we have enough licenses. ... > to the terminal server. ...
    (microsoft.public.win2000.termserv.clients)