Re: Default Domain password policy issue

Tech-Archive recommends: Fix windows errors by optimizing your registry

So, are you saying that when a domain user logs into a desktop, they are not
required to enter a complex password? Or, is the problem just that you
aren't seeing what you expect to see on a DC?

Darren

--
Darren Mar-Elia
MS-MVP-Windows Server--Group Policy
Check out http://www.gpoguy.com -- The Windows Group Policy Information Hub:
FAQs, Training Videos, Whitepapers and Utilities for all things Group
Policy-related
And, the Windows Group Policy Guide is out from Microsoft Press!!! Check it
out at http://www.microsoft.com/mspress/books/8763.asp
GPOGUY Blog: http://blogs.dirteam.com/blogs/gpoguy



"rb97685" <rb97685@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:00FED3EB-1B1A-4670-BE3D-AD7D9FD85ABA@xxxxxxxxxxxxxxxx
We're having a problem where we have enabled password complexity
requirements
at the Default Domain policy level in our organization. Upon testing, it
looks as if this policy is not being applied to many of our desktops.
Here's
are scenario:

* 2 Domain Controllers (Windows Server 2003)
* Primarily XP desktops

* I logged into one of our domain controllers, ran gpupdate, then opened
up
gpedit.msc. The old, simple password policy appears cached on this
machine.
Settings are grayed out, cannot be changed from the console directly.
* From my client machine, I opened up the GPMC snap-in, connected to both
DCs and reviewed policy settings. Both show as the new settings as having
been applied.
* While connected via GPMC to the DC in question, I changed settings,
applied. The re-applied password complexity.
* Logged back onto DC console, checked gpedit. Old policy is still cached.

Anybody know what is going on here, and how do I get rid of this
apparently
cached policy on this one DC? Thanks


.

Relevant Pages

  • Re: Problem with desktop restrictions
    ... I disabled the domain policy and still have the same issue. ... the settings of the desktops. ... but they can add folders to the drive in windows explorer. ...
    (microsoft.public.windows.group_policy)
  • Re: Problem Saving To Desktop as NON Admin
    ... What is the Group Policy that you had set up and subsequently removed for this new security group? ... > group) save documents and files to their desktops. ... > save things to their Terminal server desktops. ...
    (microsoft.public.windows.terminal_services)
  • Re: Policy loopback causes domain-level policies to reapply
    ... to apply to all the desktops, so why not create the policy as a machine ... > servers and 2000/XP desktops. ... > Our computers are split between the Desktops and Servers OUs, ... > for a handful who are in the "Screensaver Disabled Users" OU. ...
    (microsoft.public.win2000.group_policy)
  • Re: Restricted Groups Not Working
    ... Have you tried running the GPMC's "Group Policy ... Also all machines are running SP2 and with the latest hotfixes as ... are all the machines (desktops and laptops) running XP ...
    (microsoft.public.windows.group_policy)
  • Policy loopback causes domain-level policies to reapply
    ... servers and 2000/XP desktops. ... Domain container ... for a handful who are in the "Screensaver Disabled Users" OU. ... placed the deployment policy under the Desktops OU. ...
    (microsoft.public.win2000.group_policy)