Thin clients cannot access Terminal Server.

  • Thread starter Thread starter Rich B
  • Start date Start date
R

Rich B

Guest
Hello,

A couple of months ago I upgraded our Windows 2000 AD to Windows 2003 AD.
When I was sure everything was working (after about a month) I then demoted
the Windows 2000 AD servers to member servers. Since I am new to this
oraganization I didn't realize, and nobody told me, that one of the Windows
2000 servers had the terminal server licensing installed on it.

Because of this my thin clients are having problems logging on and I have
been getting Event ID's 1003, 1004 and 1010 on the terminal servers (As
expected, since there is no licensing server).

I since have added terminal server licensing to one of the Windows 2003 AD
servers and I was able to add the licenses through the Microsoft Clearing
house (using the automatic connection). It shows that I have licenses
available but my thin client users still cannot logon.

Did I miss something? Any help would be very much appreciated.

This is what we have:
Windows 2003 R2 SP2 AD
All terminal servers are Windows 2000 running Citrix XP FR2
Thin Clients are running Windows CE or Linux.


Thanks for any assistance.

--
Rich B
 
Re: Thin clients cannot access Terminal Server.

Did you install Per User or Per Device TS CALs?
My guess is that you have Per User TS CALs, but that your Terminal
Servers are still in the default Per Device licensing mode. If
that's the case, they won't "see" your Per User TS CALs.
Another possibility is that your TS can't locate the TS Licensing
Server (the EventLog should tell you if that's the case).

Verify your type of licenses in the TS Licensing manager, and if
needed, switch the licensing mode on each TS in terminal Services
Configuration - Server settings, or (better method) a Group Policy.
You'll find the setting here:

Computer Configuration - Administrative templates - Windows
Components - Terminal Services
"Set the Terminal Server licensing mode"

Check this article as well, it explains that even after you have
switched licensing mode on the TS, your User TS CAL "Issued" count
will not change from "N/A", because currently Per User CALs are
unmanaged:

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

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

=?Utf-8?B?UmljaCBC?= <RichB@discussions.microsoft.com> wrote on 04
dec 2007 in microsoft.public.windows.terminal_services:

> Hello,
>
> A couple of months ago I upgraded our Windows 2000 AD to Windows
> 2003 AD. When I was sure everything was working (after about a
> month) I then demoted the Windows 2000 AD servers to member
> servers. Since I am new to this oraganization I didn't realize,
> and nobody told me, that one of the Windows 2000 servers had the
> terminal server licensing installed on it.
>
> Because of this my thin clients are having problems logging on
> and I have been getting Event ID's 1003, 1004 and 1010 on the
> terminal servers (As expected, since there is no licensing
> server).
>
> I since have added terminal server licensing to one of the
> Windows 2003 AD servers and I was able to add the licenses
> through the Microsoft Clearing house (using the automatic
> connection). It shows that I have licenses available but my thin
> client users still cannot logon.
>
> Did I miss something? Any help would be very much appreciated.
>
> This is what we have:
> Windows 2003 R2 SP2 AD
> All terminal servers are Windows 2000 running Citrix XP FR2
> Thin Clients are running Windows CE or Linux.
>
>
> Thanks for any assistance.
 
Re: Thin clients cannot access Terminal Server.

Vera,

Thank you for your quick response. I really don't think that the problem is
with the terminal servers. Prior to the demotion of the original licensing
server everything was working properly. So the licensing mode should be set
for per user.

I also have checked the event viewers on the four terminal servers we have
and until I installed the new license server they could not locate any server
(event id 1010). After I installed it they are showing that they cannot issue
a client license (event id 1004) or the client has provided an invalid
license (event id 1003). This is only happening with some of my thin clients
at the moment. I am very concerned that the other thin clients that are
working now will start to have the same problem.

I read the article you refered me to and if I understand it correctly the TS
licensing server does not manage CALs??? Then why is this problem happening?

Is this something that I should call MS support about?


--Rich B


"Vera Noest [MVP]" wrote:

> Did you install Per User or Per Device TS CALs?
> My guess is that you have Per User TS CALs, but that your Terminal
> Servers are still in the default Per Device licensing mode. If
> that's the case, they won't "see" your Per User TS CALs.
> Another possibility is that your TS can't locate the TS Licensing
> Server (the EventLog should tell you if that's the case).
>
> Verify your type of licenses in the TS Licensing manager, and if
> needed, switch the licensing mode on each TS in terminal Services
> Configuration - Server settings, or (better method) a Group Policy.
> You'll find the setting here:
>
> Computer Configuration - Administrative templates - Windows
> Components - Terminal Services
> "Set the Terminal Server licensing mode"
>
> Check this article as well, it explains that even after you have
> switched licensing mode on the TS, your User TS CAL "Issued" count
> will not change from "N/A", because currently Per User CALs are
> unmanaged:
>
> 822134 - The Function of Terminal Server CALs in Windows Server
> 2003
> http://support.microsoft.com/?kbid=822134
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?UmljaCBC?= <RichB@discussions.microsoft.com> wrote on 04
> dec 2007 in microsoft.public.windows.terminal_services:
>
> > Hello,
> >
> > A couple of months ago I upgraded our Windows 2000 AD to Windows
> > 2003 AD. When I was sure everything was working (after about a
> > month) I then demoted the Windows 2000 AD servers to member
> > servers. Since I am new to this oraganization I didn't realize,
> > and nobody told me, that one of the Windows 2000 servers had the
> > terminal server licensing installed on it.
> >
> > Because of this my thin clients are having problems logging on
> > and I have been getting Event ID's 1003, 1004 and 1010 on the
> > terminal servers (As expected, since there is no licensing
> > server).
> >
> > I since have added terminal server licensing to one of the
> > Windows 2003 AD servers and I was able to add the licenses
> > through the Microsoft Clearing house (using the automatic
> > connection). It shows that I have licenses available but my thin
> > client users still cannot logon.
> >
> > Did I miss something? Any help would be very much appreciated.
> >
> > This is what we have:
> > Windows 2003 R2 SP2 AD
> > All terminal servers are Windows 2000 running Citrix XP FR2
> > Thin Clients are running Windows CE or Linux.
> >
> >
> > Thanks for any assistance.
>
 
Re: Thin clients cannot access Terminal Server.

Sorry, my mistake, I didn't read your post carefully enough and
thought that you also upgraded your Terminal Servers to 2003.

But since they are still running on W2K, the licensing mode of the
Terminal Servers is *not* the problem, since a W2K TS only has one
licensing mode, which is Per Device.
You should still check that your TS CALs, which you installed on
the TS Licensing Server, are Per Device TS CALs.

If the Clearinghouse issued you Per User licenses, you must phone
them again and change them into Per Device licenses, since a W2K TS
doesn't know what Per User licenses are.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?UmljaCBC?= <RichB@discussions.microsoft.com> wrote on 05
dec 2007 in microsoft.public.windows.terminal_services:

> Vera,
>
> Thank you for your quick response. I really don't think that the
> problem is with the terminal servers. Prior to the demotion of
> the original licensing server everything was working properly.
> So the licensing mode should be set for per user.
>
> I also have checked the event viewers on the four terminal
> servers we have and until I installed the new license server
> they could not locate any server (event id 1010). After I
> installed it they are showing that they cannot issue a client
> license (event id 1004) or the client has provided an invalid
> license (event id 1003). This is only happening with some of my
> thin clients at the moment. I am very concerned that the other
> thin clients that are working now will start to have the same
> problem.
>
> I read the article you refered me to and if I understand it
> correctly the TS licensing server does not manage CALs??? Then
> why is this problem happening?
>
> Is this something that I should call MS support about?
>
>
> --Rich B
>
>
> "Vera Noest [MVP]" wrote:
>
>> Did you install Per User or Per Device TS CALs?
>> My guess is that you have Per User TS CALs, but that your
>> Terminal Servers are still in the default Per Device licensing
>> mode. If that's the case, they won't "see" your Per User TS
>> CALs. Another possibility is that your TS can't locate the TS
>> Licensing Server (the EventLog should tell you if that's the
>> case).
>>
>> Verify your type of licenses in the TS Licensing manager, and
>> if needed, switch the licensing mode on each TS in terminal
>> Services Configuration - Server settings, or (better method) a
>> Group Policy. You'll find the setting here:
>>
>> Computer Configuration - Administrative templates - Windows
>> Components - Terminal Services
>> "Set the Terminal Server licensing mode"
>>
>> Check this article as well, it explains that even after you
>> have switched licensing mode on the TS, your User TS CAL
>> "Issued" count will not change from "N/A", because currently
>> Per User CALs are unmanaged:
>>
>> 822134 - The Function of Terminal Server CALs in Windows Server
>> 2003
>> http://support.microsoft.com/?kbid=822134
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?UmljaCBC?= <RichB@discussions.microsoft.com> wrote on
>> 04 dec 2007 in microsoft.public.windows.terminal_services:
>>
>> > Hello,
>> >
>> > A couple of months ago I upgraded our Windows 2000 AD to
>> > Windows 2003 AD. When I was sure everything was working
>> > (after about a month) I then demoted the Windows 2000 AD
>> > servers to member servers. Since I am new to this
>> > oraganization I didn't realize, and nobody told me, that one
>> > of the Windows 2000 servers had the terminal server licensing
>> > installed on it.
>> >
>> > Because of this my thin clients are having problems logging
>> > on and I have been getting Event ID's 1003, 1004 and 1010 on
>> > the terminal servers (As expected, since there is no
>> > licensing server).
>> >
>> > I since have added terminal server licensing to one of the
>> > Windows 2003 AD servers and I was able to add the licenses
>> > through the Microsoft Clearing house (using the automatic
>> > connection). It shows that I have licenses available but my
>> > thin client users still cannot logon.
>> >
>> > Did I miss something? Any help would be very much
>> > appreciated.
>> >
>> > This is what we have:
>> > Windows 2003 R2 SP2 AD
>> > All terminal servers are Windows 2000 running Citrix XP FR2
>> > Thin Clients are running Windows CE or Linux.
>> >
>> >
>> > Thanks for any assistance.
 
Re: Thin clients cannot access Terminal Server.

Vera,

Thank you for your help. I found that a key in the registry of my terminal
servers was still pointing to the old license server. Once I changed the key
to the new server all the thin clients that were having problems are now
working.

Registry Key HKLM\system\currentcontrolset\services\termservice\parameters.

Thank You
--
Rich B


"Vera Noest [MVP]" wrote:

> Sorry, my mistake, I didn't read your post carefully enough and
> thought that you also upgraded your Terminal Servers to 2003.
>
> But since they are still running on W2K, the licensing mode of the
> Terminal Servers is *not* the problem, since a W2K TS only has one
> licensing mode, which is Per Device.
> You should still check that your TS CALs, which you installed on
> the TS Licensing Server, are Per Device TS CALs.
>
> If the Clearinghouse issued you Per User licenses, you must phone
> them again and change them into Per Device licenses, since a W2K TS
> doesn't know what Per User licenses are.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?UmljaCBC?= <RichB@discussions.microsoft.com> wrote on 05
> dec 2007 in microsoft.public.windows.terminal_services:
>
> > Vera,
> >
> > Thank you for your quick response. I really don't think that the
> > problem is with the terminal servers. Prior to the demotion of
> > the original licensing server everything was working properly.
> > So the licensing mode should be set for per user.
> >
> > I also have checked the event viewers on the four terminal
> > servers we have and until I installed the new license server
> > they could not locate any server (event id 1010). After I
> > installed it they are showing that they cannot issue a client
> > license (event id 1004) or the client has provided an invalid
> > license (event id 1003). This is only happening with some of my
> > thin clients at the moment. I am very concerned that the other
> > thin clients that are working now will start to have the same
> > problem.
> >
> > I read the article you refered me to and if I understand it
> > correctly the TS licensing server does not manage CALs??? Then
> > why is this problem happening?
> >
> > Is this something that I should call MS support about?
> >
> >
> > --Rich B
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Did you install Per User or Per Device TS CALs?
> >> My guess is that you have Per User TS CALs, but that your
> >> Terminal Servers are still in the default Per Device licensing
> >> mode. If that's the case, they won't "see" your Per User TS
> >> CALs. Another possibility is that your TS can't locate the TS
> >> Licensing Server (the EventLog should tell you if that's the
> >> case).
> >>
> >> Verify your type of licenses in the TS Licensing manager, and
> >> if needed, switch the licensing mode on each TS in terminal
> >> Services Configuration - Server settings, or (better method) a
> >> Group Policy. You'll find the setting here:
> >>
> >> Computer Configuration - Administrative templates - Windows
> >> Components - Terminal Services
> >> "Set the Terminal Server licensing mode"
> >>
> >> Check this article as well, it explains that even after you
> >> have switched licensing mode on the TS, your User TS CAL
> >> "Issued" count will not change from "N/A", because currently
> >> Per User CALs are unmanaged:
> >>
> >> 822134 - The Function of Terminal Server CALs in Windows Server
> >> 2003
> >> http://support.microsoft.com/?kbid=822134
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?UmljaCBC?= <RichB@discussions.microsoft.com> wrote on
> >> 04 dec 2007 in microsoft.public.windows.terminal_services:
> >>
> >> > Hello,
> >> >
> >> > A couple of months ago I upgraded our Windows 2000 AD to
> >> > Windows 2003 AD. When I was sure everything was working
> >> > (after about a month) I then demoted the Windows 2000 AD
> >> > servers to member servers. Since I am new to this
> >> > oraganization I didn't realize, and nobody told me, that one
> >> > of the Windows 2000 servers had the terminal server licensing
> >> > installed on it.
> >> >
> >> > Because of this my thin clients are having problems logging
> >> > on and I have been getting Event ID's 1003, 1004 and 1010 on
> >> > the terminal servers (As expected, since there is no
> >> > licensing server).
> >> >
> >> > I since have added terminal server licensing to one of the
> >> > Windows 2003 AD servers and I was able to add the licenses
> >> > through the Microsoft Clearing house (using the automatic
> >> > connection). It shows that I have licenses available but my
> >> > thin client users still cannot logon.
> >> >
> >> > Did I miss something? Any help would be very much
> >> > appreciated.
> >> >
> >> > This is what we have:
> >> > Windows 2003 R2 SP2 AD
> >> > All terminal servers are Windows 2000 running Citrix XP FR2
> >> > Thin Clients are running Windows CE or Linux.
> >> >
> >> >
> >> > Thanks for any assistance.
>
 
Re: Thin clients cannot access Terminal Server.

OK, I'm glad that you have solved the problem, and thanks for the
feedback!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?UmljaCBC?= <RichB@discussions.microsoft.com> wrote on 05
dec 2007 in microsoft.public.windows.terminal_services:

> Vera,
>
> Thank you for your help. I found that a key in the registry of
> my terminal servers was still pointing to the old license
> server. Once I changed the key to the new server all the thin
> clients that were having problems are now working.
>
> Registry Key
> HKLM\system\currentcontrolset\services\termservice\parameters.
>
> Thank You
 
Back
Top