Default Domain Policy not linked to domain

  • Thread starter Thread starter B Parker
  • Start date Start date
B

B Parker

Our "Default Domain Policy" is not linked to the domain, in fact it is not
linked anywhere. Will this policy still take effect if it is not linked?
Also, our domain password policy is still applying, but when I make a change
to it in the Default Domain Policy GPO, the change doesn't seem to take
effect. Is there somewhere else that this may be getting defined?

Any ideas? I'm hesitant to just re-link it to the domain, as I'm not sure if
there was a reason that it was un-linked in the first place.

Thanks,
Brian
 
If you download the gpresult utility and run it on one of your workstations
it will tell you whether the group policy is being applied or not.

Thanks
 
The policy is not being applied. I'm curious though as to where the password
policy is coming from
 
The Password Policy is a domain wide policy, and it will only take effect
when it's defined at domain level.

Meanwhile, it's not restricted to the Default Domain Policy, any user
defined GPO which is linked to the domain will also take effect. However,
only the one with top priority will be the working one, that is, it should
be at the 1st position if there are multiple GPOs.

The Default Domain Policy will always sync its password settings to the 1st
position user defined GPO.

It's highly recommended that you should never un-link the Default domain
Policy to the domain.

Regards,

-Alex
 
The Default Domain Policy was unlinked prior to my working with group policy
in our domain. What I have found now is that if I change the password policy
in USRMGR under Policies > Account, the change takes effect. We have two
Win2k domain controllers and one WinNT domain controller, and we are
currently in mixed mode. Would this have anything to do with it?

Thanks for the help,
Brian
 
Back
Top