L
Lori
We changed Password settings in the Default Domain Policy
by using Terminal Services to the domain controller, then
choosing Default Domain Policy from Administrative Tools.
The policy did not take effect, and that was yesterday
afternoon around 5:00. We found article 269236, which
should take care of the problem because Block Policy
Inheritance is checked on the Domain Controllers
container, but I read documentation that the password
policies set in the Default Domain Policy would always
take affect, even if inheritance is blocked. What I'm
thinking is the Default Domain Policy is linked to the
domain in Active Directory Users and Computers, therefore
the block inheritance is taking effect. If that were
removed from that level -- I thought the Default Domain
Policy would be dynamic enough to not have to be linked
(we only have one domain) -- then the block inheritance
would not block the password settings on the Default
Domain Policy. Any thoughts?
by using Terminal Services to the domain controller, then
choosing Default Domain Policy from Administrative Tools.
The policy did not take effect, and that was yesterday
afternoon around 5:00. We found article 269236, which
should take care of the problem because Block Policy
Inheritance is checked on the Domain Controllers
container, but I read documentation that the password
policies set in the Default Domain Policy would always
take affect, even if inheritance is blocked. What I'm
thinking is the Default Domain Policy is linked to the
domain in Active Directory Users and Computers, therefore
the block inheritance is taking effect. If that were
removed from that level -- I thought the Default Domain
Policy would be dynamic enough to not have to be linked
(we only have one domain) -- then the block inheritance
would not block the password settings on the Default
Domain Policy. Any thoughts?