TS Licensing Server now not Fuctioning?

[Guest Andrew]

I have a Windows 2003 R2 box setup as our Terminal Service Licensing Server.

The server was for a long time functioning properly.

 

However recently I removed the server as a Domain Controller, it is still a

member of the domain.

 

My other W2K3 Enterprise server is now complaining that it can not find a TS

Licensing Server in the domain.

 

When I run TS Licensing "snap-in" on the server which is supposed to be the

TS Licensing server, it states it can't find a TS License Server either. If

I hit ok, and then select connect and enter the machines own name, it finds

the activated Licenses server. Close and open the "snap-in" and it throws

the error again.

 

Does the TS Licensing Server have to be a DC?

 

Any suggestions?

 

Thanks,

 

Andrew

[Guest Andrew]

Re: TS Licensing Server now not Fuctioning?

 

Look like TS License Servers have to domain controllers.

 

Andrew

 

 

"Andrew" <1800PRIVATE@NOWHERE.COM> wrote in message

news:%23FralSVyHHA.5856@TK2MSFTNGP02.phx.gbl...

>I have a Windows 2003 R2 box setup as our Terminal Service Licensing

>Server. The server was for a long time functioning properly.

>

> However recently I removed the server as a Domain Controller, it is still

> a member of the domain.

>

> My other W2K3 Enterprise server is now complaining that it can not find a

> TS Licensing Server in the domain.

>

> When I run TS Licensing "snap-in" on the server which is supposed to be

> the TS Licensing server, it states it can't find a TS License Server

> either. If I hit ok, and then select connect and enter the machines own

> name, it finds the activated Licenses server. Close and open the

> "snap-in" and it throws the error again.

>

> Does the TS Licensing Server have to be a DC?

>

> Any suggestions?

>

> Thanks,

>

> Andrew

>

[Guest Vera Noest [MVP]]

Re: TS Licensing Server now not Fuctioning?

 

No, not at all.

But a TS LS which is installed as a Domain LS is not automatically

discovered when it is running on a member server.

It was while you had the TSLS running as a Domain LS on the DC, and

would still be auto-discovered if it was an Enterprise LS on a

member server in the same site as the TS (which publishes the LS in

Active Directory).

 

This is documented here:

 

301932 - Terminal Services Licensing service discovery

http://support.microsoft.com/?kbid=301932

 

You can solve the problem by defining a preferred TSLS on your

Terminal Server. This can be done:

1) in Terminal Services Configuration - Server settings

2) in the registry

279561 - How to Override the License Server Discovery Process in

Windows Server 2003 Terminal Services

http://support.microsoft.com/?kbid=279561

3) in a Group Policy:

Computer Configuration - Administrative templates - Windows

Components - Terminal Services

"Use the specified Terminal Server license servers"

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Andrew" <1800PRIVATE@NOWHERE.COM> wrote on 18 jul 2007 in

microsoft.public.windows.terminal_services:

> Look like TS License Servers have to domain controllers.

>

> Andrew

>

>

> "Andrew" <1800PRIVATE@NOWHERE.COM> wrote in message

> news:%23FralSVyHHA.5856@TK2MSFTNGP02.phx.gbl...

>>I have a Windows 2003 R2 box setup as our Terminal Service

>>Licensing Server. The server was for a long time functioning

>>properly.

>>

>> However recently I removed the server as a Domain Controller,

>> it is still a member of the domain.

>>

>> My other W2K3 Enterprise server is now complaining that it can

>> not find a TS Licensing Server in the domain.

>>

>> When I run TS Licensing "snap-in" on the server which is

>> supposed to be the TS Licensing server, it states it can't find

>> a TS License Server either. If I hit ok, and then select

>> connect and enter the machines own name, it finds the activated

>> Licenses server. Close and open the "snap-in" and it throws

>> the error again.

>>

>> Does the TS Licensing Server have to be a DC?

>>

>> Any suggestions?

>>

>> Thanks,

>>

>> Andrew