User without local admin rights can't connect to Win8 PC via RDP
We have a user that until recently had local admin rights on his Win10 PC. He needs to connect to a Win8 VM on Azure via Remote Deskop. This worked fine until we had to remove his local admin rights.
Now he always gets a 0x80004005 Authentication error if he tries to connect.
If we run RDP as an admin it works again.
Any idea why this happens?
windows-10 windows-8 remote-desktop administrator
asked Jan 4 at 16:49
RemyRemy
1111213
add a comment |
We have a user that until recently had local admin rights on his Win10 PC. He needs to connect to a Win8 VM on Azure via Remote Deskop. This worked fine until we had to remove his local admin rights.
Now he always gets a 0x80004005 Authentication error if he tries to connect.
If we run RDP as an admin it works again.
Any idea why this happens?
windows-10 windows-8 remote-desktop administrator
asked Jan 4 at 16:49
RemyRemy
1111213
add a comment |
We have a user that until recently had local admin rights on his Win10 PC. He needs to connect to a Win8 VM on Azure via Remote Deskop. This worked fine until we had to remove his local admin rights.
Now he always gets a 0x80004005 Authentication error if he tries to connect.
If we run RDP as an admin it works again.
Any idea why this happens?
windows-10 windows-8 remote-desktop administrator
asked Jan 4 at 16:49
RemyRemy
1111213
We have a user that until recently had local admin rights on his Win10 PC. He needs to connect to a Win8 VM on Azure via Remote Deskop. This worked fine until we had to remove his local admin rights.
Now he always gets a 0x80004005 Authentication error if he tries to connect.
If we run RDP as an admin it works again.
Any idea why this happens?
windows-10 windows-8 remote-desktop administrator
windows-10 windows-8 remote-desktop administrator
asked Jan 4 at 16:49
RemyRemy
1111213
asked Jan 4 at 16:49
RemyRemy
1111213
asked Jan 4 at 16:49
RemyRemy
1111213
asked Jan 4 at 16:49
RemyRemy
1111213
asked Jan 4 at 16:49
RemyRemy
1111213
1111213
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Local admin accounts include the ability to connect via RDP. To give the user rights to RDP without full admin rights, add them to the local "Remote Desktop Users" group from the system in question.
Click Start and type "compmgmt.msc"
Expand "Local Users and Groups"
Click Groups and then double-click "Remote Desktop Users" on the right
Add the users account (remember to add from the domain, rather than the local system, if this is a domain environment.)
answered Jan 9 at 18:06
DebraDebra
3,85011021
I've tried that, but the user is an Azure AD user and I usually can't see them on the list. So I just added "Everybody" to the group. But that did not change anything.
– Remy
Jan 14 at 9:01
Also, I've done this on the local PC, not the one we connect to. Did I get that correctly?
– Remy
Jan 14 at 9:12
No, the account has to exist on the one you're connecting to (the "remote" system) to allow that user to RDP to that system.
– Debra
Jan 14 at 16:45
There we use a different account that is shared between people. And if I start his RPD with Admin rights it works.
– Remy
Jan 14 at 18:56
As stated, Administrator accounts include the right to RDP to the system. If you want a non-admin to be able to RDP to a system, they must be added to the "Remote Desktop Users" group on the target system. The username & password that is being used to connect must be exactly the same as what is set on the target remote system. There is no way I know of around this requirement. And FWIW, giving this right to the "Everyone" group creates a huge security risk. I am not understanding why you don't just add the individual's user account to the RDP group and make the passwords the same.
– Debra
Jan 14 at 19:17
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390611%2fuser-without-local-admin-rights-cant-connect-to-win8-pc-via-rdp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Local admin accounts include the ability to connect via RDP. To give the user rights to RDP without full admin rights, add them to the local "Remote Desktop Users" group from the system in question.
Click Start and type "compmgmt.msc"
Expand "Local Users and Groups"
Click Groups and then double-click "Remote Desktop Users" on the right
Add the users account (remember to add from the domain, rather than the local system, if this is a domain environment.)
answered Jan 9 at 18:06
DebraDebra
3,85011021
I've tried that, but the user is an Azure AD user and I usually can't see them on the list. So I just added "Everybody" to the group. But that did not change anything.
– Remy
Jan 14 at 9:01
Also, I've done this on the local PC, not the one we connect to. Did I get that correctly?
– Remy
Jan 14 at 9:12
No, the account has to exist on the one you're connecting to (the "remote" system) to allow that user to RDP to that system.
– Debra
Jan 14 at 16:45
There we use a different account that is shared between people. And if I start his RPD with Admin rights it works.
– Remy
Jan 14 at 18:56
As stated, Administrator accounts include the right to RDP to the system. If you want a non-admin to be able to RDP to a system, they must be added to the "Remote Desktop Users" group on the target system. The username & password that is being used to connect must be exactly the same as what is set on the target remote system. There is no way I know of around this requirement. And FWIW, giving this right to the "Everyone" group creates a huge security risk. I am not understanding why you don't just add the individual's user account to the RDP group and make the passwords the same.
– Debra
Jan 14 at 19:17
add a comment |
Local admin accounts include the ability to connect via RDP. To give the user rights to RDP without full admin rights, add them to the local "Remote Desktop Users" group from the system in question.
Click Start and type "compmgmt.msc"
Expand "Local Users and Groups"
Click Groups and then double-click "Remote Desktop Users" on the right
Add the users account (remember to add from the domain, rather than the local system, if this is a domain environment.)
answered Jan 9 at 18:06
DebraDebra
3,85011021
I've tried that, but the user is an Azure AD user and I usually can't see them on the list. So I just added "Everybody" to the group. But that did not change anything.
– Remy
Jan 14 at 9:01
Also, I've done this on the local PC, not the one we connect to. Did I get that correctly?
– Remy
Jan 14 at 9:12
No, the account has to exist on the one you're connecting to (the "remote" system) to allow that user to RDP to that system.
– Debra
Jan 14 at 16:45
There we use a different account that is shared between people. And if I start his RPD with Admin rights it works.
– Remy
Jan 14 at 18:56
As stated, Administrator accounts include the right to RDP to the system. If you want a non-admin to be able to RDP to a system, they must be added to the "Remote Desktop Users" group on the target system. The username & password that is being used to connect must be exactly the same as what is set on the target remote system. There is no way I know of around this requirement. And FWIW, giving this right to the "Everyone" group creates a huge security risk. I am not understanding why you don't just add the individual's user account to the RDP group and make the passwords the same.
– Debra
Jan 14 at 19:17
add a comment |
Local admin accounts include the ability to connect via RDP. To give the user rights to RDP without full admin rights, add them to the local "Remote Desktop Users" group from the system in question.
Click Start and type "compmgmt.msc"
Expand "Local Users and Groups"
Click Groups and then double-click "Remote Desktop Users" on the right
Add the users account (remember to add from the domain, rather than the local system, if this is a domain environment.)
answered Jan 9 at 18:06
DebraDebra
3,85011021
Local admin accounts include the ability to connect via RDP. To give the user rights to RDP without full admin rights, add them to the local "Remote Desktop Users" group from the system in question.
Click Start and type "compmgmt.msc"
Expand "Local Users and Groups"
Click Groups and then double-click "Remote Desktop Users" on the right
Add the users account (remember to add from the domain, rather than the local system, if this is a domain environment.)
answered Jan 9 at 18:06
DebraDebra
3,85011021
answered Jan 9 at 18:06
DebraDebra
3,85011021
answered Jan 9 at 18:06
DebraDebra
3,85011021
answered Jan 9 at 18:06
DebraDebra
3,85011021
3,85011021
I've tried that, but the user is an Azure AD user and I usually can't see them on the list. So I just added "Everybody" to the group. But that did not change anything.
– Remy
Jan 14 at 9:01
Also, I've done this on the local PC, not the one we connect to. Did I get that correctly?
– Remy
Jan 14 at 9:12
No, the account has to exist on the one you're connecting to (the "remote" system) to allow that user to RDP to that system.
– Debra
Jan 14 at 16:45
There we use a different account that is shared between people. And if I start his RPD with Admin rights it works.
– Remy
Jan 14 at 18:56
As stated, Administrator accounts include the right to RDP to the system. If you want a non-admin to be able to RDP to a system, they must be added to the "Remote Desktop Users" group on the target system. The username & password that is being used to connect must be exactly the same as what is set on the target remote system. There is no way I know of around this requirement. And FWIW, giving this right to the "Everyone" group creates a huge security risk. I am not understanding why you don't just add the individual's user account to the RDP group and make the passwords the same.
– Debra
Jan 14 at 19:17
add a comment |
I've tried that, but the user is an Azure AD user and I usually can't see them on the list. So I just added "Everybody" to the group. But that did not change anything.
– Remy
Jan 14 at 9:01
Also, I've done this on the local PC, not the one we connect to. Did I get that correctly?
– Remy
Jan 14 at 9:12
No, the account has to exist on the one you're connecting to (the "remote" system) to allow that user to RDP to that system.
– Debra
Jan 14 at 16:45
There we use a different account that is shared between people. And if I start his RPD with Admin rights it works.
– Remy
Jan 14 at 18:56
As stated, Administrator accounts include the right to RDP to the system. If you want a non-admin to be able to RDP to a system, they must be added to the "Remote Desktop Users" group on the target system. The username & password that is being used to connect must be exactly the same as what is set on the target remote system. There is no way I know of around this requirement. And FWIW, giving this right to the "Everyone" group creates a huge security risk. I am not understanding why you don't just add the individual's user account to the RDP group and make the passwords the same.
– Debra
Jan 14 at 19:17
I've tried that, but the user is an Azure AD user and I usually can't see them on the list. So I just added "Everybody" to the group. But that did not change anything.
– Remy
Jan 14 at 9:01
I've tried that, but the user is an Azure AD user and I usually can't see them on the list. So I just added "Everybody" to the group. But that did not change anything.
– Remy
Jan 14 at 9:01
Also, I've done this on the local PC, not the one we connect to. Did I get that correctly?
– Remy
Jan 14 at 9:12
Also, I've done this on the local PC, not the one we connect to. Did I get that correctly?
– Remy
Jan 14 at 9:12
No, the account has to exist on the one you're connecting to (the "remote" system) to allow that user to RDP to that system.
– Debra
Jan 14 at 16:45
No, the account has to exist on the one you're connecting to (the "remote" system) to allow that user to RDP to that system.
– Debra
Jan 14 at 16:45
There we use a different account that is shared between people. And if I start his RPD with Admin rights it works.
– Remy
Jan 14 at 18:56
There we use a different account that is shared between people. And if I start his RPD with Admin rights it works.
– Remy
Jan 14 at 18:56
As stated, Administrator accounts include the right to RDP to the system. If you want a non-admin to be able to RDP to a system, they must be added to the "Remote Desktop Users" group on the target system. The username & password that is being used to connect must be exactly the same as what is set on the target remote system. There is no way I know of around this requirement. And FWIW, giving this right to the "Everyone" group creates a huge security risk. I am not understanding why you don't just add the individual's user account to the RDP group and make the passwords the same.
– Debra
Jan 14 at 19:17
As stated, Administrator accounts include the right to RDP to the system. If you want a non-admin to be able to RDP to a system, they must be added to the "Remote Desktop Users" group on the target system. The username & password that is being used to connect must be exactly the same as what is set on the target remote system. There is no way I know of around this requirement. And FWIW, giving this right to the "Everyone" group creates a huge security risk. I am not understanding why you don't just add the individual's user account to the RDP group and make the passwords the same.
– Debra
Jan 14 at 19:17
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390611%2fuser-without-local-admin-rights-cant-connect-to-win8-pc-via-rdp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
