Security Settings are made then revert back?

  • Thread starter Thread starter Darryl
  • Start date Start date
D

Darryl

Hi,

I have made a number of changes to the following area

Computer Configuration, Windows Settings, Security Settings, Account
Policies, Password Polices

Then the keys are
Enforce Password History
Maximum password age
Minimum password age
etc

But after applying the changes they keep reverting back to the default
settings. Anyone got any ideas as to why?


Thanks,
 
In what GPO are you changing these settings in? Do you have any other
domain level GPOs defined with these settings?

N
 
Hi,

We have our organisation split into various OU with different Domain
Policies for each. Each OU ahs two Domain Policies one for general settings
(which is common to all OU) and a seperate Domain Policy for Office XP, so I
can set their File Locations for each department within Word & Excel But it
would appear that all the security settings revert back.


Many thanks,
Darryl
 
One problem you will run into is that password policy can only affect domain
accounts when it is set at the domain level OU, not in sub-OUs under it.
For example, if you set password policy in the default domain controllers
policy, you won't see those changes affect your domain users. If you set it
in the default domain policy though, you'll see the settings affect the
users.

With that said, when you say revert back, do you mean the new settings don't
apply to the users (as expected) or that the settings in the security policy
for those OUs actually revert to some default value? Do all of the OU GPOs
revert back to the same settings? Do your domain level GPOs revert back to
some previous value? Are there any settings other than password policy that
you have seen revert back?

N

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
 
Hi Nick,

I have set the changes on sub-ou containers not at the top level. What I
meant by revert back, is that the expiry reverts back to the default 42 days
and not the 30 days as is agreed policy here. So I do not see any of my
changes, this is as you say becuases I have applied this on a sub-containers
and not at the top level.


Many thanks for your help,
 
Back
Top