Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Monday, November 16, 2015 9:43 PM | 3 votes
I have a clean install of Windwos 10 pro (well actually clean install of 10 home and then upgraded to 10 after a license key ordeal) and I'm trying to RDP but I'm instantly rejected every time. "The connection was denied because the user account is not authorized for remote login."
I have tried with and without checking the box that says allow connections from pcs with network level authentication. But the "select users" button is grayed out.
I've tried connecting with a local user on that pc as well as a microsoft account which is on both pcs. On the local user I've tried with just the username robbie and .\robbie
What step am I missing?
Thursday, November 19, 2015 7:12 PM ✅Answered | 3 votes
Adding that group did not work for me. the add user button was still grayed out.
I tried recovery and that did add the group and I was able to RDP but it didnt' add all of the other missing groups as in my other pro client pcs or your screen grab.
I ended up a full clean install with the proper pro key and all is fine. What a mess!
Monday, November 16, 2015 10:13 PM | 1 vote
Well not sure why the 'select users' is greyed out. But you can add users via Computer Management, so right click stand select Computer Management. Expand Local Users and Groups > Groups. Anybody that is member of Administrators or Remote Desktop Users has access. So is the robbie account and MSA account in either group, if not can they be added?
To connect you have to specify the user on the remote system. So that would be REMOTESYSTEMNAME\Username (the .\ states local machine so not the remote machine). Although is the MSA is an admin on the remote machine that should work.
Does that help? but the greyed out 'select users' is still a puzzle.
Tuesday, November 17, 2015 1:14 AM | 1 vote
What step am I missing?
Maybe none. GUI are often buggy. What about trying a PowerShell equivalent? Perhaps you could get better diagnostics that way.
Bad guess? I don't see anything with PowerShell but WMIC might have some clues for you
PS>wmic.exe /? | Select-string "remote"
RDACCOUNT - Remote Desktop connection permission management.
RDNIC - Remote Desktop connection management on a specific network adapter.
RDPERMISSIONS - Permissions to a specific Remote Desktop connection.
RDTOGGLE - Turning Remote Desktop listener on or off remotely.
Otherwise, as always, I would be trying ProcMon for supplementing anything which could be gleaned by either method.
Good luck
Robert Aldwinckle
Wednesday, November 18, 2015 5:07 AM | 1 vote
Hi,
It is possible that this issue caused by upgrade, if you have access to Group Policy see this setting. You need Windows 10 Pro machines to access it.
Computer configuration | Administrative Templates | Windows Components | Remote Desktop Services | Remote Desktop Session Host | Connections
In the right-pane, double-click Allow users to connect remotely using Terminal Services, set it to Not configured.
Check the “Remote Desktop Users” group in users and groups, because that can be caused by the absence of the Remote Desktop Users group is missing from the container.
Regards,
D. Wu
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Wednesday, November 18, 2015 5:31 PM | 1 vote
I didn't see the anything in the list that said "terminal services" but I did see "Allow users to connect remotely using Remote Desktop Services"
Everything is already set to not configured. But for instance, if I do set it to enable, i can rdp but only as an admin user. And this also grays the radio button options for Remote Desktop in the System Properties Remote tab.
http://i.imgur.com/RSfezMC.png
Wednesday, November 18, 2015 10:13 PM | 1 vote
Right click start select Computer Management. Expand Local Users and Groups > Groups. Is there a 'Remote Desktop Users' group?
Wednesday, November 18, 2015 11:51 PM | 1 vote
Yep but still not able to login with the non admin user
http://i.imgur.com/o5MMSb2.png
Thursday, November 19, 2015 12:17 AM | 1 vote
Thank you for the response and screenshot for clarity.
But your group is 'Remote Management Users' not 'Remote Desktop Users'. My Windows 10 Pro installed from a Pro DVD has 'Remote Desktop Users' with description 'Members in this group are granted the right to logon remotely'. So my thinking is the Home to Pro upgrade by key has missed something perhaps (my Home test PC has only Remote Management Users). Try creating a 'Remote Desktop Users' with description 'Members in this group are granted the right to logon remotely' does the button display, do users in that get access?
Monday, February 22, 2016 1:16 PM | 4 votes
I had same exact problem with Pro upgrade by key and missing groups. A "Reset this PC" fixed it. Luckily I had not configured the install much.
Tuesday, February 23, 2016 12:17 AM | 1 vote
I had the exact same problem, after upgraded from Home to Pro, and did the painful "Reset this PC" as well. Otherwise I was missing a number of groups in computer management. See the before and after "reset" below:
Saturday, June 25, 2016 1:08 PM
Adding that group did not work for me. the add user button was still grayed out.
I tried recovery and that did add the group and I was able to RDP but it didnt' add all of the other missing groups as in my other pro client pcs or your screen grab.
I ended up a full clean install with the proper pro key and all is fine. What a mess!
I have purchased the 8.1 Pro pack upgrade back when Windows 8 came out. That key doesn't work on a Windows 10 clean install. How did you get the proper key?
Saturday, June 25, 2016 6:51 PM
How did you get the proper key?
By finding someone who is sympathetic on Support. That's how it happened to me with W7sp1 Pro. I found the ISO for that and installed it expecting to be able to use my upgrade key with it. Apparently that key is designed to be used only to cover that explicit scenario: the upgrade of W7 to W7 Pro. So, if I hadn't found an understanding support agent to give me a new key I would have had to have gone all the way back to W7 then used my upgrade key and then done all the necessary updating to get that up to W7sp1 level (equivalent to the ISO that I had installed). In fact, I suspect your case could then complicated by the fact that you have already had your "free upgrade" to W10, thus changing the status of your original W8 key.
Good luck
Robert Aldwinckle