Comments
-
I think I found the issue. There was a second unnamed filter that I didn't notice. This filter was a counter filter This event is generated by the Domain Controller that logged the event, as well as the PDC, so this filter was added to prevent double alerts for the same event. Still testing, but I will report back with…
-
Also missing: System.DirectoryServices.AccountManagement System.DirectoryServices.Protocols
-
Feature Request submitted: thwack.solarwinds.com/.../syslog-server-ng---add-full-net-8-framework-support-for-scripting
-
I have discovered a couple things: (1) a workaround and (2) where the DLLs are loaded by the service The Workaround I'm not sure how reliable this is, so I'm going to watch the logs I'm having the script generate to see if it continues to run as expected. Here is what I did: 1. Drop the DLL in the service directory (…
-
As suspected, simply dropping the DLL in the service directory did not work. Likely because the application was not compiled with that DLL in the reference list, so the it doesn't know to try and load it. After further examination, I determined that the DLLs in the service directory are versioned with versions that ship…
-
Thanks @"jholmes" . I ended up also asking the support tech for the open case. He confirmed the same.
-
Have you tried using DNS resolution to see if the FQDN is shown? It almost acts like it is converting it to a decimal representation of an IP address (but the number is too small - 35764 = 0.0.139.180). I use $Message.MsgHost for emails, but I have DNS resolution turned on and it enters the FQDN of the system. Eric
