Account Lockout threshold

From: ikbea (ikbea_at_discussions.microsoft.com)
Date: 06/13/05

  • Next message: ikbea: "RE: Account Lockout threshold" 
    Date: Sun, 12 Jun 2005 20:31:03 -0700

    Three domain controller: one primary and two backup
    Member servers (joined same DC) : MServer1, MServer2
    All are windows 2000 SP3 servers

    I want to set account policy in MServer1 and MServer2:
    Account Lockout duration: Not defined (original) --> 30minutes (new)
    Account Lockout threshold: 0 (original) --> 5 (new) invalid logon attempts
    Reset account lockout counter after: Not defined (original) --> 30minutes
    (new)

    In MServer, all settings were changed as I expected.
    However, for MServer2, in "local policy settings --> account lockout
    threshold", the local setting = 5, the effective setting = 0.

    In DC, the
    "Domain Controoler Security Policy", "Domain Security Policy" and "Local
    Security Policy", the effective setting = not defined

    I tried to change MServer2 account lockout threshold to 5 in "Local
    Sercurity Policy", "MMC-->Group policy" and "MMC-->Security Configuration and
    Analysis", but the effective setting is still = 0

    How to set account lockout threshold to 5 in MServer2?

  • Next message: ikbea: "RE: Account Lockout threshold"

    Relevant Pages

    • Re: GPO causing client security logs to fill?
      ... Enabled Small Business Server Remote Assistance Policy No ... Default Domain Controller policy should not be linked to the domain ... thread titled "Client Logon Failure". ... So basically, the Account lockout threshold, account lockout ...
      (microsoft.public.windows.server.sbs)
    • Re: LAN Manager authentication level
      ... If you want to apply lan manager authentication level setting to domain ... domain controllers then configure it in Domain Controller Security Policy. ... users including account lockout must be configured at the domain level. ...
      (microsoft.public.win2000.group_policy)
    • RE: Domain Security Policy change
      ... If you look at the application log on your domain controller are there ... ensure that this policy is being set in the Default Domain Policy ... password settings can only be set at the domain level and are only enforced ... setting the account lockout to 3 bad attempts may cause ...
      (microsoft.public.windows.server.active_directory)
    • Re: GPO causing client security logs to fill?
      ... titled "Client Logon Failure". ... This was done in the Group Policy ... So basically, the Account lockout threshold, account lockout duration ... When you do clean boot on the client computer, ...
      (microsoft.public.windows.server.sbs)
    • Re: GPO causing client security logs to fill?
      ... titled "Client Logon Failure". ... This was done in the Group Policy ... So basically, the Account lockout threshold, account lockout duration ... When you do clean boot on the client computer, ...
      (microsoft.public.windows.server.sbs)
    Loading