Allow user remote access windows server 2008

It gave me the message. The local policy of this system does not permit you to logon interactively. Adding a user to the remote desktop group in ad on a domain worked with no problems. I am thinking there are extra steps that must be taken when dealing with a r2 domain. Best Answer. Had to add the domain group remote desktop users to the allow logon locally group.

View this "Best Answer" in the replies below ». We do not want this user account to have administrator rights. Astral Apr 16, at UTC. That is helpful for other applications but not for this one. This setting is Enabled and Grayed Out on Clients. But cant get back to the previous settings.

If i Disable, it is disabled and the Option is Grayed Out, so it can not be changed. If i Enable, it is enabled and Grayed out. Are you logged in as Administrator on the Client? Because otherwise you cannot change this setting and it is correctly displayed as grayed out. So if you want to disable it - set so in the policy. If enabled then enabled. Either way on the client, as long as you are not logged in as admin it will be dimmed. The fDenyTSConnections is there and has value " 0 ".

I manually deleted this registry Entry, then i was able to change the value of "Allow users to connect remotely". But as soon i update the group policy, it is again dimmed out. The behavior you mentioned in 2. Now, you know the GPO name in which the policy is configured from the rsop. It should solve the issue. That is what exactly the problem is, The policy is not enabled, it is set to " Not Configured ". But it is behaving like it is Enabled. Office Office Exchange Server. Not an IT pro?

Sign in. Remote Desktop lets users control their desktop computer remotely. Until Microsoft Windows Server , the network connection itself has been the biggest challenge. Your private network probably uses private Internet Protocol addresses, which prevent users from connecting directly to their desktop computers from the Internet. Even if you offered users a virtual private network connection, many firewalls block VPNs. To work around these limits, Windows Server introduces the Terminal Services TS Gateway role, which acts as a proxy server between the Internet and your internal network.

The TS Gateway authenticates the user via either a password or a smart card , verifies that the user is authorized to connect to the destination computer and then uses Remote Desktop Protocol RDP to complete the connection on your private network. To configure the Remote Desktop Client, follow these steps:. To connect to the server, open the RDP file, and click Connect.