Policy / Script Problem

Hi We Have the following problem , one of the lab pc's has been configured with a certain policy/ script that kicks the user out of Windows (Even Admin) when logging in . I can luckily get into Windows via Safe Mode


Is there any way that I can get it working correctly again ?

 

Good grief - the lack of detail makes this one a real challange.

- XP-home or XP-Pro?
- Domains/workgroups/other?
- User or domain policy/script?
- Policy or script?

If policy, what sort of policy? Startup/computer policy options I'm aware of (in order they will be applied with last applied taking control):
. NT 4 policy (NTCONFIG.POL)
. Local group policy
. Site group policy
. Domain group policy
(and if 2K AD)
. Organizational unit (OU) group policy
. Child OU group policy

Well, you get the idea. Question is way too vague.

 

Don't Worry

I got it working using System Restore

 

Thanks for letting us know.

 

Newt Just For Reference

- XP-home or XP-Pro?
- Domains/workgroups/other?
- User or domain policy/script?
- Policy or script?

If policy, what sort of policy? Startup/computer policy options I'm aware of (in order they will be applied with last applied taking control):
. NT 4 policy (NTCONFIG.POL)
. Local group policy
. Site group policy
. Domain group policy
(and if 2K AD)
. Organizational unit (OU) group policy
. Child OU group policy

I just want to know for future reference , what it could have been

-XP Pro
-Domain (But the guy who worked on it , was logged in as local admin who ******* it up)
-User Policy (I think)
-Policy or Script : I don't know , but his level of expertise I'd guess he just figured out how to use the local policy , so let's go with Local Policy

-I'm pretty sure it's a local group policy

I think he maybe disabled log in interactively or something . You seem to be an expert , sorry about the vague question , but this is all data I could get out .



Replies Appreciated
djdrastic

 

If "lab" indicates a computer learning/training room of some sort, my best suggestion to you is to get the machines like you want them and then have a system restore run at every start-up.

Then you don't really care what folks do short of breaking the hardware. Especially useful if there will be lots of folks with local admin rights.

The behavior you described could have been done by something as simple as stuffing a logout script into every startup folder. Log on, script runs, logged out.

You might also want to take a look at a well written but badly titled article from M$ that will bring you up to speed on policy things. Here.