PC Review Forums Newsgroups Windows 2000 Microsoft Windows 2000 Terminal Server Applications Terminal Server Licensing of Windows Server 2003 again

Reply

Terminal Server Licensing of Windows Server 2003 again

 
Thread Tools Rate Thread
Old 17-12-2004, 08:21 AM   #1
=?Utf-8?B?VmVyYVVrcg==?=
Guest
 
Posts: n/a
Default Terminal Server Licensing of Windows Server 2003 again


The description of the situation:
Our firm bought Microsoft Windows Server Standard 2003 Russian and such
client licenses as:
1) Microsoft Windows Server CAL 2003 Russian OPEN No Level User CAL (10);
2) Microsoft Windows Terminal Svr CAL 2003 Russian OPEN No Level User CAL (5)

I installed this server as a server in a workgroup on 17.8.04 and chose
roles of the Terminal server and the File server for it.
After this installation I received such a message in the Event log:
TermService ID:1027 (the Terminal server can't find the license server in
the workgroup PRINT_GROUP.... (texts of messages are not precise as I
translate them from Russian to English)).
This server is the only Windows server in the network. That's why I began to
install the license server on the same computer. As this computer has no
access to Internet I chose licensing by phone. After installing the License
server of Terminal service such messages appeared in the Event log:

1) Service Control Manager ID: 7035
2) Service Control Manager ID:7036
3) TermServLicensing ID:18 (Terminal Service Licensing on the server PRN2003
is not activated)

I didn't activate the license server till 27.10.04 and clients of the server
received notification that their temporary license will expire in N days.

I called to the Microsoft service by phone which I received during
installation of the license service on the 27.10.04 and received from them
the ID of the license server and the code of the key packet of client
licenses.
I activated the license server with these codes.

After that clients stopped to receive notifications, I saw that the license
server is activated at the Terminal service licensing panel.

So, after installing and activating of the license server the situation on
this server is as follows:
1) at the panel "Control of this server" the message appeared: " The
terminal service license server was found in the network"
2) Administration -> Services
a) TermServLicensing
the type of launching: Auto
the state: working
b) TermService
the type of launching: Manually
the state: working
3) Terminal service Licensing
PRN2003 Activated
The token of client licenses (CAL) of the terminal server Windows Server
2003 (per user):

the type - open
Total : 5
Available : 5
In use: 0

4) Information in the Registry
a)HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\Parameters\DomainLicenseServerMult
b)HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermServLicensing\Parameters
Role is equal 0
c) as I had doubts about the fact that I installed the terminal server and
the license server at the same computer I add the NetBios name of this
computer to the Registry as the name of license server
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters\LicenseServers\PRN2003

------------------------------------------------------------------------------------------------
After all those actions I thought that all is ok with licensing of terminal
service, but suddenly such message appeared in the Event log on 25.11.04:

TermService ID:1009
The favourable period of licensing of the terminal server on 25.11.04 will
finish soon, but the server was not registered on the license server...

This message appeared once a day till 10.12.04 and then stopped to appear.

When this message appeared I tested carefully all things concerning
licensing at the server and found several disturbing me things:

1) Licensing
After installation of Windows Server 2003 such a message appeared there when
I try to open this feature:
License service doesn't work on \\PRN2003 or \\PRN2003 is unavailable
When I click OK, the system ask for the domain which I have no.

This situation didn't change after installation and activation of the
license server

2) Administration -> Services
License Service

the type of launching: Stopped
the state: Stopped

------------------------------------------------------------------------------------------------

In these circumstances is the only way for me to deactivate the license
server and then activate it anew?


  Reply With Quote
Old 17-12-2004, 12:46 PM   #2
Vera Noest [MVP]
Guest
 
Posts: n/a
Default Re: Terminal Server Licensing of Windows Server 2003 again

I can't promise that this solves the whole situation, but there are 2
things that seem to apply to your situation:

1) You have bought and installed Per User licenses, but is the
Terminal Server also set to use the Per User licensing mode?
The default is "Per Device".
You can check this from Administrative Tools - Terminal Services
Configuration - Server Settings
If it's set to Per Device mode, it will look for a Device TS CAL and
will not issue your Per User TS CALs.

Check this article, it explains that even after you have
switched licensing mode on the TS, your Per User TS CAL count will
not be decremented:

822134 - The Function of Terminal Server CALs in Windows Server
2003
http://support.microsoft.com/?kbid=822134

2) The Event 1009 that you saw can be caused by a known problem, in
which case it is easy to solve:
885013 - Event ID 1009 is logged on a Terminal Server License server
in a Windows Server 2003-based domain
http://support.microsoft.com/?kbid=885013

Hope this helps!

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"=?Utf-8?B?VmVyYVVrcg==?=" <VeraUkr@discussions.microsoft.com>
wrote on 17 dec 2004:

> The description of the situation:
> Our firm bought Microsoft Windows Server Standard 2003 Russian
> and such client licenses as:
> 1) Microsoft Windows Server CAL 2003 Russian OPEN No Level User
> CAL (10); 2) Microsoft Windows Terminal Svr CAL 2003 Russian
> OPEN No Level User CAL (5)
>
> I installed this server as a server in a workgroup on 17.8.04
> and chose roles of the Terminal server and the File server for
> it. After this installation I received such a message in the
> Event log: TermService ID:1027 (the Terminal server can't find
> the license server in the workgroup PRINT_GROUP.... (texts of
> messages are not precise as I translate them from Russian to
> English)). This server is the only Windows server in the
> network. That's why I began to install the license server on the
> same computer. As this computer has no access to Internet I
> chose licensing by phone. After installing the License server of
> Terminal service such messages appeared in the Event log:
>
> 1) Service Control Manager ID: 7035
> 2) Service Control Manager ID:7036
> 3) TermServLicensing ID:18 (Terminal Service Licensing on the
> server PRN2003 is not activated)
>
> I didn't activate the license server till 27.10.04 and clients
> of the server received notification that their temporary license
> will expire in N days.
>
> I called to the Microsoft service by phone which I received
> during installation of the license service on the 27.10.04 and
> received from them the ID of the license server and the code of
> the key packet of client licenses.
> I activated the license server with these codes.
>
> After that clients stopped to receive notifications, I saw that
> the license server is activated at the Terminal service
> licensing panel.
>
> So, after installing and activating of the license server the
> situation on this server is as follows:
> 1) at the panel "Control of this server" the message appeared: "
> The terminal service license server was found in the network"
> 2) Administration -> Services
> a) TermServLicensing
> the type of launching: Auto
> the state: working
> b) TermService
> the type of launching: Manually
> the state: working
> 3) Terminal service Licensing
> PRN2003 Activated
> The token of client licenses (CAL) of the terminal
> server Windows Server
> 2003 (per user):
>
> the type - open
> Total : 5
> Available : 5
> In use: 0
>
> 4) Information in the Registry:
> a)HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\Paramete
> rs\DomainLicenseServerMulti
> b)HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermS
> ervLicensing\Parameters
> Role is equal 0
> c) as I had doubts about the fact that I installed the
> terminal server and
> the license server at the same computer I add the NetBios name
> of this computer to the Registry as the name of license server:
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermSer
> vice\Parameters\LicenseServers\PRN2003
>
> -----------------------------------------------------------------
> ------------------------------- After all those actions I
> thought that all is ok with licensing of terminal service, but
> suddenly such message appeared in the Event log on 25.11.04:
>
> TermService ID:1009
> The favourable period of licensing of the terminal server on
> 25.11.04 will finish soon, but the server was not registered on
> the license server...
>
> This message appeared once a day till 10.12.04 and then stopped
> to appear.
>
> When this message appeared I tested carefully all things
> concerning licensing at the server and found several disturbing
> me things:
>
> 1) Licensing
> After installation of Windows Server 2003 such a message
> appeared there when I try to open this feature:
> License service doesn't work on \\PRN2003 or \\PRN2003 is
> unavailable When I click OK, the system ask for the domain which
> I have no.
>
> This situation didn't change after installation and activation
> of the license server
>
> 2) Administration -> Services
> License Service
>
> the type of launching: Stopped
> the state: Stopped
>
> -----------------------------------------------------------------
> -------------------------------
>
> In these circumstances is the only way for me to deactivate the
> license server and then activate it anew?

  Reply With Quote
Old 20-12-2004, 02:09 AM   #3
v_sajit@hotmail.com
Guest
 
Posts: n/a
Default Re: Terminal Server Licensing of Windows Server 2003 again

> Hi Vera
1. If you have reinstalled the License Server then you need
to get a new LServer ID from activate.microsoft.com
2.Start/Run/services.msc
check whether Terminal Server Licensing service is running
in automatic mode
3.%systemroot%/system32/LServer
Check how many LServer folders do you have
4. You have already added the LicenseServers key to help
discovery. though download LSview.exe from
microsoft.com/downloads install it and run it
5.The Terminal server 2003 comes only in the application
server mode and bydefault it will be installed in per device
mode
As you have user cals change the mode from terminal services
configuration/server settings to user mode

If you find that this is not working then follow these steps

1. Stop the Terminal Server Licensing service and put it in
manual mode : Start/run/services.msc
2.rename the Lserver folder in %systemroot%/system32 to
LServerold, if you have more than one then rename all as
Lserverold1-2 etc.
3.Open Terminal Server Licensing and click on you server
(If it is activated it will have a green mark otherwise red,
this would be yellow)..then click on Action on the top,
click Install licenses set connection to telephone and get
your present LServer ID which would be below the Product ID
on the CAL installation wizard.
4.Uninstall Terminal Services Licensing from add/remove
programs
5.Install it back after a reboot
6.Go to activate.microsoft.com and reactivate your License
Server: get anew Lserver ID
7.Enter that on the server activation wizard in Terminal
Server Licensing
8.Call MSclearing house and get the cals reissued or may be
try installing them on the same website
9.CAL installation might not work on the website as it
already was issued.

Good Luck

Let me know if you need more help

> The description of the situation:
> Our firm bought Microsoft Windows Server Standard 2003
> Russian and such client licenses as:
> 1) Microsoft Windows Server CAL 2003 Russian OPEN No Level
> User CAL (10); 2) Microsoft Windows Terminal Svr CAL 2003
> Russian OPEN No Level User CAL (5)
>
> I installed this server as a server in a workgroup on
> 17.8.04 and chose roles of the Terminal server and the
> File server for it. After this installation I received
> such a message in the Event log: TermService ID:1027
> (the Terminal server can't find the license server in the
> workgroup PRINT_GROUP.... (texts of messages are not
> precise as I translate them from Russian to English)).
> This server is the only Windows server in the network.
> That's why I began to install the license server on the
> same computer. As this computer has no access to Internet
> I chose licensing by phone. After installing the License
> server of Terminal service such messages appeared in the
> Event log:
>
> 1) Service Control Manager ID: 7035
> 2) Service Control Manager ID:7036
> 3) TermServLicensing ID:18 (Terminal Service Licensing on
> the server PRN2003 is not activated)
>
> I didn't activate the license server till 27.10.04 and
> clients of the server received notification that their
> temporary license will expire in N days.
>
> I called to the Microsoft service by phone which I
> received during installation of the license service on
> the 27.10.04 and received from them the ID of the license
> server and the code of the key packet of client licenses.
> I activated the license server with these codes.
>
> After that clients stopped to receive notifications, I saw
> that the license server is activated at the Terminal
> service licensing panel.
>
> So, after installing and activating of the license server
> the situation on this server is as follows:
> 1) at the panel "Control of this server" the message
> appeared: " The terminal service license server was found
> in the network" 2) Administration -> Services
> a) TermServLicensing
> the type of launching: Auto
> the state: working
> b) TermService
> the type of launching: Manually
> the state: working
> 3) Terminal service Licensing
> PRN2003 Activated
> The token of client licenses (CAL) of the terminal
> server Windows Server 2003 (per user):
>
> the type - open
> Total : 5
> Available : 5
> In use: 0
>
> 4) Information in the Registry:
>
> a)HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\Parame
> ters\DomainLicenseServerMulti
>
> b)HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Ter
> mServLicensing\Parameters Role is equal 0
> c) as I had doubts about the fact that I installed the
> terminal server and the license server at the same
> computer I add the NetBios name of this computer to the
> Registry as the name of license server:
>
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermS
> ervice\Parameters\LicenseServers\PRN2003
>
> ----------------------------------------------------------
> -------------------------------------- After all those
> actions I thought that all is ok with licensing of
> terminal service, but suddenly such message appeared in
> the Event log on 25.11.04:
>
> TermService ID:1009
> The favourable period of licensing of the terminal server
> on 25.11.04 will finish soon, but the server was not
> registered on the license server...
>
> This message appeared once a day till 10.12.04 and then
> stopped to appear.
>
> When this message appeared I tested carefully all things
> concerning licensing at the server and found several
> disturbing me things:
>
> 1) Licensing
> After installation of Windows Server 2003 such a message
> appeared there when I try to open this feature:
> License service doesn't work on \\PRN2003 or \\PRN2003
> is unavailable When I click OK, the system ask for the
> domain which I have no.
>
> This situation didn't change after installation and
> activation of the license server
>
> 2) Administration -> Services
> License Service
>
> the type of launching: Stopped
> the state: Stopped
>
> ----------------------------------------------------------
> --------------------------------------
>
> In these circumstances is the only way for me to
> deactivate the license server and then activate it anew?
>
>

  Reply With Quote
Old 20-12-2004, 10:07 AM   #4
=?Utf-8?B?VmVyYVVrcg==?=
Guest
 
Posts: n/a
Default Re: Terminal Server Licensing of Windows Server 2003 again

Dear Vera,
thank u for ur help.

First of all, concerning User licensing mode... I tested it once more as u
recommended to me and ensured once more that it WAS set in PER USER mode
already.

Concerning ur second recommendation... Do I really need to add
LicensingGracePeriodEnded parameter in the Registry if the Event ID 1009
stopped to appear in the event log already as I wrote in my question?

Best regards
Vera

"Vera Noest [MVP]" пишет:

> I can't promise that this solves the whole situation, but there are 2
> things that seem to apply to your situation:
>
> 1) You have bought and installed Per User licenses, but is the
> Terminal Server also set to use the Per User licensing mode?
> The default is "Per Device".
> You can check this from Administrative Tools - Terminal Services
> Configuration - Server Settings
> If it's set to Per Device mode, it will look for a Device TS CAL and
> will not issue your Per User TS CALs.
>
> Check this article, it explains that even after you have
> switched licensing mode on the TS, your Per User TS CAL count will
> not be decremented:
>
> 822134 - The Function of Terminal Server CALs in Windows Server
> 2003
> http://support.microsoft.com/?kbid=822134
>
> 2) The Event 1009 that you saw can be caused by a known problem, in
> which case it is easy to solve:
> 885013 - Event ID 1009 is logged on a Terminal Server License server
> in a Windows Server 2003-based domain
> http://support.microsoft.com/?kbid=885013
>
> Hope this helps!
>
> --
> Vera Noest
> MCSE,CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> *----------- Please reply in newsgroup -------------*
>


  Reply With Quote
Old 20-12-2004, 10:21 AM   #5
=?Utf-8?B?VmVyYVVrcg==?=
Guest
 
Posts: n/a
Default Re: Terminal Server Licensing of Windows Server 2003 again



"v_sajit@hotmail.com" пишет:

> > Hi Vera

> 1. If you have reinstalled the License Server then you need
> to get a new LServer ID from activate.microsoft.com
> 2.Start/Run/services.msc
> check whether Terminal Server Licensing service is running
> in automatic mode
> 3.%systemroot%/system32/LServer
> Check how many LServer folders do you have
> 4. You have already added the LicenseServers key to help
> discovery. though download LSview.exe from
> microsoft.com/downloads install it and run it
> 5.The Terminal server 2003 comes only in the application
> server mode and bydefault it will be installed in per device
> mode
> As you have user cals change the mode from terminal services
> configuration/server settings to user mode
>
> If you find that this is not working then follow these steps
>
> 1. Stop the Terminal Server Licensing service and put it in
> manual mode : Start/run/services.msc
> 2.rename the Lserver folder in %systemroot%/system32 to
> LServerold, if you have more than one then rename all as
> Lserverold1-2 etc.
> 3.Open Terminal Server Licensing and click on you server
> (If it is activated it will have a green mark otherwise red,
> this would be yellow)..then click on Action on the top,
> click Install licenses set connection to telephone and get
> your present LServer ID which would be below the Product ID
> on the CAL installation wizard.
> 4.Uninstall Terminal Services Licensing from add/remove
> programs
> 5.Install it back after a reboot
> 6.Go to activate.microsoft.com and reactivate your License
> Server: get anew Lserver ID
> 7.Enter that on the server activation wizard in Terminal
> Server Licensing
> 8.Call MSclearing house and get the cals reissued or may be
> try installing them on the same website
> 9.CAL installation might not work on the website as it
> already was issued.
>
> Good Luck
>
> Let me know if you need more help
>


Dear v_sajit,
first of all thank u for ur help. Now concerning those actions that u
recommended to me...
1. Terminal Service Licensing does run in Automatic mode.
2. There is only one LServer folder at this server.
3. I downloaded, installed and launched LSview.exe. It found at once my
license server (that is situated at the same server as the terminal server),
it showed the green light. More over, it showed that my license server is in
the Domain mode (I was afraid that the system sees it as Enterprise).
4. Concerning User licensing mode... I tested it once more as u recommended
to me and ensured once more that it WAS set in PER USER mode already.

Concerning ur recommendation to set Terminal Server licensing server in the
manual mode, I can't understand how it can help me , but maybe I'll try
to set it such a way today.

Best regards
Vera

  Reply With Quote
Reply



Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off