Windows 2000 Terminal Services on a domain controller returns “The local policy of this system does not allow you to log on interactively.” Users cannot connect, but administrators can. Which user right must you grant to allow users to connect to the Terminal server?

Difficulty: Easy

Correct Answer: Grant users the right to log on locally

Explanation:


Introduction / Context:
On Windows 2000, Terminal Services in application mode on a domain controller enforces local security policies strictly. The error “does not allow you to log on interactively” indicates users lack a required logon right. Admins often can connect because they already possess the needed rights via built-in groups.


Given Data / Assumptions:

  • Terminal Services installed on a domain controller.
  • Users receive the interactive logon policy error; administrators can connect.
  • Goal: enable user connections securely via policy.


Concept / Approach:
In Windows 2000, Terminal Services connections check the “Log on locally” user right on domain controllers (later systems add a distinct “Allow log on through Terminal Services” right). Granting this right to an appropriate group (e.g., a TS Users group) enables non-admin users to log on via Terminal Services. “Log on as a service” applies to running services, not interactive sessions. “Log on over the network” affects network access to shares, not console/TS logons. Copying profiles or home folders does not change policy rights.


Step-by-Step Solution:
1) Open Domain Controller Security Policy or Local Security Policy (on the DC hosting TS).2) Navigate to Local Policies → User Rights Assignment.3) Add the appropriate user group to “Log on locally.”4) Force policy update (secedit /refreshpolicy or reboot) and test a user connection.


Verification / Alternative check:
Attempt a Terminal Services logon using a test user from the granted group; the session should establish successfully without policy denials in the Security log.


Why Other Options Are Wrong:

  • Log on as a service: For service accounts only.
  • Log on over the network: Governs SMB/RPC access, not TS interactive sessions.
  • Copy profiles/home folders: Storage changes do not grant logon rights.


Common Pitfalls:
Granting overly broad rights (e.g., Everyone) on a domain controller; failing to scope the right to a specific group of TS users.


Final Answer:
Grant users the right to log on locally

More Questions from Windows 2000 Server

Discussion & Comments

No comments yet. Be the first to comment!
Join Discussion