Link to home
Start Free TrialLog in
Avatar of rpm
rpmFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Different access permissions for two terminal servers

Hi,

I have a network with three servers, as follows:

1x Windows SBS 2003, primary domain controller
2x Windows 2008 Servers, domian controllers and terminal services servers

The SBS 2003 box should only accept terminal services sessions from administrators, whilst each of the two 2008 boxes shoud accept TS connections from a different group of users. (That is a different group of users for each 2008 box.)

Initially I went into computer/properties on each 2008 box and tried to set the users who could log into terminal services from there, but I noticed that changing this on one, changed it on both.

I then tried setting the remote access permissions to administrators only and created a group policy object for each 2008 box, and in each object setting the "allow logon through terminal services" to the appropriate group. I linked both of these policy objects to the domain controllers OU and then filtered each one to the appropriate computer. This did not appear to allow anyone but administrators in.

How do I acheive what I need?
Avatar of RoelvanDijnen
RoelvanDijnen
Flag of Netherlands image

Did you set:
Computer Configuration > Windows Settings > Security Settings > Restricted Groups > Builtin\Remote Desktop Users?

And apply the GPO object in scope > security filtering to a AD security group for the Server (SG-TS01-SERVER) AND to a security group for the Users (SG-TS01USERS)
Avatar of Mino DC
Try this.

Logon on first 2008 server.
In server manager click on :
Configuration->Local Users and Groups->Groups
On Remote Desktop User and click Properties. Add user or group that you want.

Now please login on the second 2008 server and do the same operations.
Avatar of rpm

ASKER

MinoDC: There isn't a Local Users & Groups ... presumably because the server is a DC
Avatar of rpm

ASKER

RoelvanDijnen: A couple of questions for you ...
1) The Restricted Groups container is currently empty in my policy object ... do I add remote desktop users into this empty container?
2) I am not completly sure about your instructions for linking this policy object. Do I still link it to the Domain Controllers OU, and what filtering should I be using, is that the computer object and the user group object with access to this server?
Thanks,
Richard
ASKER CERTIFIED SOLUTION
Avatar of ormerodrutter
ormerodrutter
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I use the 2008 GPO editor, so it may be a litle different.
But yes, I right click in de empty space, click "add" and browse for the Remote Desktop Users.
Then I select the mebers of the group in the same way..

Second:
Create three security groups for the servers (DC01SERVER, TS01SERVER, TS02SERVER) AND three groups for the users (DC01USER, TS01USER, TS02USER).  
Then create three GPO objects and link them al to the DC OU, but with different Security groups filtering.
Make sure there is no inherrited GPO interfering of course :)
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of rpm

ASKER

Following the general cconsensus, I have demoted one of the servers to a member server.

Now I cannot log on remotely at all! The staff at the data centre have logged on locally and confirmed that the administrator is in the remote access permissions group, but when I log on as the administrator remotely, it says the user doesn't have permissions. Any ideas?

My colleague is heading over to the data centre now

Richard
On server where you are having the issue, do following.
See to it RDP is enabled on the server with issue,just confirm again.

Take a registry backup on the desktop &  Delete the following keys  

Start Registry Editor.
Locate and then click the  following registry  subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters
Under  this registry subkey, delete the following values:
Certificate
X509  Certificate
X509 Certificate ID

Quit Registry Editor, and then restart the  server  
Try taking RDP & if still it doesn't connect do the below.

Click Start, click Run, type regedit, and then  click OK   Locate and click the following subkey on the  left:  

HKLM\SYSTEM\CurrentControlSet\Control\Terminal  Server\WinStations\RDP-Tcp    

On the right,  locate and right-click on the  value named Security,
choose Rename, type Security.backup, and  then press Enter.  

Reboot the server as i had issue once did same got it working.
Also check if Remote Access has been enabled on the server. Then check if access was blocked by firewall (Windows firewall or vendor's). For your reference RDP use port 3389 so if you can't find anything relevent open this port on the server firewall.
Avatar of rpm

ASKER

Turned out to be an IPv6 DNS error!