none
Permissions error when attempting to use RDP to a Server 2003 machine

    Question

  • Recieve the following error when attempting to open a RDP session to my Server 2003 machine. 

    "To log on to this remote computer, you must have Terminal Server User Access permissions on this computer. By default, members of the Remote Desktop Users group have these permissions. If you are not a member of the Remote Desktop Users Group or another group that has these permissions, or if the Remote Desktop User group does not have these permissions, you must be granted these permissions manually."

    I've checked membership on the remote Desktop Users group, and the user i am testing with is definitely in there. 

    Remote Desktop User group is allowed "Log on with Terminal Services" permission on the box in question. 

    Connection permissions are correct in Terminal Server Configuration. 

    I'm not sure where else to look. 

    This is a server 2003 R2 box also running an Exchange role. 

    Friday, August 31, 2012 2:17 PM

Answers

  • Hi,

    Please install Terminal Server Licensing via Control Panel -- Add or Remove Programs -- Add/Remove Windows Components.  After that you may use TS Licensing Manager (licmgr.exe) to Activate the server and install purchased RDS/TS CALs.

    NOTE: If the only thing you need to do is connect to this server using Remote Desktop for administration purposes like adding/deleting users, configuring the server, checking error logs, etc., then you do not need to have Terminal Server installed and you do not need TS CALs.  In this case you need to uninstall Terminal Server via Control Panel -- Add or Remove Programs -- Add/Remove Windows Components.

    Thanks.

    -TP

    Friday, August 31, 2012 3:41 PM
    Moderator

All replies

  • Hi,

    1. Is the user a member of the local Remote Desktop Users group on this box, as viewed from Computer Management?

    2. In Terminal Services Configuration (tscc.msc), is the Licensing mode set to match the type of purchased TS CALs that you have installed on the TS Licensing server?  For example, if you purchased and installed Per User RDS/TS CALs then the licensing mode should be set to Per User.

    3. In Terminal Services Configuration, is the License server discovery mode set to Use these license servers with the name of your TS Licensing server entered in the box?

    4. Is the TS Licensing server running and accessible from this server?

    -TP

    Friday, August 31, 2012 2:41 PM
    Moderator
  • 1. yes. 

    2. Licensing mode is set to Per User. 

    3. Yes.

    4. it does not appear to be. Opening the Terminal Server Licensing console tells me that no licensing servers can be found. 

    Friday, August 31, 2012 3:17 PM
  • Hi,

    1. On the TS Licensing server, please make sure the Terminal Services Licensing or Remote Desktop Licensing service is started.

    2. Please make sure there are no firewalls blocking communication between the TS and the TS Licensing server.

    Thanks.

    -TP

    Friday, August 31, 2012 3:20 PM
    Moderator
  • I do not see a Terminal Services Licensing service on the server in question. THis is a single-server environment. 

    Friday, August 31, 2012 3:25 PM
  • Hi,

    Please install Terminal Server Licensing via Control Panel -- Add or Remove Programs -- Add/Remove Windows Components.  After that you may use TS Licensing Manager (licmgr.exe) to Activate the server and install purchased RDS/TS CALs.

    NOTE: If the only thing you need to do is connect to this server using Remote Desktop for administration purposes like adding/deleting users, configuring the server, checking error logs, etc., then you do not need to have Terminal Server installed and you do not need TS CALs.  In this case you need to uninstall Terminal Server via Control Panel -- Add or Remove Programs -- Add/Remove Windows Components.

    Thanks.

    -TP

    Friday, August 31, 2012 3:41 PM
    Moderator
  • Hi,

    sometimes when the number of user profiles created in the the server while remoting exceeded such kind of issue occurs. so you need to remove some unwanted user profiles on the affected the server from the c drive users or documents and settings folder.

    Thanks,

    -Hamis


    Wednesday, July 16, 2014 9:52 AM