Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | FW: Account Lockout Policy |
|---|---|
| Date: | Thu, 20 Oct 2005 10:48:25 -0700 |
You can change the local policy on the machine, or filter a GPO to only apply to that machine. But if they are using the hardcoded local admin, it can't be locked out. MS Safety feature I guess. ---------------------------------------------------------------------- Chris Bates (CISSP) Infrastructure Management Consultant ACS Inc. (Enterprise Services; NWDC) Chris.Bates@nwdc.net -----Original Message----- From: Derick Anderson [mailto:danderson@vikus.com] Sent: Thursday, October 20, 2005 8:59 AM To: Shabbar Arsiwala; focus-ms@securityfocus.com Subject: RE: Account Lockout Policy
-----Original Message----- From: Shabbar Arsiwala [mailto:sarsiwala@obleness.org] Sent: Thursday, October 20, 2005 9:07 AM To: focus-ms@securityfocus.com Subject: Account Lockout Policy -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We have an account lockout policy setup for users on our domain Win 2K3 / Active Directory environment. 4 invalid attempts the account locks out / 30 mins the account is released. We would like to change this policy for one the machines on our domain. This machine uses a local administrator account to log in. Is this possible ??? Thanks, Shabbar
It is possible to change the *local* machine account lockout policy for a specific machine, but not the *domain* lockout policy. To do this you need to put your *domain* password policy in the Domain Controllers OU, create a separate OU for this one machine, make a new policy with the desired lockout settings, and link it to the single machine's OU. This will only work for *local* accounts (such as MACHINE\Administrator), not *domain* accounts (DOMAIN\Administrator). Derick Anderson ------------------------------------------------------------------------ --- ------------------------------------------------------------------------ --- --------------------------------------------------------------------------- ---------------------------------------------------------------------------
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Account Lockout Policy, Laura A. Robinson |
|---|---|
| Next by Date: | RE: Account Lockout Policy, RAMI KHANFER |
| Previous by Thread: | RE: Account Lockout Policy, Derick Anderson |
| Next by Thread: | RE: Account Lockout Policy, Laura A. Robinson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |