• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Trying to setup remote desktop, not working

G

glassvial

Senior member
So here's the situation, Windows Server 2003, trying to setup a user account for remote desktop. I've added the user under "Select Remote Users" and the user account is a member of the Remote User group, yet still cannot logon saying something about terminal services rights, which the Remote User group is supposed to have enabled by default.

The second half of my problem is once I get this user working, they need to have very restricted access to the machine, only able to run 1-2 programs, sign off, and that's IT. Would appreciate suggestions for an easy way to implement this.

TIA
 
Okay, you want to run TS on the 2003 server using RDP client!, correct?, Terminal services have to be installed on the server 1st, the connection manager needs permissions for which ever user group and licencing per user, rather than device should get you sorted.

Edit: just user 'user setting' group policies to lock down the server
 
We're using remote desktop. We can already login with an administrator account just fine, but trying to connect with a limited user account is proving troublesome.
 
Frankly, I don't use straight Server 2003 much. But I wouldn't be surprised if it denies Remote Desktop access to non-Administrators by default. Certainly if it's a Domain Controller, I'd guess that Remote Desktop is denied to non-Administrators. You should be able to change this using Local Policy or Group Policy if it's a Domain Controller. But there's a reason why it's denied. Allowing direct access to a DC is risky.

Remote Desktop on Windows Server is designed for administrative purposes. For non-administrative use, you normally install the Terminal Server component and pay the $100/user TS license CAL fees.
 
What you're looking for should be in your Local Security Settings under Local Policies -> User Rights Assignment.

I'm not exactly sure what it's labeled but It shouldn't be too hard to find. You can find the Local Security Settings in the control panel under Administrative Tools.
 
Originally posted by: Astray
What you're looking for should be in your Local Security Settings under Local Policies -> User Rights Assignment.

I'm not exactly sure what it's labeled but It shouldn't be too hard to find. You can find the Local Security Settings in the control panel under Administrative Tools.
Click to expand...
Yeah I tried adding the user to "Allow log on through terminal services" and it still doesn't work, says I need to add the user to the allow logon through terminal services, which doesn't make sense to me.
 
And yes this is a domain controller, but in a very small office and they only need 1 remote user who will only be logged on a few times a week.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top