We have a Windows Server 2003 server farm used for Terminal services/Citrix. On the authentication side of things/AD we are having a new issue. We audit user logins and disable accounts after three unsuccessful logon attempts. The process works fine on all four of our application servers but only two of them will log it in the event logs. All four servers have their event log and audit settings setup identically. As a matter of fact, we use global policy to dish that out.
Our servers are 01, 02, 03 and 04 for example. If users enter a wrong password three times in succession it will lock their account out. This works on all four servers. But only servers 03 and 04 will log it. 01 and 02 do not log it. This is coupled then with some other issues.
We monitor the event logs for these event ID's so that administrative staff receive an email alert when an account lockout occurs. The problem is we only get alerts from users who happen to lock out on 03 and 04. Since 01 and 02 do not log it the monitor has no event ID to pull and report.
The other issue then that I am sure is related is that since there is no logging of the events on 01 and 02 it appears that AD or global policy is not notified then either. I say this because we have the policy setup to automatically re-enable th users account after two hours. This works for users who locked out on 03 and 04 but users who locked out on 01 and 02 will remain locked indefinitely until they are unlocked administratively.
Any Server 2k3/AD gurus out there care to take a stab at this? We would really appreciate the help.
Mark
Mark
CCEA
Our servers are 01, 02, 03 and 04 for example. If users enter a wrong password three times in succession it will lock their account out. This works on all four servers. But only servers 03 and 04 will log it. 01 and 02 do not log it. This is coupled then with some other issues.
We monitor the event logs for these event ID's so that administrative staff receive an email alert when an account lockout occurs. The problem is we only get alerts from users who happen to lock out on 03 and 04. Since 01 and 02 do not log it the monitor has no event ID to pull and report.
The other issue then that I am sure is related is that since there is no logging of the events on 01 and 02 it appears that AD or global policy is not notified then either. I say this because we have the policy setup to automatically re-enable th users account after two hours. This works for users who locked out on 03 and 04 but users who locked out on 01 and 02 will remain locked indefinitely until they are unlocked administratively.
Any Server 2k3/AD gurus out there care to take a stab at this? We would really appreciate the help.
Mark
Mark
CCEA