Solved

Purpose of Remote Desktop GPO if machines needs to be configured locally

Posted on 2014-09-06
7
262 Views
Last Modified: 2014-09-11
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
0
Comment
Question by:Urbantrax
  • 4
  • 3
7 Comments
 
LVL 57

Expert Comment

by:Cliff Galiher
ID: 40307583
You usually wouldn't ever give remote access to 200 machines. Not just because of the policy issue, but because of the network traffic l, management, information security....remote desktop was never designed to be used in that way.

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.
0
 

Author Comment

by:Urbantrax
ID: 40307716
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.
0
 
LVL 57

Expert Comment

by:Cliff Galiher
ID: 40307722
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.
0
Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

 

Accepted Solution

by:
Urbantrax earned 0 total points
ID: 40307843
Don't agree with your vision. Remote Desktop GPO already existed before RDSH/RDVH servers and it is a valid way to connect remotely to Windows workstations. I succeeded to solve the issue: It was apparently a security filtering issue (to be confirmed) or a gpupdate issue.
0
 
LVL 57

Expert Comment

by:Cliff Galiher
ID: 40307886
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.
0
 

Author Comment

by:Urbantrax
ID: 40308293
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 !
0
 

Author Closing Comment

by:Urbantrax
ID: 40316497
No solution provided by member. Solved myself.
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Let’s list some of the technologies that enable smooth teleworking. 
If you get continual lockouts after changing your Active Directory password, there are several possible reasons.  Two of the most common are using other devices to access your email and stored passwords in the credential manager of windows.
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question