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

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix. This customization deals with Group Policy and PowerShell. For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material. I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO. This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy. One organization in the crowd had over 5,000 Group Policies. In an environment like that, the comment section can be priceless. I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2 # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2 #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers. The first command creates a collection with 2 duplicates of both 1 and 2. The second command creates another collection with the duplicates filtered out. The Compare-Object cmdlet will first find items that are diffe

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.

Jason Yoder, MCT

Search This Blog