Cannot Remote Control Users

  • Thread starter Thread starter Lance
  • Start date Start date
L

Lance

Guest
I have a 2k3 Terminal server that has been set up and running for
approximately 2 years, which as been updated to SP1, SP2 and RC2, with all
current Updates.

I need to replace this server so I am setting up a new Terminal Server. I
set up the new server using RC2, installed SP2 and did all the windows
updates. Set up all the Licensing and Terminal Services configurations the
EXACT SAME as the original Terminal Server that has been running for about 2
years just fine.

Now the problem. Users can log on with no problems. But when I try to
remote control the users using Terminal Server Manager, the exact same as I
do with the 2 year old Terminal Server, I receive "Error 7054 - The system
has reached its licensed logon limit" I have searched, and looked and
searched some more for an answer for this and am only able to find one other
thread with the same problem which I can find now, but I have tried
everything in that thread to no avail. On top of that, this is the second
time I have tried to install and configure this server. I tried a couple
months ago and gave up because of this problem, now I am in the exact same
situation.

Can anyone provide even a hint of help or direction on this.

Thanks
 
Re: Cannot Remote Control Users

This message usually has to do with server CALs, not TS CALs.
There should be an Event in the EventLog which gives (slightly)
more details about which product is out of its licensed limit, i.e.
the Windows 2003 OS.

Make sure that you have the proper amount of server CALs to be
compliant with the EULA, and then stop and disable the Licensing
Logging Service. Documented here:

824196 - Description of the License Logging Service in Windows
Server Operating Systems
http://support.microsoft.com/?kbid=824196
_________________________________________________________
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?TGFuY2U=?= <Lance@discussions.microsoft.com> wrote on 21
nov 2007 in microsoft.public.windows.terminal_services:

> I have a 2k3 Terminal server that has been set up and running
> for approximately 2 years, which as been updated to SP1, SP2 and
> RC2, with all current Updates.
>
> I need to replace this server so I am setting up a new Terminal
> Server. I set up the new server using RC2, installed SP2 and
> did all the windows updates. Set up all the Licensing and
> Terminal Services configurations the EXACT SAME as the original
> Terminal Server that has been running for about 2 years just
> fine.
>
> Now the problem. Users can log on with no problems. But when I
> try to remote control the users using Terminal Server Manager,
> the exact same as I do with the 2 year old Terminal Server, I
> receive "Error 7054 - The system has reached its licensed logon
> limit" I have searched, and looked and searched some more for
> an answer for this and am only able to find one other thread
> with the same problem which I can find now, but I have tried
> everything in that thread to no avail. On top of that, this is
> the second time I have tried to install and configure this
> server. I tried a couple months ago and gave up because of this
> problem, now I am in the exact same situation.
>
> Can anyone provide even a hint of help or direction on this.
>
> Thanks
 
Re: Cannot Remote Control Users

I am assuming this is the Licensing icon under Administrative Tools. I have
enabled the license Logging Service which allowed me to open this. If this
is the case, it opens the licensing on the Domain Controller which is the
same exact thing that happens on the 2 year old Terminal Server. There are
more than enough CAL's in there.

Let me know if there is something else I need to check.

"Vera Noest [MVP]" wrote:

> This message usually has to do with server CALs, not TS CALs.
> There should be an Event in the EventLog which gives (slightly)
> more details about which product is out of its licensed limit, i.e.
> the Windows 2003 OS.
>
> Make sure that you have the proper amount of server CALs to be
> compliant with the EULA, and then stop and disable the Licensing
> Logging Service. Documented here:
>
> 824196 - Description of the License Logging Service in Windows
> Server Operating Systems
> http://support.microsoft.com/?kbid=824196
> _________________________________________________________
> 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?TGFuY2U=?= <Lance@discussions.microsoft.com> wrote on 21
> nov 2007 in microsoft.public.windows.terminal_services:
>
> > I have a 2k3 Terminal server that has been set up and running
> > for approximately 2 years, which as been updated to SP1, SP2 and
> > RC2, with all current Updates.
> >
> > I need to replace this server so I am setting up a new Terminal
> > Server. I set up the new server using RC2, installed SP2 and
> > did all the windows updates. Set up all the Licensing and
> > Terminal Services configurations the EXACT SAME as the original
> > Terminal Server that has been running for about 2 years just
> > fine.
> >
> > Now the problem. Users can log on with no problems. But when I
> > try to remote control the users using Terminal Server Manager,
> > the exact same as I do with the 2 year old Terminal Server, I
> > receive "Error 7054 - The system has reached its licensed logon
> > limit" I have searched, and looked and searched some more for
> > an answer for this and am only able to find one other thread
> > with the same problem which I can find now, but I have tried
> > everything in that thread to no avail. On top of that, this is
> > the second time I have tried to install and configure this
> > server. I tried a couple months ago and gave up because of this
> > problem, now I am in the exact same situation.
> >
> > Can anyone provide even a hint of help or direction on this.
> >
> > Thanks
>
 
Re: Cannot Remote Control Users

It's the Licensing applet in Control Panel.
Have you checked the EventLog?
As the article explains, having enough server CALs is no guarantee
for not getting the error, since the Licensing Logging Service is
unreliable. That's why the recommendation is to stop and disable
it.

The Licensing Manager under Administrative tools is the Terminal
Services Licensing Manager. That doesn't report CALs, it report TS
CALs. And I don't think that those are a problem, since they
produce different error messages, but I would need to know the
EventID, Source and Description to be sure.
_________________________________________________________
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?TGFuY2U=?= <Lance@discussions.microsoft.com> wrote on 21
nov 2007 in microsoft.public.windows.terminal_services:

> I am assuming this is the Licensing icon under Administrative
> Tools. I have enabled the license Logging Service which allowed
> me to open this. If this is the case, it opens the licensing on
> the Domain Controller which is the same exact thing that happens
> on the 2 year old Terminal Server. There are more than enough
> CAL's in there.
>
> Let me know if there is something else I need to check.
>
> "Vera Noest [MVP]" wrote:
>
>> This message usually has to do with server CALs, not TS CALs.
>> There should be an Event in the EventLog which gives (slightly)
>> more details about which product is out of its licensed limit,
>> i.e. the Windows 2003 OS.
>>
>> Make sure that you have the proper amount of server CALs to be
>> compliant with the EULA, and then stop and disable the
>> Licensing Logging Service. Documented here:
>>
>> 824196 - Description of the License Logging Service in Windows
>> Server Operating Systems
>> http://support.microsoft.com/?kbid=824196
>> _________________________________________________________
>> 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?TGFuY2U=?= <Lance@discussions.microsoft.com> wrote on
>> 21 nov 2007 in microsoft.public.windows.terminal_services:
>>
>> > I have a 2k3 Terminal server that has been set up and running
>> > for approximately 2 years, which as been updated to SP1, SP2
>> > and RC2, with all current Updates.
>> >
>> > I need to replace this server so I am setting up a new
>> > Terminal Server. I set up the new server using RC2,
>> > installed SP2 and did all the windows updates. Set up all
>> > the Licensing and Terminal Services configurations the EXACT
>> > SAME as the original Terminal Server that has been running
>> > for about 2 years just fine.
>> >
>> > Now the problem. Users can log on with no problems. But
>> > when I try to remote control the users using Terminal Server
>> > Manager, the exact same as I do with the 2 year old Terminal
>> > Server, I receive "Error 7054 - The system has reached its
>> > licensed logon limit" I have searched, and looked and
>> > searched some more for an answer for this and am only able to
>> > find one other thread with the same problem which I can find
>> > now, but I have tried everything in that thread to no avail.
>> > On top of that, this is the second time I have tried to
>> > install and configure this server. I tried a couple months
>> > ago and gave up because of this problem, now I am in the
>> > exact same situation.
>> >
>> > Can anyone provide even a hint of help or direction on this.
>> >
>> > Thanks
 
Back
Top