Terminal Server Events 1004 & 4105

[Guest Saucer Man]

I am getting this Informational event logged on my terminal server (server

2008) whenever someone connects to it from within our domain.

 

1004 - "The terminal server cannot issue a client license. It was unable to

issue the license due to a changed (mismatched) client license, insufficient

memory, or an internal error. Further details for this problem may have been

reported at the client's computer."

 

We have 5 per user TS Cals installed. A Microsoft rep stated that per user

Cals cannot be tracked and that this message is normal. I felt perhaps he

was a little unsure about this as my call to them was actually on another

issue. Does anyone know if this is true and normal?

 

 

Additionally, I am getting this Warning event when someone connects from the

Internet to it.

 

4105 - "The Terminal Services license server cannot update the license

attributes for user "bob" in the Active Directory Domain "domain.local".

Ensure that the computer account for the license server is a member of

Terminal Server License Servers group in Active Directory domain

"domain.local".If the license server is installed on a domain controller,

the Network Service account also needs to be a member of the Terminal Server

License Servers group.If the license server is installed on a domain

controller, after you have added the appropriate accounts to the Terminal

Server License Servers group, you must restart the Terminal Services

Licensing service to track or report the usage of TS Per User CALs.Win32

error code: 0x80070005"

 

The computer account is a member of Terminal Server License Servers. Any

ideas?

 

--

Thanks!

[Guest Vera Noest [MVP]]

Re: Terminal Server Events 1004 & 4105

 

No, this is not as it should be.

The MS rep. was wrong on all accounts, TS User CALs *are* issued,

and they can be tracked, the only difference with Per Device TS

CALs is that they are not enforced.

 

The problem seems to be that the LS doesn't have enough privileges

in the domain to update the user account in AD.

Is you LS running on a DC? If not, which OS is your DC running?

Have you run the LS diagnostics tool?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Saucer Man" <saucerman@nospam.com> wrote on 08 sep 2008 in

microsoft.public.windows.terminal_services:

> I am getting this Informational event logged on my terminal

> server (server 2008) whenever someone connects to it from within

> our domain.

>

> 1004 - "The terminal server cannot issue a client license. It

> was unable to issue the license due to a changed (mismatched)

> client license, insufficient memory, or an internal error.

> Further details for this problem may have been reported at the

> client's computer."

>

> We have 5 per user TS Cals installed. A Microsoft rep stated

> that per user Cals cannot be tracked and that this message is

> normal. I felt perhaps he was a little unsure about this as my

> call to them was actually on another issue. Does anyone know if

> this is true and normal?

>

>

> Additionally, I am getting this Warning event when someone

> connects from the Internet to it.

>

> 4105 - "The Terminal Services license server cannot update the

> license attributes for user "bob" in the Active Directory Domain

> "domain.local". Ensure that the computer account for the license

> server is a member of Terminal Server License Servers group in

> Active Directory domain "domain.local".If the license server is

> installed on a domain controller, the Network Service account

> also needs to be a member of the Terminal Server License Servers

> group.If the license server is installed on a domain controller,

> after you have added the appropriate accounts to the Terminal

> Server License Servers group, you must restart the Terminal

> Services Licensing service to track or report the usage of TS

> Per User CALs.Win32 error code: 0x80070005"

>

> The computer account is a member of Terminal Server License

> Servers. Any ideas?

[Guest Saucer Man]

Re: Terminal Server Events 1004 & 4105

 

Hi Vera.

 

The LS is running on our TS, not a DC. The TS is Server 2008 and our DCs

are 2003. The LS Diagnostics come back with "Licensing Diagnosis did not

identify any problems to report." Do you think that this can be a

non-charge incident with Microsoft?

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns9B13A7A93CE29veranoesthemutforsse@207.46.248.16...

> No, this is not as it should be.

> The MS rep. was wrong on all accounts, TS User CALs *are* issued,

> and they can be tracked, the only difference with Per Device TS

> CALs is that they are not enforced.

>

> The problem seems to be that the LS doesn't have enough privileges

> in the domain to update the user account in AD.

> Is you LS running on a DC? If not, which OS is your DC running?

> Have you run the LS diagnostics tool?

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> "Saucer Man" <saucerman@nospam.com> wrote on 08 sep 2008 in

> microsoft.public.windows.terminal_services:

>

>> I am getting this Informational event logged on my terminal

>> server (server 2008) whenever someone connects to it from within

>> our domain.

>>

>> 1004 - "The terminal server cannot issue a client license. It

>> was unable to issue the license due to a changed (mismatched)

>> client license, insufficient memory, or an internal error.

>> Further details for this problem may have been reported at the

>> client's computer."

>>

>> We have 5 per user TS Cals installed. A Microsoft rep stated

>> that per user Cals cannot be tracked and that this message is

>> normal. I felt perhaps he was a little unsure about this as my

>> call to them was actually on another issue. Does anyone know if

>> this is true and normal?

>>

>>

>> Additionally, I am getting this Warning event when someone

>> connects from the Internet to it.

>>

>> 4105 - "The Terminal Services license server cannot update the

>> license attributes for user "bob" in the Active Directory Domain

>> "domain.local". Ensure that the computer account for the license

>> server is a member of Terminal Server License Servers group in

>> Active Directory domain "domain.local".If the license server is

>> installed on a domain controller, the Network Service account

>> also needs to be a member of the Terminal Server License Servers

>> group.If the license server is installed on a domain controller,

>> after you have added the appropriate accounts to the Terminal

>> Server License Servers group, you must restart the Terminal

>> Services Licensing service to track or report the usage of TS

>> Per User CALs.Win32 error code: 0x80070005"

>>

>> The computer account is a member of Terminal Server License

>> Servers. Any ideas?

>

[Guest Vera Noest [MVP]]

Re: Terminal Server Events 1004 & 4105

 

That's difficult to say, depends on the cause. If it turns out to

be a wrong configuration, you pay. Otherwise, not.

Have you checked the EventLog on the DC? Maybe the security log

there tells you which account is denied?

Did you install the LS when logged on with at least a Domain Admin

account, preferably a Enterprise Admin account?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Saucer Man" <saucerman@nospam.com> wrote on 08 sep 2008 in

microsoft.public.windows.terminal_services:

> Hi Vera.

>

> The LS is running on our TS, not a DC. The TS is Server 2008

> and our DCs are 2003. The LS Diagnostics come back with

> "Licensing Diagnosis did not identify any problems to report."

> Do you think that this can be a non-charge incident with

> Microsoft?

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns9B13A7A93CE29veranoesthemutforsse@207.46.248.16...

>> No, this is not as it should be.

>> The MS rep. was wrong on all accounts, TS User CALs *are*

>> issued, and they can be tracked, the only difference with Per

>> Device TS CALs is that they are not enforced.

>>

>> The problem seems to be that the LS doesn't have enough

>> privileges in the domain to update the user account in AD.

>> Is you LS running on a DC? If not, which OS is your DC running?

>> Have you run the LS diagnostics tool?

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "Saucer Man" <saucerman@nospam.com> wrote on 08 sep 2008 in

>> microsoft.public.windows.terminal_services:

>>

>>> I am getting this Informational event logged on my terminal

>>> server (server 2008) whenever someone connects to it from

>>> within our domain.

>>>

>>> 1004 - "The terminal server cannot issue a client license. It

>>> was unable to issue the license due to a changed (mismatched)

>>> client license, insufficient memory, or an internal error.

>>> Further details for this problem may have been reported at the

>>> client's computer."

>>>

>>> We have 5 per user TS Cals installed. A Microsoft rep stated

>>> that per user Cals cannot be tracked and that this message is

>>> normal. I felt perhaps he was a little unsure about this as

>>> my call to them was actually on another issue. Does anyone

>>> know if this is true and normal?

>>>

>>>

>>> Additionally, I am getting this Warning event when someone

>>> connects from the Internet to it.

>>>

>>> 4105 - "The Terminal Services license server cannot update the

>>> license attributes for user "bob" in the Active Directory

>>> Domain "domain.local". Ensure that the computer account for

>>> the license server is a member of Terminal Server License

>>> Servers group in Active Directory domain "domain.local".If the

>>> license server is installed on a domain controller, the

>>> Network Service account also needs to be a member of the

>>> Terminal Server License Servers group.If the license server is

>>> installed on a domain controller, after you have added the

>>> appropriate accounts to the Terminal Server License Servers

>>> group, you must restart the Terminal Services Licensing

>>> service to track or report the usage of TS Per User CALs.Win32

>>> error code: 0x80070005"

>>>

>>> The computer account is a member of Terminal Server License

>>> Servers. Any ideas?

[Guest Saucer Man]

Re: Terminal Server Events 1004 & 4105

 

The DC's event log shows everything about the logon to the TS as Suggess A.

I don't see any hint there. I did install the LS with an Enterprise Admin

account.

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns9B13E745C7F19veranoesthemutforsse@207.46.248.16...

> That's difficult to say, depends on the cause. If it turns out to

> be a wrong configuration, you pay. Otherwise, not.

> Have you checked the EventLog on the DC? Maybe the security log

> there tells you which account is denied?

> Did you install the LS when logged on with at least a Domain Admin

> account, preferably a Enterprise Admin account?

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> "Saucer Man" <saucerman@nospam.com> wrote on 08 sep 2008 in

> microsoft.public.windows.terminal_services:

>

>> Hi Vera.

>>

>> The LS is running on our TS, not a DC. The TS is Server 2008

>> and our DCs are 2003. The LS Diagnostics come back with

>> "Licensing Diagnosis did not identify any problems to report."

>> Do you think that this can be a non-charge incident with

>> Microsoft?

>>

>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

>> in message

>> news:Xns9B13A7A93CE29veranoesthemutforsse@207.46.248.16...

>>> No, this is not as it should be.

>>> The MS rep. was wrong on all accounts, TS User CALs *are*

>>> issued, and they can be tracked, the only difference with Per

>>> Device TS CALs is that they are not enforced.

>>>

>>> The problem seems to be that the LS doesn't have enough

>>> privileges in the domain to update the user account in AD.

>>> Is you LS running on a DC? If not, which OS is your DC running?

>>> Have you run the LS diagnostics tool?

>>>

>>> _________________________________________________________

>>> Vera Noest

>>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>>> ___ please respond in newsgroup, NOT by private email ___

>>>

>>> "Saucer Man" <saucerman@nospam.com> wrote on 08 sep 2008 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> I am getting this Informational event logged on my terminal

>>>> server (server 2008) whenever someone connects to it from

>>>> within our domain.

>>>>

>>>> 1004 - "The terminal server cannot issue a client license. It

>>>> was unable to issue the license due to a changed (mismatched)

>>>> client license, insufficient memory, or an internal error.

>>>> Further details for this problem may have been reported at the

>>>> client's computer."

>>>>

>>>> We have 5 per user TS Cals installed. A Microsoft rep stated

>>>> that per user Cals cannot be tracked and that this message is

>>>> normal. I felt perhaps he was a little unsure about this as

>>>> my call to them was actually on another issue. Does anyone

>>>> know if this is true and normal?

>>>>

>>>>

>>>> Additionally, I am getting this Warning event when someone

>>>> connects from the Internet to it.

>>>>

>>>> 4105 - "The Terminal Services license server cannot update the

>>>> license attributes for user "bob" in the Active Directory

>>>> Domain "domain.local". Ensure that the computer account for

>>>> the license server is a member of Terminal Server License

>>>> Servers group in Active Directory domain "domain.local".If the

>>>> license server is installed on a domain controller, the

>>>> Network Service account also needs to be a member of the

>>>> Terminal Server License Servers group.If the license server is

>>>> installed on a domain controller, after you have added the

>>>> appropriate accounts to the Terminal Server License Servers

>>>> group, you must restart the Terminal Services Licensing

>>>> service to track or report the usage of TS Per User CALs.Win32

>>>> error code: 0x80070005"

>>>>

>>>> The computer account is a member of Terminal Server License

>>>> Servers. Any ideas?

[Guest Saucer Man]

Re: Terminal Server Events 1004 & 4105

 

Vera, have you got TS user cals to be issued with Windows server 2008? I

have another Microsoft rep on the line right no who is telling me that user

cals will not be issued and cannot be tracked. He will be sending me a KB

article.

 

 

"Saucer Man" <saucerman@nospam.com> wrote in message

news:48c6792b$0$31967$cc2e38e6@news.uslec.net...

> The DC's event log shows everything about the logon to the TS as Suggess

> A. I don't see any hint there. I did install the LS with an Enterprise

> Admin account.

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

> news:Xns9B13E745C7F19veranoesthemutforsse@207.46.248.16...

>> That's difficult to say, depends on the cause. If it turns out to

>> be a wrong configuration, you pay. Otherwise, not.

>> Have you checked the EventLog on the DC? Maybe the security log

>> there tells you which account is denied?

>> Did you install the LS when logged on with at least a Domain Admin

>> account, preferably a Enterprise Admin account?

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "Saucer Man" <saucerman@nospam.com> wrote on 08 sep 2008 in

>> microsoft.public.windows.terminal_services:

>>

>>> Hi Vera.

>>>

>>> The LS is running on our TS, not a DC. The TS is Server 2008

>>> and our DCs are 2003. The LS Diagnostics come back with

>>> "Licensing Diagnosis did not identify any problems to report."

>>> Do you think that this can be a non-charge incident with

>>> Microsoft?

>>>

>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

>>> in message

>>> news:Xns9B13A7A93CE29veranoesthemutforsse@207.46.248.16...

>>>> No, this is not as it should be.

>>>> The MS rep. was wrong on all accounts, TS User CALs *are*

>>>> issued, and they can be tracked, the only difference with Per

>>>> Device TS CALs is that they are not enforced.

>>>>

>>>> The problem seems to be that the LS doesn't have enough

>>>> privileges in the domain to update the user account in AD.

>>>> Is you LS running on a DC? If not, which OS is your DC running?

>>>> Have you run the LS diagnostics tool?

>>>>

>>>> _________________________________________________________

>>>> Vera Noest

>>>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>

>>>> "Saucer Man" <saucerman@nospam.com> wrote on 08 sep 2008 in

>>>> microsoft.public.windows.terminal_services:

>>>>

>>>>> I am getting this Informational event logged on my terminal

>>>>> server (server 2008) whenever someone connects to it from

>>>>> within our domain.

>>>>>

>>>>> 1004 - "The terminal server cannot issue a client license. It

>>>>> was unable to issue the license due to a changed (mismatched)

>>>>> client license, insufficient memory, or an internal error.

>>>>> Further details for this problem may have been reported at the

>>>>> client's computer."

>>>>>

>>>>> We have 5 per user TS Cals installed. A Microsoft rep stated

>>>>> that per user Cals cannot be tracked and that this message is

>>>>> normal. I felt perhaps he was a little unsure about this as

>>>>> my call to them was actually on another issue. Does anyone

>>>>> know if this is true and normal?

>>>>>

>>>>>

>>>>> Additionally, I am getting this Warning event when someone

>>>>> connects from the Internet to it.

>>>>>

>>>>> 4105 - "The Terminal Services license server cannot update the

>>>>> license attributes for user "bob" in the Active Directory

>>>>> Domain "domain.local". Ensure that the computer account for

>>>>> the license server is a member of Terminal Server License

>>>>> Servers group in Active Directory domain "domain.local".If the

>>>>> license server is installed on a domain controller, the

>>>>> Network Service account also needs to be a member of the

>>>>> Terminal Server License Servers group.If the license server is

>>>>> installed on a domain controller, after you have added the

>>>>> appropriate accounts to the Terminal Server License Servers

>>>>> group, you must restart the Terminal Services Licensing

>>>>> service to track or report the usage of TS Per User CALs.Win32

>>>>> error code: 0x80070005"

>>>>>

>>>>> The computer account is a member of Terminal Server License

>>>>> Servers. Any ideas?

>

>

>

[Guest Saucer Man]

Re: Terminal Server Events 1004 & 4105

 

Well, Microsoft fixed the events with an internal hotfix, kb957068. They

are currently looking into why the user cals are not being issued.

 

"Saucer Man" <saucerman@nospam.com> wrote in message

news:48ca732c$0$31957$cc2e38e6@news.uslec.net...

> Vera, have you got TS user cals to be issued with Windows server 2008? I

> have another Microsoft rep on the line right no who is telling me that

> user cals will not be issued and cannot be tracked. He will be sending me

> a KB article.

>

>

> "Saucer Man" <saucerman@nospam.com> wrote in message

> news:48c6792b$0$31967$cc2e38e6@news.uslec.net...

>> The DC's event log shows everything about the logon to the TS as Suggess

>> A. I don't see any hint there. I did install the LS with an Enterprise

>> Admin account.

>>

>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in

>> message news:Xns9B13E745C7F19veranoesthemutforsse@207.46.248.16...

>>> That's difficult to say, depends on the cause. If it turns out to

>>> be a wrong configuration, you pay. Otherwise, not.

>>> Have you checked the EventLog on the DC? Maybe the security log

>>> there tells you which account is denied?

>>> Did you install the LS when logged on with at least a Domain Admin

>>> account, preferably a Enterprise Admin account?

>>>

>>> _________________________________________________________

>>> Vera Noest

>>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>>> ___ please respond in newsgroup, NOT by private email ___

>>>

>>> "Saucer Man" <saucerman@nospam.com> wrote on 08 sep 2008 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> Hi Vera.

>>>>

>>>> The LS is running on our TS, not a DC. The TS is Server 2008

>>>> and our DCs are 2003. The LS Diagnostics come back with

>>>> "Licensing Diagnosis did not identify any problems to report."

>>>> Do you think that this can be a non-charge incident with

>>>> Microsoft?

>>>>

>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

>>>> in message

>>>> news:Xns9B13A7A93CE29veranoesthemutforsse@207.46.248.16...

>>>>> No, this is not as it should be.

>>>>> The MS rep. was wrong on all accounts, TS User CALs *are*

>>>>> issued, and they can be tracked, the only difference with Per

>>>>> Device TS CALs is that they are not enforced.

>>>>>

>>>>> The problem seems to be that the LS doesn't have enough

>>>>> privileges in the domain to update the user account in AD.

>>>>> Is you LS running on a DC? If not, which OS is your DC running?

>>>>> Have you run the LS diagnostics tool?

>>>>>

>>>>> _________________________________________________________

>>>>> Vera Noest

>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>>

>>>>> "Saucer Man" <saucerman@nospam.com> wrote on 08 sep 2008 in

>>>>> microsoft.public.windows.terminal_services:

>>>>>

>>>>>> I am getting this Informational event logged on my terminal

>>>>>> server (server 2008) whenever someone connects to it from

>>>>>> within our domain.

>>>>>>

>>>>>> 1004 - "The terminal server cannot issue a client license. It

>>>>>> was unable to issue the license due to a changed (mismatched)

>>>>>> client license, insufficient memory, or an internal error.

>>>>>> Further details for this problem may have been reported at the

>>>>>> client's computer."

>>>>>>

>>>>>> We have 5 per user TS Cals installed. A Microsoft rep stated

>>>>>> that per user Cals cannot be tracked and that this message is

>>>>>> normal. I felt perhaps he was a little unsure about this as

>>>>>> my call to them was actually on another issue. Does anyone

>>>>>> know if this is true and normal?

>>>>>>

>>>>>>

>>>>>> Additionally, I am getting this Warning event when someone

>>>>>> connects from the Internet to it.

>>>>>>

>>>>>> 4105 - "The Terminal Services license server cannot update the

>>>>>> license attributes for user "bob" in the Active Directory

>>>>>> Domain "domain.local". Ensure that the computer account for

>>>>>> the license server is a member of Terminal Server License

>>>>>> Servers group in Active Directory domain "domain.local".If the

>>>>>> license server is installed on a domain controller, the

>>>>>> Network Service account also needs to be a member of the

>>>>>> Terminal Server License Servers group.If the license server is

>>>>>> installed on a domain controller, after you have added the

>>>>>> appropriate accounts to the Terminal Server License Servers

>>>>>> group, you must restart the Terminal Services Licensing

>>>>>> service to track or report the usage of TS Per User CALs.Win32

>>>>>> error code: 0x80070005"

>>>>>>

>>>>>> The computer account is a member of Terminal Server License

>>>>>> Servers. Any ideas?

>>

>>

>>

>

>

>