Re: Changes to Password Policy did not update?

So you're saying that the changes in A reflect on B domain? That isn't possible...
Check if you're editing the correct domain.
Did you created a new domain policy or edit the Default Domain Policy?
Also check the policy higher priority.

--
*************************************************
I hope that the information above helps you
Good Luck

Jorge Silva

MCSA + Exchange + MSCE
*************************************************

"rlk" <rlk@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:446C3F25-E540-4AF2-9BA4-9AF5FD75A764@xxxxxxxxxxxxxxxx
it was made at a domain level. We applied it first to the first child domain
(A) the beginning of November. Today we were applying it to the 2nd child
domain (B). To make sure things were consistant we checked on (A) and found
none of the changes were updated. When we looked at (B) we found that the
expiration date changed from 42 days to 140 days - but we did not make any
changes in (B). So we are at a loss.

Thank You In Advance


"Jorge Silva" wrote:

Hi
Different Password req. is one of the reasons commonly used to create
multiple domains, you need to create or change a Password policy at the
Domain level.

--
*************************************************
I hope that the information above helps you
Good Luck

Jorge Silva

MCSA + Exchange + MSCE
*************************************************

"rlk" <rlk@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C3344D87-78A7-44EF-84EE-10168740E0B5@xxxxxxxxxxxxxxxx
> Hi - we have a root and 2 child domains. We applied to one of the > child
> domains a new password policy. The policy increased the expiration > date
> from
> 42 days to 140 days and also changed the complexity and not able to > repeat
> the password. However no changes were made to that domain.
>
> When we went in to change the 2nd child domain we found that the
> expiration
> the expiration increased to the 140 days. However on the first domian
> none
> of the policy changes updated and it was still set at 42 day > expiration,
> no
> complexity everything else was disabled.
>
> If anyone has any ideas it would be greatly appreciated.
>
> We are in a window 2000 environment at the moment.
> -- > Thank You In Advance



.

Relevant Pages

  • Re: 2003 Domain Password Policy with NT 4.0 Workstations
    ... The only way to exclude users from adhering to the domain password policy is ... > running Windows NT 4.0, so would the following scenario work? ... Modify the Default Domain Policy and remove the Account ...
    (microsoft.public.windows.server.active_directory)
  • Re: Reasons and examples for security
    ... > One thing that is totally unneeded but which would facilitate ... > is if there were some champion in MS to take up getting a ... > mod to the gina so that there were a password policy to ... > on length minimum and relationship with complexity policy). ...
    (microsoft.public.security)
  • Re: Re: Turn off "prompt user to change password"
    ... Alter when Windows NT displays the Password expiration warining. ... in the default domain policy. ... I'm wanting to turn off the setting that prompts users to change their ... Windows Server MVP ...
    (microsoft.public.windows.group_policy)
  • Re: GPO configuration
    ... > There natively is no possible way to override/bypass domain password policy ... > GPO's for password/account policy. ... >> does an account/password policy applied at the domain level override OU ... I thought the lower GPO policies would overwrite the upper levels ...
    (microsoft.public.cert.exam.mcse)
  • Re: Domain password expiration reset
    ... Basically setting the policy sets an attribute on the domain NC Head object ... chop it down by a few more days and slowly expire everyone and get them reset. ... >>So if you have someone with a password age of 80 days and you set a policy of 90 ... how do you reset the password expiration ...
    (microsoft.public.windows.server.active_directory)