I would be more than happy to try those suggestions, but i am totally
unfamiliar with how to perform those operations. Any insight as how to do
them?
Thanks,
Ben
- Show quoted text -
Hi,
I think any one of the suggestions made by Roger would get you back on
track but it comes down to what you wish to do.
Just fix it, or find out what happened and fix it so it never happens
again.
The easiest of the bunch would of course would be to just fix it, and
that is just fine for the most but sometimes root cause is needed.
You mention that you do not remember where you changed the settings so
maybe suggestion A is not the route.
Suggestion B sounds good but that would mean a policy is still around
causing this issue in the first place.
Suggestion C is the easiest UNLESS this is being caused by a policy
higher up than the default domain policy linked to the domain.
If your AD is W2K, you can use a tool called recreatedefpol which will
recreate BOTH default policies...domain and domain controllers.
If you go this route, I would backup your Default domain controllers
policy (as you have not mentioned any errors with this one) to know
all your settings before reverting to default.
If your AD is W2K3, you can run dcgpofix and specify which policy you
wish to revert to default. The domain policy or the default domain
controllers policy.
You have yet to mention how many group policies you have linked at
your domain level.
When you open up GPMC and click on your domain, how many policies are
linked? And which one is sitting with the link order of 1?
Good luck
Harj Singh
Password Policy Done Right
www.specopssoft.com