Help with Terminal Server Licensing

  • Thread starter Thread starter Craig Mann
  • Start date Start date
C

Craig Mann

Guest
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
 
Re: Help with Terminal Server Licensing

Hello Craig,

Is the license server activated:
http://technet.microsoft.com/en-us/library/cc740046.aspx

http://technet.microsoft.com/en-us/library/cc759642.aspx

See also here:
http://technet.microsoft.com/en-us/library/cc738962.aspx

http://technet.microsoft.com/en-us/library/cc783401.aspx

http://technet.microsoft.com/en-us/library/cc738426.aspx

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> 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
 
Re: Help with Terminal Server Licensing

Craig,
Its really quite straightforward, so the problem is going to be in
discovering where you are are going wrong.
- when you say you have installed the CALs, obviously you have activated the
Licensing server?
- On the Licensing server, what licenses are shown as installed and used?
- when you use the TS Licensing mmc from the TS server, does it discover the
Licensing server?
- In your AD, under the Site, do you see a TS Licensing server?
- what registry key have you changed?
Anthony,
http://www.airdesk.com



"Craig Mann" <craig.cm@ardentia.co.uk> wrote in message
news:e3rXo8V$IHA.2244@TK2MSFTNGP05.phx.gbl...
> 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
>
>
 
Re: Help with Terminal Server Licensing

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@ardentia.co.uk> wrote in message
news:e3rXo8V$IHA.2244@TK2MSFTNGP05.phx.gbl...
> 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
>
>
 
Back
Top