Avatar of AXISHK
AXISHK
 asked on

Audit account lock on Window 2003 and 2008 DC

http://community.spiceworks.com/how_to/show/11824-email-account-lock-out-notification

Follow the link to audit account lock but it doesn't work.

I have already enabled audit policy under domain password policy and Default domain controller policy to audit " account login" failure event.

We have two domain controllers, Window 2003 and Window 2008. I tried to stimulate a user login failure and find that event 4740 is not logged. Only event 675 is logged in Window 2003. This event corresponded to a stimulated login failure on a workstation.

Any idea ??
Windows Server 2003Windows Server 2008Active Directory

Avatar of undefined
Last Comment
AXISHK

8/22/2022 - Mon
Aard Vark

4740 is the account lockout event for Server 2008 and above. 644 is the lockout event for Server 2003. You would need to trigger on 644 on Server 2003 and 4740 on Server 2008 and Server 2008 R2.

I tried to stimulate a user login failure and find that event 4740 is not logged.
4740 will trigger on a lockout not a bad password attempt.
AXISHK

ASKER
HOW TO MAIL ACcount lockout on window 2003 as it does not have powershell
Aard Vark

You need to install Windows Management framework 2.0 (PowerShell 2).

http://support.microsoft.com/kb/968929

It supports Windows Server 2003 with Service Pack 2 and higher. If you have a lower service pack level you will need to install Windows Management Framework 1.0 (PowerShell 1).
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
Detlef001

Would you be intrested in an third party application if yes please update so as to update you with this,

As this task can be easily with an third party application.

Thanks.
AXISHK

ASKER
Install Powershell on Window 2003 but it seems that there is no trigger event in Window 2003 schedule. Hence, not sure whether I can still use powershell to track the event.

If there is no workaround powershell solution for Window 2003, I can consider 3rd solution. Tks
ASKER CERTIFIED SOLUTION
Aard Vark

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
AXISHK

ASKER
Tks
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.