Printer_Maestro Logon/logoff Filling Security Logs
We have a 20 printer license with about 6 computers having bartender installed and I believe each has Printer_Maestro installed on it. Looking at each of our machines, the 20mb limit on the Windows Security Event log is completely full of Logon/Logoff events. It's writing to the security log so fast that it's only holding about 13h worth of data, for a total of 37215 events. That's about 47 events written a minute on each of the machines.
My Questions:
Whats going on that's causing this?
What can I do to stop it?
-
I'm having the same issue with Even 4625, but I didn't see a resolution on this thread.
0 -
I'm having the same issue with security logs filling up with:
An account was successfully logged on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0Logon Information:
Logon Type: 3
Restricted Admin Mode: -
Virtual Account: No
Elevated Token: NoImpersonation Level: Impersonation
New Logon:
Security ID: MyPCName\$Printer_Maestro$
Account Name: $Printer_Maestro$
Account Domain: MyPCName
Logon ID: 0x6309779
Linked Logon ID: 0x0
Network Account Name: -
Network Account Domain: -
Logon GUID: {00000000-0000-0000-0000-000000000000}Process Information:
Process ID: 0x0
Process Name: -Network Information:
Workstation Name: {different computer names on network show up here in different event entries}
Source Network Address: -
Source Port: -Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): NTLM V2
Key Length: 128This event is generated when a logon session is created. It is generated on the computer that was accessed.
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 occurred. The most common types are 2 (interactive) and 3 (network).
The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The impersonation level field indicates the extent to which a process in the logon session can impersonate.
The authentication information fields provide detailed information about this specific logon request.
- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
- 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.0 -
Was this ever solved? we are experiencing the same issue. Regards Ed
0
Iniciar sesión para dejar un comentario.
Comentarios
3 comentarios