Event ID: 1004 - Trm srvr cannot issue a client license. Need advise?

[Guest DougD]

Hello. I have a issue where a Windows 2000 terminal server is

displaying the Event ID: 1004 error "The terminal server cannot issue

a client license" message in the event logs. A month ago the Terminal

Server was also a backup domain controller but I had to demote it to a

standard member server. Since then the error code 1004 comes up. We are

using a new Windows 2003 domain controller that the Terminal server is

in the same domain as. The Windows 2003 domain controller does not have

terminal server licensing service running on it. Is my fix as simple as

installing the windows 2003 term server licensing? I have no plans

immediately on installing terminal services on that windows 2003 server

since I plan on keeping the windows 2000 terminal server running. Will

my existing windows 2000 terminal server cals install on the windows

2003 server if I install the terminal services licensing?

 

Thanks for any assistance.

 

Doug D

[Guest Meinolf Weber]

Re: Event ID: 1004 - Trm srvr cannot issue a client license. Need advise?

 

Hello DougD,

 

Check out this one:

http://support.microsoft.com/kb/315277

 

Or is a thin client trying to connect?

http://support.microsoft.com/kb/827355

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

> Hello. I have a issue where a Windows 2000 terminal server is

> displaying the Event ID: 1004 error "The terminal server cannot issue

> a client license" message in the event logs. A month ago the Terminal

> Server was also a backup domain controller but I had to demote it to

> a standard member server. Since then the error code 1004 comes up. We

> are using a new Windows 2003 domain controller that the Terminal

> server is in the same domain as. The Windows 2003 domain controller

> does not have terminal server licensing service running on it. Is my

> fix as simple as installing the windows 2003 term server licensing? I

> have no plans immediately on installing terminal services on that

> windows 2003 server since I plan on keeping the windows 2000 terminal

> server running. Will my existing windows 2000 terminal server cals

> install on the windows 2003 server if I install the terminal services

> licensing?

>

> Thanks for any assistance.

>

> Doug D

>

[Guest DougD]

Re: Event ID: 1004 - Trm srvr cannot issue a client license. Need advise?

 

Hello. Meinolf. Thank you for your prompt response. Since typing my

original request I installed the Terminal Server Licensing on the

Windows 2003 domain controller and

the windows 2000 terminal server can see that windows 2003 server and

the terminal server licensing on it. I was able to connect into my

terminal server via my vpn gateway where before installing the

licensing server I was unable to do this. My fear is my current Windows

2000 Terminal server cals will not install on the windows 2003 terminal

server licensing without purchasing upgraded licenses. The windows 2003

terminal server licensing is currently running in the "not activated"

state. I assume I have 60 days before I have to active this?

 

Thank you.

 

DougD

 

On 2007-09-29 13:18:23 -0400, Meinolf Weber said:

> Hello DougD,

>

> Check out this one:

> http://support.microsoft.com/kb/315277

>

> Or is a thin client trying to connect?

> http://support.microsoft.com/kb/827355

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and

> confers no rights.

>

>> Hello. I have a issue where a Windows 2000 terminal server is

>> displaying the Event ID: 1004 error "The terminal server cannot issue

>> a client license" message in the event logs. A month ago the Terminal

>> Server was also a backup domain controller but I had to demote it to

>> a standard member server. Since then the error code 1004 comes up. We

>> are using a new Windows 2003 domain controller that the Terminal

>> server is in the same domain as. The Windows 2003 domain controller

>> does not have terminal server licensing service running on it. Is my

>> fix as simple as installing the windows 2003 term server licensing? I

>> have no plans immediately on installing terminal services on that

>> windows 2003 server since I plan on keeping the windows 2000 terminal

>> server running. Will my existing windows 2000 terminal server cals

>> install on the windows 2003 server if I install the terminal services

>> licensing?

>>

>> Thanks for any assistance.

>>

>> Doug D

[Guest Meinolf Weber]

Re: Event ID: 1004 - Trm srvr cannot issue a client license. Need advise?

 

Hello DougD,

 

Check out this one about the upgrade of licenses:

http://techrepublic.com.com/5208-6230-0.html?forumID=101&threadID=208697&start=0

 

In 2003 you have 120 day's as grace period.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

> Hello. Meinolf. Thank you for your prompt response. Since typing my

> original request I installed the Terminal Server Licensing on the

> Windows 2003 domain controller and

> the windows 2000 terminal server can see that windows 2003 server and

> the terminal server licensing on it. I was able to connect into my

> terminal server via my vpn gateway where before installing the

> licensing server I was unable to do this. My fear is my current

> Windows

> 2000 Terminal server cals will not install on the windows 2003

> terminal

> server licensing without purchasing upgraded licenses. The windows

> 2003

> terminal server licensing is currently running in the "not activated"

> state. I assume I have 60 days before I have to active this?

> Thank you.

>

> DougD

>

> On 2007-09-29 13:18:23 -0400, Meinolf Weber said:

>

>> Hello DougD,

>>

>> Check out this one:

>> http://support.microsoft.com/kb/315277

>> Or is a thin client trying to connect?

>> http://support.microsoft.com/kb/827355

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers no rights.

>>> Hello. I have a issue where a Windows 2000 terminal server is

>>> displaying the Event ID: 1004 error "The terminal server cannot

>>> issue a client license" message in the event logs. A month ago the

>>> Terminal Server was also a backup domain controller but I had to

>>> demote it to a standard member server. Since then the error code

>>> 1004 comes up. We are using a new Windows 2003 domain controller

>>> that the Terminal server is in the same domain as. The Windows 2003

>>> domain controller does not have terminal server licensing service

>>> running on it. Is my fix as simple as installing the windows 2003

>>> term server licensing? I have no plans immediately on installing

>>> terminal services on that windows 2003 server since I plan on

>>> keeping the windows 2000 terminal server running. Will my existing

>>> windows 2000 terminal server cals install on the windows 2003 server

>>> if I install the terminal services licensing?

>>>

>>> Thanks for any assistance.

>>>

>>> Doug D

>>>

[Guest Vera Noest [MVP]]

Re: Event ID: 1004 - Trm srvr cannot issue a client license. Need advise?

 

The 120 day grace period of 2003 is *not* applicable in this

situation!

A grace period (which is the period in which a newly installed

Terminal Server can function without the need to contact a TS

Licensing Server) is a feature of a *terminal Server*, not of a TS

Licensing Server.

The W2K Terminal Server has long past used up its grace period.

Changing to a new TS LS on a 2003 server will *not* gibe the W2K TS

a second grace period.

 

Doug, your initial problem occurred when you demoted the W2K DC to

a member server, because a W2K TS LS must run on a Domain

Controller. If you look in the EventLog of the W2K TS, you will

find:

Event ID 29

"Terminal Services Licensing can only be run on Domain Controllers

or Server in a Workgroup." and

Event ID 7024

"The Terminal Services Licensing service terminated with service-

specific error 29."

 

Your decision to install the TS Licensing Service on the 2003

server was the right decision. Now you have to activate it as well.

 

About your licenses: you do *not* have to upgrade your W2K TS CALs!

As long as your Terminal Server runs W2K, W2K TS CALs are all you

need (+ 2003 server CALs, but you should already have those, since

you have a 2003 DC).

 

If all of your clients run W2K Pro, XP Pro or Vista Business, then

they are issued the free "Existing Windows 2000 Per Device TS

CALs", which are also present on a 2003 TS Licensing Server.

Only if you have down-level clients (XP Home Edition, thin clients,

unix, Macintosh), then you need purchased W2K TS CALs.

 

You are correct that you cannot install them on the 2003 TS

Licensing Server, because you only can install a License Pack once.

But you can simply call the Microsoft Clearinghouse and they will

re-issue your License Pack for installation on the new 2003 TS LS.

Make sure that you have the paperwork ready when you call them.

 

291795 - HOW TO: Locate a Phone Number for the Microsoft

Clearinghouse

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

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

Meinolf Weber <meiweb(nospam)@gmx.de> wrote on 29 sep 2007 in

microsoft.public.windows.terminal_services:

> Hello DougD,

>

> Check out this one about the upgrade of licenses:

> http://techrepublic.com.com/5208-6230-0.html?forumID=101&threadID

> =208697&start=0

>

> In 2003 you have 120 day's as grace period.

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties,

> and confers no rights.

>

>> Hello. Meinolf. Thank you for your prompt response. Since

>> typing my original request I installed the Terminal Server

>> Licensing on the Windows 2003 domain controller and

>> the windows 2000 terminal server can see that windows 2003

>> server and the terminal server licensing on it. I was able to

>> connect into my terminal server via my vpn gateway where before

>> installing the licensing server I was unable to do this. My

>> fear is my current Windows

>> 2000 Terminal server cals will not install on the windows 2003

>> terminal

>> server licensing without purchasing upgraded licenses. The

>> windows 2003

>> terminal server licensing is currently running in the "not

>> activated" state. I assume I have 60 days before I have to

>> active this? Thank you.

>>

>> DougD

>>

>> On 2007-09-29 13:18:23 -0400, Meinolf Weber said:

>>

>>> Hello DougD,

>>>

>>> Check out this one:

>>> http://support.microsoft.com/kb/315277

>>> Or is a thin client trying to connect?

>>> http://support.microsoft.com/kb/827355

>>> Best regards

>>>

>>> Meinolf Weber

>>> Disclaimer: This posting is provided "AS IS" with no

>>> warranties, and confers no rights.

>>>> Hello. I have a issue where a Windows 2000 terminal server is

>>>> displaying the Event ID: 1004 error "The terminal server

>>>> cannot issue a client license" message in the event logs. A

>>>> month ago the Terminal Server was also a backup domain

>>>> controller but I had to demote it to a standard member

>>>> server. Since then the error code 1004 comes up. We are using

>>>> a new Windows 2003 domain controller that the Terminal server

>>>> is in the same domain as. The Windows 2003 domain controller

>>>> does not have terminal server licensing service running on

>>>> it. Is my fix as simple as installing the windows 2003 term

>>>> server licensing? I have no plans immediately on installing

>>>> terminal services on that windows 2003 server since I plan on

>>>> keeping the windows 2000 terminal server running. Will my

>>>> existing windows 2000 terminal server cals install on the

>>>> windows 2003 server if I install the terminal services

>>>> licensing?

>>>>

>>>> Thanks for any assistance.

>>>>

>>>> Doug D