Re: Help with Terminal Server Licensing

Tech-Archive recommends: Fix windows errors by optimizing your registry

I ust admit to having given up with ms and their licensing. I use a thing
called xp unlimited which I run on a xp machine and was £500 for unlimited
users

Why not take a look

Glenn

"Craig Mann" <craig.cm@xxxxxxxxxxxxxx> wrote in message
news:e3rXo8V$IHA.2244@xxxxxxxxxxxxxxxxxxxxxxx
Does anyone understand Terminal Server Licensing ? Looking on the
internet
it appears a lot of network administrators out there are having the same
issues as me, why is this so complicated?

I have purchased 12 Device CALs and have setup a Terminal Server License
Server and installed the CALs. I have configured a seperate server as a
Terminal Server. However the terminal server currently is in its 120 day
grace period. I want the License Server to issue the CALs to the Terminal
Server but the Terminal Server keeps prompting that there are no Terminal
Server Licensing Servers available, although the License Server can be
seen
on the network, can ping it etc and it's in the same domain / workgroup.
There are no firewalls so nothing is being blocked between the license
server and terminal server.

I'm resorting to this newsgroup because I have looked on the internet and
attempted all the resolutions that are out there such as enabling License
Server Security group in Group Policy on the License Server, but this
doesn't give me the Terminal Services Computer group as it suggests it
would
when enabled. I've tried creating the registry keys on the Terminal
Server,
this doesn't do anything and there is no where in Terminal Services
Configuration on the Terminal Server to point it to the license server.

Can anyone explain what is going on? Is this one of those Microsoft
flaws?!
I did read somewhere that Microsoft didn't finish their Terminal Server
coding in time before release of Windows 2003 Server ... is this my
problem?
Do I need to apply any patches or service packs? I've purchased my CALs,
Microsoft have had their money, how do I use the CA:Ls? Because I'm sure
that when this grace period expires it'll be prompting me to install the
CALs !

Many Thanks
Craig




.

Relevant Pages

  • RE: local computer client access license error
    ... the Terminal Server Licensing server only has Per User CALS. ... Windows Server 2003 does not manage User CALs. ... even though there is a User CAL in the license server database, ...
    (microsoft.public.windows.server.sbs)
  • 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: Changing TS Licensing Mode
    ... 822134 - The Function of Terminal Server CALs in Windows Server ... MCSE, CCEA, Microsoft MVP - Terminal Server ... One question I do have is that on the License ...
    (microsoft.public.windows.terminal_services)
  • RE: Event 1004 Terminal Server Cannot issue a client license
    ... by default Windows 2000 client/XP does not require license to connect ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Per User TS CALs, so don't buy those. ... is issued to the client, which is good for 30 days. ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Confused about CALs
    ... You mention that the 5 CALs that come with the server do not ... Terminal Services client connection. ... License Server must be activated within 120 days of using the ...
    (microsoft.public.windows.terminal_services)