Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

June 18, 2002 12:00 AM

Access Denied: Using Group Policy to Log Off Users

Windows IT Pro
InstantDoc ID #25419
Rating: (1)

What's the difference between the Automatically log off users when logon time expires and Automatically log off users when logon time expires (Local) Group Policy Object (GPO) settings under \\computer configuration\\windows settings\\security settings\\local policies\\security options? And why don't these policies seem to work consistently? I enabled Automatically log off users when logon time expires in my Default Domain Policy GPO, and the policy appears to be in effect on the local machines, but users remain logged on after their logon times expire. What can I do to get these settings to work properly?

Automatically log off users when logon time expires affects all computers in the domain, but Windows 2000 only looks at this policy in GPOs that are linked to the domain root. The policy has no effect in GPOs that are linked to organizational units (OUs). Automatically log off users when logon time expires (Local) behaves like most GPO policies. When you use a GPO to enable this policy, any computers to which that GPO applies will disconnect users who remain logged on remotely after their logon hours expire. For example, if you enable Automatically log off users when logon time expires (Local) on your File Servers OU, the policy will disconnect all computers in that OU after logon hours expire, but other computers in the domain will remain connected. If you enable or disable Automatically log off users when logon time expires at the domain level, that setting will override any GPOs in which you enabled or disabled Automatically log off users when logon time expires (Local).

Also be aware that these policies disconnect users who are connected over the network from other computers when their logon hours expire—but only if those connections are inactive. For example, Jim's logon hours are between 7:00 a.m. and 9:00 p.m. Jim logs on at 8:00 a.m. from his workstation, maps a drive to server A and another drive to server B, and remains logged on after 9:00 p.m. Jim frequently accesses files on server A but doesn't access server B at all. At 9:00 p.m., server B will disconnect Jim, but server A won't.

Related Content:

ARTICLE TOOLS

Comments
    There are no comments to display. Be the first one!
You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.