problems with admin account

[nikos]

I have used gpedit to change the rights of some users that
also use my computer (trying to restrict access to
changing settings etc.) but the changes affected the
account with admin rights(belonging to the admin group)
and now I can't change those settings back (even logged as
the administrator) as I don't have access to computer
management, admin tools, control panel and so on (a
message pops up asking me to contact the computer
administrator because the operation I have tried is
restricted) (p.s. I know all the passwords in the
computer).
Please help!

 

[Roger Abell [MVP]]

When outside of a domain group policy is only local policy,
and this affects all accounts equally.
To get out of your present pickle, while logged in as an
admin, go to the Security dialog on system32\GroupPolicy
folder and set a Deny of Full control for Administrators.
Log off and then back in, again as an admin, go to the same
folder and remove the Deny, and then edit the local policy
to remove the restrictions.
Then, consider visiting Doug's site to get his XP Security
console app that allows you to set some values on a
per-account basis.
www.dougknox.com

 

[nikos]

I did as you said but I still can't get access to
gpedit.msc it says that "the snap-in has been restricted
by policy.Contact your administrator for details".

 

[Doug Knox MS-MVP]

As Roger said, my XP Security Console is designed to allow you to put a number of restrictions in place, on a per-user basis.

You'll be able to unlock some of the settings that you've made with GPEDIT, but not all. Post back with what you can't resolve with the Security Console, and we'll assist you from there.

http://www.dougknox.com/xp/utils/xp_securityconsole.htm

 

[Roger Abell [MVP]]

If you carefully follow directions, set the deny on
the folder system32\GroupPolicy, log off and back
in, remove the deny, and then launch Local Security
Policy immediately and change the policy settings
that are causing the restriction on running msc
consoles then the next time you log in (without
having set the deny) you should be back to where
you can normally manage the system.

Where did things fail when you tried?