Re: Cannot Remote Control: Error 7054

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I did this many times already. Also I tried to remote control a session from
another machines. I did all your suggestion (not the Connect) many times
successfully before we reinstalled our Terminal Server machine.
Remote controlling the session I launched from my own machine is just for
testing, that will never happen in real production because that makes no
sense to do it.
The previous installation worked alright, but we had to reinstall because
the harddrive crashed and this new installation is not working (we
reinstalled last month). What is weird, multiple user, we had 10 users from
10 different machines, connected to TermServ all at once and everybody got
in. The only problem is I cannot Remote Control (I tried to Remote control
from a session with admin login, this is not a Console session).

I cannot use the Connect because that will require the other user to tell me
the password, although they might trust me, I don't want to know their
password.

Maybe I should change my question:
1. How do I check if we have CAL for our Terminal Server?
2. How do I know which machine our TermServ machine is ACTUALLY queries to
get the CAL?
I think the problem is not having CAL for Terminal Server Windows 2003
Server, but our network admin said he put the license already, and I don't
know much about server. How can I check the licensing?

Thank you for responding.


"Vera Noest [MVP]" wrote:

So from clientA you try to remote control another session, which
also runs on clientA, but with a different user name? I don't know
if this is even possible.
Does it work when you try to remote control a session which is
started from another client altogether?

What is it that you are trying to accomplish? Maybe you simply want
to connect to your other session, in stead of remote controlling
it?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?Sm9oYW5uZXM=?= <Johannes@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 13 sep 2007:

Vera,
There is no error log in the EventLog regarding this. I check
the EventLog
before and after my attempt to Remote Control a user session
(from Terminal Services Manager), and the EventLog is the same
before and after. From my laptop, I Remote Desktop to the
Terminal Server, login as Administrator. Then again from my
Laptop, I Remote Desktop to the same Terminal Server but this
time with another user login. From the RDP that I login as
Admin, I use Terminal Services Manager, Right click on the
Session that has my 2nd login and select Remote Control. I got
the error message.

The license server is on our Domain controller. On this Terminal
Server machine, we set the licensing to Auto Discover. Btw, this
Terminal Server machine is Win2K3 Standard Server.
From the Terminal Server Licensing, there is only 1 entry on the
left, and this entry shows our Domain controller machine name.
When I expand it, there are 3 branches:
1. Existing Windows 2000 Server - Terminal Services CAL Token
(per device)
there are a bunch of entry (Issued to), but don't see the
name of this
trouble Terminal Server machine name.
2. Windows Server 2003 - Terminal Server Per User CAL Token
When I clicked on it, on the right pane, I have only one
row, with all
columns say "Not Applicable"
3. Temporary Licenses for WIndows Server 2003 - Terminal Server
Per Device CAL Token
When I clicked on it,on the right pane, there is a bunch of
rows, but
again don't see this troubled machine name.

What should I do?

Jo

"Vera Noest [MVP]" wrote:

Check the EventLog on the server for more info. Repost with
EventID and Source if you need more help.
I believe that this messsage points to a lack of Windows CALs,
rather than TS CALs.
If that's the case, simply stop and disable the License Logging
Service on the TS, since it is known to inaccurate and
shouldn't be used anymore.

Documented here:
824196 - Description of the License Logging Service in Windows
Server Operating Systems
http://support.microsoft.com/?kbid=824196

You can start the TS Licensing Manager to have a look at the TS
CALs which are installed and issued.
_________________________________________________________
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?Sm9oYW5uZXM=?= <Johannes@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 11 sep 2007 in
microsoft.public.windows.terminal_services:

When I try to remote control a session (neither are console
session), I get error:
Session (ID 2) remote control failed
(Error 7054 - The system has reached its licensed logon
limit. Please try again later. )

The old installation didn't have this problem but the hard
drive crashed so we have to reinstall.

Q1. Why do I get this error and how do I fix it?
Q2. a. Is this because we don't have license?
b. Our network admin told me that he already put the
CAL license on
the license manager (on our Domain controller), how do I
check if we actually have CAL for Windows 2003 Terminal
Server?

Btw, here are a few settings:
1. From Terminal Services Configuration
a. Server Settings:
- Licensing Per Device
- License server discovery mode Automatic
b. Connections: RDP-Tcp Properties, Permissions tab
The local admin, which I'm login right now, On
Advanced, Everything
(Query Information, Remote Control, Connect etc) is set to
Allow.

If anybody can help, it's greatly appreciated.

.

Relevant Pages

  • Re: Cannot Remote Control: Error 7054
    ... before and after my attempt to Remote Control a user session (from Terminal ... Terminal Server but this time with another user login. ... I believe that this messsage points to a lack of Windows CALs, ... simply stop and disable the License Logging ...
    (microsoft.public.windows.terminal_services)
  • Re: Cannot Remote Control: Error 7054
    ... Does it work when you try to remote control a session which is ... MCSE, CCEA, Microsoft MVP - Terminal Server ... simply stop and disable the License Logging ...
    (microsoft.public.windows.terminal_services)
  • Re: Remote Control the Console
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... SQL troubleshooting: http://sql.veranoest.net ... Control another session, that neither session can see the other ... Is it possible to Remote Control the Console? ...
    (microsoft.public.windows.terminal_services)
  • Re: Remote Control: Shadowing user sessions from helpdesk local ma
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... TS troubleshooting: http://ts.veranoest.net ... connect to another session. ... if you use RunAs) has Remote Control rights ...
    (microsoft.public.windows.terminal_services)
  • Re: Black Screen after TSADMIN remote session with client.
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... is i'll log into a session to help the ... I ctrl+* to exit the remote control session. ... I log the person off through tsadmin so they can log back in. ...
    (microsoft.public.windows.terminal_services)