Allow log on to Terminal Services right errors
I am configuring a new bunch of new servers to replace our current ones. I have built one server with Windows Server 2003 Enterprise, and configured it to be my Domain, DHCP and DNS server. I also have several other servers that will be configured exactly alike that will run Windows Server 2003 Standard and are configured to be Terminal Servers (10 TS's in all).
I am currently doing testing with my DC Server and a master image TS server. The TS is in the Domain, and when I log in using RDP as administrator it works great. But when I attempt to login as a user I get the "to log onto this remote computer, you must have Allow log on to Terminal Services rights" error.
I have allowed Users and Authenticated Users to be able to login to Terminal Serverice via the Group Policy. I even allowed them to login locally using the Group Policy. When I attempt an RDP connection to the DC my user can log in successfully, but when I try to login to my TS I get the error.
I have researched the Experts Exchange knowledge base and tried multiple recommendations but none of them seem to work in my TS environment. Are there settings on the Terminal Server its self that I need to change, or is everything controlled at the Domain Controller level? Thanks in advance.
I am currently doing testing with my DC Server and a master image TS server. The TS is in the Domain, and when I log in using RDP as administrator it works great. But when I attempt to login as a user I get the "to log onto this remote computer, you must have Allow log on to Terminal Services rights" error.
I have allowed Users and Authenticated Users to be able to login to Terminal Serverice via the Group Policy. I even allowed them to login locally using the Group Policy. When I attempt an RDP connection to the DC my user can log in successfully, but when I try to login to my TS I get the error.
I have researched the Experts Exchange knowledge base and tried multiple recommendations but none of them seem to work in my TS environment. Are there settings on the Terminal Server its self that I need to change, or is everything controlled at the Domain Controller level? Thanks in advance.
Darius Ghassem
Go to Run type GPEDIT.MSC then Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment then look for Allow log ong through Terminal Server.
ASKER
When I look I see the groups, Authenticated Users, Users, and Remote Desktop users.
Go to Terminal Server Configuration then right-click the RDP-TCP then go to the permissions tab add the users or groups you want to RDP into the server.
ASKER
I found the solution.
Went onto the Terminal Server.
Opened Administrative Tools - Computer Management
Under Computer Management (Local), open System Tools, Local Users and Groups, click on Groups.
Enter Remote Desktop Users group properties.
Add Domain Users
Click OK until I got out and tested successfully
Went onto the Terminal Server.
Opened Administrative Tools - Computer Management
Under Computer Management (Local), open System Tools, Local Users and Groups, click on Groups.
Enter Remote Desktop Users group properties.
Add Domain Users
Click OK until I got out and tested successfully
The Remote Desktop Group has all permissions to Terminal Server but if you want to add another group or just another user without using the Built-in Remote Desktop Group then you would need to add them like this:
Terminal Server Configuration then right-click the RDP-TCP then go to the permissions tab add the users or groups you want to RDP into the server.
I thought you were asking how to add another group to Terminal Server into the Server.
Terminal Server Configuration then right-click the RDP-TCP then go to the permissions tab add the users or groups you want to RDP into the server.
I thought you were asking how to add another group to Terminal Server into the Server.
ASKER
I was asking how to do that. My experience with Terminal Server farms is very limited, since I usually one deal with small clients with a single multi-funtion server IE , DC-DHCP-DNS-Termianl Server etc. So using my experience I did everything that I found was recommended by the Experts to resolve the issue, but no dice.
What I thought could happen was that I could make a single change at the DC level and all of the Terminal Servers would then allow the users in the AD to login. This wasn't the case, as I could login using a user via RDP to the DC but not the TS'. When I changed what sub-groups were a part of the main Remote Desktop User group (IE, Domain Users)that seemed to work. So it appears as though a one stop solution isn't available, and I'll have to make the said change to each of my TS' as they join the domain.
I'll try doing it your way though since it would be a more comfortable solution rather than messing with local groups. Thanks for the response, I'll close this question within the next couple of days when I have a final grasp on the solution.
What I thought could happen was that I could make a single change at the DC level and all of the Terminal Servers would then allow the users in the AD to login. This wasn't the case, as I could login using a user via RDP to the DC but not the TS'. When I changed what sub-groups were a part of the main Remote Desktop User group (IE, Domain Users)that seemed to work. So it appears as though a one stop solution isn't available, and I'll have to make the said change to each of my TS' as they join the domain.
I'll try doing it your way though since it would be a more comfortable solution rather than messing with local groups. Thanks for the response, I'll close this question within the next couple of days when I have a final grasp on the solution.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the great help. I apollogize for the delay in awarding you the points, I was away.