gpedit.msc - Locked up even for Administrator

  • Thread starter Thread starter Mailene
  • Start date Start date
M

Mailene

Hi everybody,

I am running (1) Windows 2000 Server with (21) Windows
2000 Pro computers in this location. I have been using
gpedit.msc to lock down each individual computer to a
unique configuration that depends on the user's daily
tasks and level of trust. The computers are restricted of
all configuration changes, just as of they were part of
the Users Group. The reason I just do not set them up as
Restricted Users (Users Group) is because the software
installed in the computers requires a minimum level of
access of Standard Users (Power Users Group).

The reason I am writing is because I have encountered a
major problem with gpedit. It crashed on one of the
stations to the point that not even the local
administrator could open gpedit. My way out of this mess
was to perform a fresh install of the OS.

If anybody know what might have caused gpedit to corrupt
or at least how to fix it if it happens again, I will
appreciate.

Mailene
 
It depends on how it's locked up. Maybe it's the local policy get corrupted.

But if it is NTFS on your drive, then check the security on your folder \windows\system32\GroupPolicy. Reset it to local admin and SYSTEM full control and see if it helps.
 
Try:
cd /d %appdata%\microsoft\mmc
del gpedit

MMC creates preference configuration files for some snap-ins. You can clear
all of these out by launching mmc.exe,
then File->Options, choose the "Disk Cleanup" tab in the dialog, and choose
to "Delete Files."

--
--matthew
-------------------------------------------------------------
Please do not send email directly to the alias used to post to the
newsgroup. The alias is for newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


Denis Wong @ Hong Kong said:
It depends on how it's locked up. Maybe it's the local policy get corrupted.

But if it is NTFS on your drive, then check the security on your folder
Click to expand...
\windows\system32\GroupPolicy. Reset it to local admin and SYSTEM full
control and see if it helps.
 
Back
Top