RemoteApp Problem: The Connection was denied because the user account is not authorized for remote login

While attempting to connect to a RemoteApp with a standard user account, you may receive this message:

This can be caused by not having the logged on user as a member of the Remote Desktop Users group on the Remote Desktop Server. Another reason why you may experience this issue is if you are still on the 180 grace period for RDS licensing. To clear up this problem, reboot the RDS server.

if this still does not work while you are in the grace period add the users, or preferably a group, to the allowed list of users who can log into the RDS server.

On the RDS server, Click Start.

Right click Computer and select Properties

Click Remote Settings

Click Select Users

Click Add.

Add in the User or groups that you want to be able to log in through Remote Desktop Services to this server.

You should be able to access your RemoteApp now.

Comments

Anonymous said…

Thanks for the post

February 18, 2013 at 11:50 PM

BikerSco said…

Thanks for the tip mate, I tried everything even adding the user to the admin group and it still wouldnt allow him to connect. Now he can thanks to you.

April 25, 2013 at 8:16 AM

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Jason Yoder, MCT

Search This Blog