Has anyone done any work on trying to integrate NOD32 with Kaseya at all? Since it appears NOD32 doesn't drop anything into event logs, we're not able to capture any info/warnings through Kaseya. We have SMTP setup on all clients at least. . . Here's an issue we ran into. We didn't realize that NOD32 wasn't updating properly at the mirror, nor any of the clients. Someone pushed out a new config file to ALL machines, including the mirror, which caused that to break. But none of the clients complained because they were in sync with the mirror. We came from a Symantec background, and there used to be a file in Symantec in plain text that we would query for a particular string that held the definition date. Then we'd check the date and if it was greater than 7 days old, we'd throw a flag in Kaseya and get notified. I found the upd.ver file in Program Files\Eset\updfiles, and saw under [ENGINE2] that it displayed the most recent definitions. Anyone know how this file is put together and if we can accurately report on this information from clients?