Home > Windows News > Step-by-step guide: Filter to prevent administrator lockouts
Windows News:
EMAIL THIS LICENSING & REPRINTS

Step-by-step guide: Filter to prevent administrator lockouts

By John Heuglin, Windows 2000 and XP instructor
14 Aug 2002 | SearchWindowsManageability

Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   

"Help! I've locked myself out! What can I do?" That's one of the most frequently-asked questions in the SearchWindowsManageability's Ask the Expert mailbox. Don't get smug; it could happen to you.

Picture this: you are in workgroup or stand-alone environment where many users share a computer, and you need to place the computer on "lock down." For example, you want to remove the "Run" command. So, you logon as the Administrator, open the local group policy and make the necessary change to remove the "Run" command. You logoff, and go about your business. A few days later, you logon to the "locked down" computer and notice that you, the Administrator, do not have the "Run" command. How can this be? You are the Administrator, aren't you?

The steps below will work with Windows 2000 and XP to help "filter" the Administrator (or anyone else you choose) from being affected by the local group policy.

  1. Logon as the Administrator

  2. Click START>>>RUN and enter "GPEdit.MSC" – this will open the local group policy.

  3. Configure the appropriate Computer and User settings to "lock down" the machine (i.e. – Remove the Run command).

  4. Close the Policy window.

  5. In Windows Explorer, Right Click on "%systemroot%System32GroupPolicygpt.ini" and select Properties.

  6. Select the Security Tab.

  7. Select the "Administrators" group in the Access Control List (ACL).

  8. Select the "Deny" box for Full Control and select OK

  9. Logoff/Logon as the Administrator

Once this task is completed, the Administrator will no longer be affected by the Local GPO, but all other users will! However, because you have denied yourself permission to read the Local GPO, you cannot edit it the local Group Policy on the fly. You must go back in and uncheck the "Deny" permissions on the gpt.ini file prior to making changes to the local Group Policy.

About the author: John Heuglin is Microsoft Windows XP Professional and Windows 2000 Server Instructor at Louisville Technical Institute in Louisville, Ky. He holds N+, CNE, MCP+I, MCSA, MCSE(NT4/2K) and MCT certifications.

Do you have a Windows management or administration tip or shortcut to contribute to our new Step-by-Step Guide series? Then please send it in to editor@searchwindowsmanageability.com.

MORE ON THIS TOPIC:

Finding a lost password
Securing logins

Tags: Windows ManageabilityVIEW ALL TAGS

Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


HomeNewsTopicsITKnowledge ExchangeTipsAsk the ExpertsWebcastsWhite PapersIT DownloadsBlogs
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Reprints  |  Site Map




All Rights Reserved, Copyright 1999 - 2008, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts