This has been going on for years and I've just accepted it, but it seems too weird and makes auditing difficult. We have 5 load-balanced terminal servers and 2 connection brokers. Once a week, I audit all 7 servers for event ID 4625. The week that Windows Updates have been staged through our WSUS, I get literally hundreds of 4625 Events on the Connection Brokers. The events pop up 8 at a time within 1 second. The terminal servers themselves don't have any issues.
This is an event from one of the Connection Brokers:
An account failed to log on. Subject: Security ID: NULL SID Account Name: - Account Domain: - Logon ID: 0x0 Logon Type: 3 Account For Which Logon Failed: Security ID: NULL SID Account Name: <CNBRKR COMPUTER NAME> Account Domain: <DOMAIN> Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xc000006d Sub Status: 0xc0000064 Process Information: Caller Process ID: 0x0 Caller Process Name: - Network Information: Workstation Name: <CNBRKR COMPUTER NAME> Source Network Address: fe80::39b9:306b:5224:fd9 Source Port: 62951 Detailed Authentication Information: Logon Process: NtLmSsp Authentication Package: NTLM Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon request fails. It is generated on the computer where access was attempted. The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network). The Process Information fields indicate which account and process on the system requested the logon. The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
After the Windows Updates are installed, the 4625 events go back to normal where my users can't remember their passwords.
Any ideas?