Purpose of Remote Desktop GPO if machines needs to be configured locally
Hi,
I created A GPO in my Windows server 2012 domain to allow users to connect to workstations remotely through Remote Desktop.
Following procedure had been applied: http://www.dannyeckes.com/server-2012-enable-remote-desktop-rdp-group-policy-gpo/
GPO have been updated (gpudate / force) and workstation even rebooted.
Users that have no administrator privilege cannot remotely login and get the following messages: "The connection was denied because the user account is not authorized for remote login"
I have read on different posts that the remote desktop permissions should be given locally by adding the necessary groups / users. Didn't try but that will work for sure.
I'm wondering what is then the purpose of the GPO if permissions are to be given locally !
And also, what do you do if you have 200 machines to configure !
Regards,
David
I created A GPO in my Windows server 2012 domain to allow users to connect to workstations remotely through Remote Desktop.
Following procedure had been applied: http://www.dannyeckes.com/server-2012-enable-remote-desktop-rdp-group-policy-gpo/
GPO have been updated (gpudate / force) and workstation even rebooted.
Users that have no administrator privilege cannot remotely login and get the following messages: "The connection was denied because the user account is not authorized for remote login"
I have read on different posts that the remote desktop permissions should be given locally by adding the necessary groups / users. Didn't try but that will work for sure.
I'm wondering what is then the purpose of the GPO if permissions are to be given locally !
And also, what do you do if you have 200 machines to configure !
Regards,
David
ASKER
200 workstations is of course only an example. The goal is here to allow some users to access physical machines remotely if needed. I'm trying to understand why the GPO doesn't work or, in other words, to understand what is the purpose of such a GPO while it seems mandatory (correct me if I'm wrong) to still manually add a selection of users/domain groups on each machine.
As I said, the purpose of the GPO is meant to control RDSH/RDVH servers. In those environments the GPO is an effective tool. It is NOT meant to be used how you are trying to use it, and so it is proving to be less than ideal. You are trying to use a screwdriver to pound in a nail.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
RDSH used to be called TS, and has been built into windows just as long as group policies have, since windows 2000. So you at closjg a question when you haven't prove your own theory (which you admit to with your "to be confirmed" comment AND your "facts" are blatantly wrong. But good luck to you. I'll remember you and won't help further since you clearly know the answer before you ever ask the question.
ASKER
Excuse me Cliff but you simply didn't answer the original question (how can I allow some users to connect to workstations through RDP using GPOs and without having to add local security manually) and I didn't know the answer before posting. I just kept on reading and trying.
I can know confirm that the default "Authenticated Users" group in the "Security Filtering" section of the GPO needs to be replaced by the group "Remote Desktop Users" (in my case) and do a gpupdate. This wasn't described in the procedure I used as you can verify.
Before virtualization existed, it was already possible to connect to workstations through RDP using GPOs. That is all I wanted to do. So please, be a good player !
I can know confirm that the default "Authenticated Users" group in the "Security Filtering" section of the GPO needs to be replaced by the group "Remote Desktop Users" (in my case) and do a gpupdate. This wasn't described in the procedure I used as you can verify.
Before virtualization existed, it was already possible to connect to workstations through RDP using GPOs. That is all I wanted to do. So please, be a good player !
ASKER
No solution provided by member. Solved myself.
You'd instead set up RDSH or RDVH, and in that setup, you don't configure or touch a bunch of individual machines. Your desktops are centralized on fewer large servers. RDSH makes the necessary changes by default, and RDVH is based off an image that has been purpose-built for the task and also has the necessary changes. So touching local installs becomes a non-issue.
So basically if you are trying to allow access to 200 workstations ,chances are you are doing something wrong. And are probably breaking the software EULA in the process.