locked
Cannot remote control users sessions using Terminal Services Manager RRS feed

  • Question

  • Hello all

    I have recently put Terminal Services on one of our Windows 2003 x64 Standard servers, before installed could remote control another admin no problem.

    When I now go to remote control a user, I get Session (ID#) remote control failed.

    (Error 7054 - The system has reached its licensed logon limit.  Please try again later.)

    Run LSView and confirms that it can see the licensing server.

    Anyone got any ideas, doesn't make any sense?

    Many Thanks


    Colin
    Tuesday, October 27, 2009 12:11 PM

Answers

All replies

  • Did you enable Remote Desktop or actually instaled the Terminal Services role? Normally you will get another message when licensing in the issue. It looks like your server is still running in Remote Administration mode which allows a maximum of 2 remote connections.
    http://sbc.vanbragt.net
    Tuesday, October 27, 2009 1:17 PM
  • Installed Terminal Services, not running in remote admin mode as we are getting more than 2 remote connections on the server.
    Tuesday, October 27, 2009 1:52 PM
  • All of these are just ideas from research - I have actually never experienced this issue.  I h found alot of posts like this one:

    http://www.brianmadden.com/forums/t/16694.aspx

    So with that in mind:

    Do you have enough windows CALs for logons?

    Is the time correct on the License server?

    have you tried disabling LLS: http://support.microsoft.com/kb/824196


    Hope this helps,

    Kristin L. Griffin

    Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!) 
    Tuesday, October 27, 2009 6:25 PM
  • I'm running into the same problem except this is on a Windows 2003 Enterprise Edition R2. Before this, the server was a Standard Edition w/o R2 and I could remote control without problems. The hard drive was getting old and I rebuilt the whole server using Enterprise Edition R2. I called it the same name using the same IP and hardware and re-added it back to the domain. Only thing changed was a much larger capacity hard drive. The license server is on a domain controller and terminal services licensing does not seem to be the problem. Sessions are logging on fine except the ones which used to work from Mac Remote Desktop don't work anymore. I installed CoRD on the Macs instead and that worked. It looks like the server thinks it is in Remote Administration mode when the Terminal Services Manager tries to remote control sessions even though it is installed as a Terminal Server. The error seems similar to what you get when you have too many sessions in Remote Administration mode. The License Logging Server is not on and it is disabled. Any help would be much appreciated.

    If anyone can answer this question, it might help. Is your server's licensing mode per device per user or is it per server mode for the terminal servers that are able to remote control fine? Because it only allows a one-time change from per server to per device per user, I have to find out before I pull the trigger to try that. Thanks.
    Tuesday, December 1, 2009 9:18 AM
  • I'm running into the same problem except this is on a Windows 2003 Enterprise Edition R2. Before this, the server was a Standard Edition w/o R2 and I could remote control without problems. The hard drive was getting old and I rebuilt the whole server using Enterprise Edition R2. I called it the same name using the same IP and hardware and re-added it back to the domain. Only thing changed was a much larger capacity hard drive. The license server is on a domain controller and terminal services licensing does not seem to be the problem. Sessions are logging on fine except the ones which used to work from Mac Remote Desktop don't work anymore. I installed CoRD on the Macs instead and that worked. It looks like the server thinks it is in Remote Administration mode when the Terminal Services Manager tries to remote control sessions even though it is installed as a Terminal Server. The error seems similar to what you get when you have too many sessions in Remote Administration mode. The License Logging Server is not on and it is disabled. Any help would be much appreciated.

    If anyone can answer this question, it might help. Is your server's licensing mode per device per user or is it per server mode for the terminal servers that are able to remote control fine? Because it only allows a one-time change from per server to per device per user, I have to find out before I pull the trigger to try that. Thanks.

    I had the same problem with a Windows 2003 Enterprise R2 server. I uninstalled Terminal Services, rebooted, the reinstalled and rebooted it from Add/Remove Windows Components and it seems to have cleared the issue up.
    Friday, January 22, 2010 3:44 AM
  • Hi, I am having the exact same problem but this didnt work for me. Can anyone help\advise please?
    Monday, January 7, 2013 8:43 AM
  • Recently, I have the same issue. I have done the following steps.

    Run --tscc.msc -- RDP-TCP properties --> Permissions --> Select the administrator and  Click on Advanced.

    Select the Name and click on Edit button, then Select the check box to allow the "Remote Control". Click ok.
    (If administrator name is not appeared in the "Group or user names" list, click on Add button and add the administrator, to whom you want to give remote control permissions.)

    Now test with a new user.

    Also check this article,

    http://www.99technuts.com/others/terminal-services/common-issues/access-denied-trying-to-remote-control-a-user-session/

    Monday, January 7, 2013 10:00 AM
  • Hi,

    I am experiancing the same issue exactly, were you able to resolve yours?

    thanks


    • Edited by ArikTeleal Monday, January 28, 2013 1:30 PM
    Monday, January 28, 2013 11:14 AM