Domain Group policy software restrictions locked out sbs 2003

I have stupidly applied a domain group policy under software restrictions additional rules that have locked me out of running any programs.

This is true on the server and workstations.

What is the best method to allow access to the active directory group policy to enable me to remove the restriction?
leibholdAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jekautzCommented:
The policies are files store under \\{fqdn}\sysvol\{fqdn}\policies.

You could try to access that folder and delete or rename the policy causing this effect.

Are you able to run Windows Explorer, Command Prompt, Regedit?  Any of these tools could be used to temporarily disable these features.  Since most all group policy settings are stored in the registry, you could delete those settings from the registry, enough to run GPMC.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
leibholdAuthor Commented:
I was able to do a gpedit on the 2008 server to allow local programs to run

Have looked under  \\{fqdn}\sysvol\{fqdn}\policies and removed the file/dir that was last modified today
The gpupdate  comes back with processing group policy failed - unable to read the file .....

I am searching though the files to see what one contains the policy for the software restriction
0
leibholdAuthor Commented:
Hello,
would you like to write this up as a solution?

I took your advice - was able to find the file but  without it being there it would not update ended up

So on another sbs2003 created the default software restrictions policy.
Then opened Registry.pol in note pad on that server

I then copied the contents over the Registry.pol on the affected server in the sysvol  policies {31B2F340-016D-11D2-945F-00C04FB984F9} directory

This appears to have fixed the issue.

Please write the complete solution with your original section and I will award the points.

Thanks you very much for pulling my stupid self out of the fire.
0
jekautzCommented:
I'm glad I could help, but I don't get what you mean by writing up the solution.  If you think my post fixed your problem, then simply mark it as the accepted solution.  That will award the points.

Have a good day.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.