Q

Setting user permissions on non-domain controllers

I have been trying for two days to find a place to set user permissions and restrictions on a Windows 2000 Terminal Services system that is NOT a domain controller. The system is on a Windows 2000 domain, but the policies for non-domain controller computers don't have any Terminal Services settings available. I also can't find the settings locally on the machine itself. I DO have the settings I want in the domain controllers policies -- I just can't find them for non-domain controllers. Specifically, I want to set the options relating to inactive sessions and how they should be handled.
The settings you're looking for can be defined on either a per-user or per-protocol basis. To define them for all users of a particular protocol, open Terminal Services Configuration and open the properties for the protocol-say, RDP. Turn to the Sessions tab, choose to override the client-defined settings, and choose the options you want for session timeouts and disconnects. To define these settings for individual users, turn to the Sessions tab in their user account properties. In Windows 2000, you can't define these settings for groups or OUs, so it's easier to define settings for all users of a particular protocol.
This was first published in November 2003

Dig deeper on User passwords and network permissions

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

SearchVirtualDesktop

SearchWindowsServer

SearchExchange

Close