Undue gpedit settings

[Brian]

I was "playing" with gpedit the other night. I was experimenting
making a very restricted account on this computer, and basically
disabled a lot of stuff and the only program that is authorized to run
is IE. Well, those settings under "user" were applied to all users,
even the machine Administrator account, and so now I can not run
gpedit again to undue them. I'm just wondering if there are any ways
to fix it, before I reload this computer. It's not a big deal as this
computer isn't a main computer, I'm merely curious.

Thanks for any information.

Brian

 

[Carey Frisch [MVP]]

"Snap-in Failed to Initialize" Error Message When You Open Microsoft Management Console
http://support.microsoft.com/default.aspx?scid=kb;en-us;826282&Product=winxp

Visit http://www.kellys-korner-xp.com/xp_tweaks.htm and scroll way down
to Item No. 296 titled: "Lift MMC/GPEDIT Snap-In Restrictions".

[Courtesy of MS-MVP Kelly Theriot]

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect your PC!
http://www.microsoft.com/security/protect/

----------------------------------------------------------------------------------


|I was "playing" with gpedit the other night. I was experimenting
| making a very restricted account on this computer, and basically
| disabled a lot of stuff and the only program that is authorized to run
| is IE. Well, those settings under "user" were applied to all users,
| even the machine Administrator account, and so now I can not run
| gpedit again to undue them. I'm just wondering if there are any ways
| to fix it, before I reload this computer. It's not a big deal as this
| computer isn't a main computer, I'm merely curious.
|
| Thanks for any information.
|
| Brian

 

[Brian]

Thanks for your response. Like always, I found some helpful
information that I used to get fixed shortly after my post. I found
you can deny the Administrator read/write access to gpt.ini under the
C:\WINDOWS\system32\GroupPolicy folder to prevent the policies from
being applied when the account is logging on. However, doing that
prevented me from using gpedit.msc again (which might just be a good
thing). To get around all of this I simply renamed gpt.ini to
gpt_old.ini and then logged off/on and presto... the policies weren't
applied, and Windows created a new gpt.ini file for me and I could run
gpedit.msc again.