W2k3 R2 Terminalserver gets no license...

[i.edelmann@googlemail.com]

Hi there,

I have a mixed mode terminalserver farm running.
The license server for MS and CTX ist running on a W2k3 standard
server. The infrastructure is also running on W2k3 standard (farm
metric, db server) and the published desktop servers, too.
Only Some W2k published application server are in the farm.
All is running okay - there are no problems with the licenses (per
device).
I got some new servers, which are located in another subnet (the
existing subnet was full and there was no possibility to put them into
the old subnet.
All these new servers (W2k3 R2) have a strange behaviour. They all
were installed similar to the other W2k3 servers. They all have the
configuration to get their CALs from one license server only (my
dedicated license server is registered hardcoded under the following
regkey:[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
\TermService\Parameters\LicenseServers] )
With the tool lsview I can see the right license server.
A normal published application or desktop starts (with JumpinProfile
and my mandatory) in about 16 seconds completely. But on this new
servers, all sessions start in about >1 minute. In the eventlog I get
an 1004 event, which says, that the server can´t get a license from
the license server.
How can I test the connection between this server and the license
server on another way?
Another symptom of the problem is, that i got an information message
on my license servers eventlog.
Event ID 213 (Replication of license information failed because the
License Logging Service on server <PDC servername> could not be
contacted)
A week ago the company, which hosts the customer´s network
infrastructure, has upgraded the ADS from ADS 2000 to ADS 2003. All
existing dc´s (W2k) were replaced by new W2k3 servers. Could this be
my problem?
All terminalservers are in the same ou and should work correctly.

So my questions are:
- How can I test the connection from a terminalserver to the licensing
server correctly (e.g. with a logfile oder visibly)?
- Could I have a problem with the licensing server, cause the lc is in
another subnet (routing, firewall, ports?)?
- Are there known problems with the R2 version of Windows 2003?
- Could this be, that I have a problem with the new ADS, so that I
have to dejoin / join the existing farm again in the ADS (see the
event id 213 - seems to be a problem with the licensing service on a
dc)

Thanks for your help
Greetz
Ingo

 

[Vera Noest [MVP]]

Re: W2k3 R2 Terminalserver gets no license...

EventID 213 is about server CALs, not TS CALs.
This warning is harmless, and you can (and should) get rid of it by
stpping and disabling the Licensing Logging Service. This is the
default on Windows 2003 SP2.

Documented here:
824196 - Description of the License Logging Service in Windows
Server Operating Systems
http://support.microsoft.com/?kbid=824196

This is not going to solve your problem with the TS licenses, but
it helps to clarify the problem.

I'm not sure why your TS can't get a license from the LS, since it
is detectable by lsview.
Which type of TS CALs do you have on the TS Licensing Server? Did
you purchase and install 2003 Per Device licenses? And do you have
free licenses available?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

i.edelmann@googlemail.com wrote on 24 okt 2007 in
microsoft.public.windows.terminal_services:

> Hi there,
>
> I have a mixed mode terminalserver farm running.
> The license server for MS and CTX ist running on a W2k3 standard
> server. The infrastructure is also running on W2k3 standard
> (farm metric, db server) and the published desktop servers, too.
> Only Some W2k published application server are in the farm.
> All is running okay - there are no problems with the licenses
> (per device).
> I got some new servers, which are located in another subnet (the
> existing subnet was full and there was no possibility to put
> them into the old subnet.
> All these new servers (W2k3 R2) have a strange behaviour. They
> all were installed similar to the other W2k3 servers. They all
> have the configuration to get their CALs from one license server
> only (my dedicated license server is registered hardcoded under
> the following
> regkey:[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
> \TermService\Parameters\LicenseServers] ) With the tool lsview I
> can see the right license server. A normal published application
> or desktop starts (with JumpinProfile and my mandatory) in about
> 16 seconds completely. But on this new servers, all sessions
> start in about >1 minute. In the eventlog I get an 1004 event,
> which says, that the server can´t get a license from the license
> server. How can I test the connection between this server and
> the license server on another way?
> Another symptom of the problem is, that i got an information
> message on my license servers eventlog.
> Event ID 213 (Replication of license information failed because
> the License Logging Service on server <PDC servername> could not
> be contacted)
> A week ago the company, which hosts the customer´s network
> infrastructure, has upgraded the ADS from ADS 2000 to ADS 2003.
> All existing dc´s (W2k) were replaced by new W2k3 servers. Could
> this be my problem?
> All terminalservers are in the same ou and should work
> correctly.
>
> So my questions are:
> - How can I test the connection from a terminalserver to the
> licensing server correctly (e.g. with a logfile oder visibly)?
> - Could I have a problem with the licensing server, cause the lc
> is in another subnet (routing, firewall, ports?)?
> - Are there known problems with the R2 version of Windows 2003?
> - Could this be, that I have a problem with the new ADS, so that
> I have to dejoin / join the existing farm again in the ADS (see
> the event id 213 - seems to be a problem with the licensing
> service on a dc)
>
> Thanks for your help
> Greetz
> Ingo

 

[i.edelmann@googlemail.com]

Re: W2k3 R2 Terminalserver gets no license...

Hiho,
okay - event 213 is no risk for me, I understood.
I have only per device cals on the licensing server, because I use
ThinClients on Windows CE.
The strange thing is, that all the servers are in the same ou and
should get the same GPOs.
But on the "normal" servers, the terminalserver configurations are
greyed out, so I see that the server gets per device cals. On the new
servers this configuration is changeable and not greyed out. I used
the command gpoupdate /force but nothing happened. I put the
configurations hardcoded in the registry under
HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services but
nothing happened.
Is my problem a gpo problem?
Should I try to get the right gpo´s by taking out the servers out of
the ou and put them in again?

Regards and thanks

Ingo

On 24 Okt., 21:50, "Vera Noest [MVP]" <vera.no...@remove-
this.hem.utfors.se> wrote:
> EventID 213 is about server CALs, not TS CALs.
> This warning is harmless, and you can (and should) get rid of it by
> stpping and disabling the Licensing Logging Service. This is the
> default on Windows 2003 SP2.
>
> Documented here:
> 824196 - Description of the License Logging Service in Windows
> Server Operating Systemshttp://support.microsoft.com/?kbid=824196
>
> This is not going to solve your problem with the TS licenses, but
> it helps to clarify the problem.
>
> I'm not sure why your TS can't get a license from the LS, since it
> is detectable by lsview.
> Which type of TS CALs do you have on the TS Licensing Server? Did
> you purchase and install 2003 Per Device licenses? And do you have
> free licenses available?
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> i.edelm...@googlemail.com wrote on 24 okt 2007 in
> microsoft.public.windows.terminal_services:
>
>
>
> > Hi there,
>
> > I have a mixed mode terminalserver farm running.
> > The license server for MS and CTX ist running on a W2k3 standard
> > server. The infrastructure is also running on W2k3 standard
> > (farm metric, db server) and the published desktop servers, too.
> > Only Some W2k published application server are in the farm.
> > All is running okay - there are no problems with the licenses
> > (per device).
> > I got some new servers, which are located in another subnet (the
> > existing subnet was full and there was no possibility to put
> > them into the old subnet.
> > All these new servers (W2k3 R2) have a strange behaviour. They
> > all were installed similar to the other W2k3 servers. They all
> > have the configuration to get their CALs from one license server
> > only (my dedicated license server is registered hardcoded under
> > the following
> > regkey:[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
> > \TermService\Parameters\LicenseServers] ) With the tool lsview I
> > can see the right license server. A normal published application
> > or desktop starts (with JumpinProfile and my mandatory) in about
> > 16 seconds completely. But on this new servers, all sessions
> > start in about >1 minute. In the eventlog I get an 1004 event,
> > which says, that the server can´t get a license from the license
> > server. How can I test the connection between this server and
> > the license server on another way?
> > Another symptom of the problem is, that i got an information
> > message on my license servers eventlog.
> > Event ID 213 (Replication of license information failed because
> > the License Logging Service on server <PDC servername> could not
> > be contacted)
> > A week ago the company, which hosts the customer´s network
> > infrastructure, has upgraded the ADS from ADS 2000 to ADS 2003.
> > All existing dc´s (W2k) were replaced by new W2k3 servers. Could
> > this be my problem?
> > All terminalservers are in the same ou and should work
> > correctly.
>
> > So my questions are:
> > - How can I test the connection from a terminalserver to the
> > licensing server correctly (e.g. with a logfile oder visibly)?
> > - Could I have a problem with the licensing server, cause the lc
> > is in another subnet (routing, firewall, ports?)?
> > - Are there known problems with the R2 version of Windows 2003?
> > - Could this be, that I have a problem with the new ADS, so that
> > I have to dejoin / join the existing farm again in the ADS (see
> > the event id 213 - seems to be a problem with the licensing
> > service on a dc)
>
> > Thanks for your help
> > Greetz
> > Ingo- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -

 

[Vera Noest [MVP]]

Re: W2k3 R2 Terminalserver gets no license...

That sounds indeed as a problem with your GPO!
Taking the TS account out and in the OU will not change anything.
Rather, have a detailed look at the GPO. Does it use security
filtering? You need either the group "Authenticated Users" in the
security filtering list (which includes your TS), or the specific
computer account of all of your Terminal Servers, with Read and
Apply GPO rights.
Also check if the GPO uses the "License Server Security Group"
setting:

Computer Configuration - Administrative templates - Windows
Components - Terminal Services - Licensing
"License Server Security Group"

Then run Resultant Set of Policies (RSoP) to check wheter the GPO
applies to your new TS.

250842 - Troubleshooting Group Policy Application Problems
http://support.microsoft.com/?kbid=250842
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

i.edelmann@googlemail.com wrote on 25 okt 2007 in
microsoft.public.windows.terminal_services:

> Hiho,
> okay - event 213 is no risk for me, I understood.
> I have only per device cals on the licensing server, because I
> use ThinClients on Windows CE.
> The strange thing is, that all the servers are in the same ou
> and should get the same GPOs.
> But on the "normal" servers, the terminalserver configurations
> are greyed out, so I see that the server gets per device cals.
> On the new servers this configuration is changeable and not
> greyed out. I used the command gpoupdate /force but nothing
> happened. I put the configurations hardcoded in the registry
> under HKLM\Software\Policies\Microsoft\Windows NT\Terminal
> Services but nothing happened.
> Is my problem a gpo problem?
> Should I try to get the right gpo´s by taking out the servers
> out of the ou and put them in again?
>
> Regards and thanks
>
> Ingo
>
> On 24 Okt., 21:50, "Vera Noest [MVP]" <vera.no...@remove-
> this.hem.utfors.se> wrote:
>> EventID 213 is about server CALs, not TS CALs.
>> This warning is harmless, and you can (and should) get rid of
>> it by stpping and disabling the Licensing Logging Service. This
>> is the default on Windows 2003 SP2.
>>
>> Documented here:
>> 824196 - Description of the License Logging Service in Windows
>> Server Operating
>> Systemshttp://support.microsoft.com/?kbid=824196
>>
>> This is not going to solve your problem with the TS licenses,
>> but it helps to clarify the problem.
>>
>> I'm not sure why your TS can't get a license from the LS, since
>> it is detectable by lsview.
>> Which type of TS CALs do you have on the TS Licensing Server?
>> Did you purchase and install 2003 Per Device licenses? And do
>> you have free licenses available?
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> i.edelm...@googlemail.com wrote on 24 okt 2007 in
>> microsoft.public.windows.terminal_services:
>>
>>
>>
>> > Hi there,
>>
>> > I have a mixed mode terminalserver farm running.
>> > The license server for MS and CTX ist running on a W2k3
>> > standard server. The infrastructure is also running on W2k3
>> > standard (farm metric, db server) and the published desktop
>> > servers, too. Only Some W2k published application server are
>> > in the farm. All is running okay - there are no problems with
>> > the licenses (per device).
>> > I got some new servers, which are located in another subnet
>> > (the existing subnet was full and there was no possibility to
>> > put them into the old subnet.
>> > All these new servers (W2k3 R2) have a strange behaviour.
>> > They all were installed similar to the other W2k3 servers.
>> > They all have the configuration to get their CALs from one
>> > license server only (my dedicated license server is
>> > registered hardcoded under the following
>> > regkey:[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
>> > \TermService\Parameters\LicenseServers] ) With the tool
>> > lsview I can see the right license server. A normal published
>> > application or desktop starts (with JumpinProfile and my
>> > mandatory) in about 16 seconds completely. But on this new
>> > servers, all sessions start in about >1 minute. In the
>> > eventlog I get an 1004 event, which says, that the server
>> > can´t get a license from the license server. How can I test
>> > the connection between this server and the license server on
>> > another way? Another symptom of the problem is, that i got an
>> > information message on my license servers eventlog.
>> > Event ID 213 (Replication of license information failed
>> > because the License Logging Service on server <PDC
>> > servername> could not be contacted)
>> > A week ago the company, which hosts the customer´s network
>> > infrastructure, has upgraded the ADS from ADS 2000 to ADS
>> > 2003. All existing dc´s (W2k) were replaced by new W2k3
>> > servers. Could this be my problem?
>> > All terminalservers are in the same ou and should work
>> > correctly.
>>
>> > So my questions are:
>> > - How can I test the connection from a terminalserver to the
>> > licensing server correctly (e.g. with a logfile oder
>> > visibly)? - Could I have a problem with the licensing server,
>> > cause the lc is in another subnet (routing, firewall,
>> > ports?)? - Are there known problems with the R2 version of
>> > Windows 2003? - Could this be, that I have a problem with the
>> > new ADS, so that I have to dejoin / join the existing farm
>> > again in the ADS (see the event id 213 - seems to be a
>> > problem with the licensing service on a dc)
>>
>> > Thanks for your help
>> > Greetz
>> > Ingo