DiPersiaTech

Old post, but did you ever find an API that we could use? Looking at the same thing myself.

Any updates on this? Just updated from ERA 6.5 to SMC 7.0.577.0. Same error when running the MSI to update the agent (Because the tasks are so hit or miss for us) - ERROR: (preps) Preparing of service failed.

Frank - no resolution yet. I DO have an idea though - the next machine we get in with Norton Internet Security, I'm going to run Process Monitor while I run the Norton Removal Tool and see if that gives me any indication as to what's happening. I'm expecting it to be a nightmare though as I'm sure the removal tool checks a multitude of registry entries and files, so weeding through it will be a joy. Too bad ESET can't say what specifically it found in the install log.

Thanks, Chad - but we've been over these machines with a fine tooth comb. Spent hours looking at the drive, registry, etc. We've even captured an image of the machine BEFORE we run the Norton Removal Tool and an image after and compared them. Nothing jumps out at us. Would be GREAT if you guys noted in the install log WHAT tripped the installer up. It does tell us Norton Internet Security, but a reference to what specifically would be outstanding.

Thanks. As an aside, would be REALLY helpful if we could see the list of items you guys look for during install for conflicting apps. Or include in the install log file exactly WHAT was found as a conflict (As opposed to just the app name.)

Great, thanks!

Aryeh - was hoping to hear something back from you guys. . . Anything?

Aryeh, Just sent you a PM with the files in my Dropbox. Hoping your engineers can tell us something good. Thanks!!! --Pat

The Norton uninstall tool does work for us. Just not well when we have to do it 200x manually. It would be nice if ESET could tell us via a log or tool or something WHAT it is detecting so we can script a cleanup. EVERY Lenovo that we deploy now has this and doing 200+ machines in the field isn't fun. Never found anything in terms of the sysinspector results. Ran a sysinspector before and after the Norton uninstaller and did a compare and nothing helpful.

So the ESET installer is actually checking the specific rights on registry keys to determine if a Symantec product is installed? I find that hard to believe. . .

So it appears more and more machines are coming with Norton Internet Security on them out of the box. We always uninstall it through add/remove programs, and always tell it to take all traces along with it. Problem is, ESET still detects it and won't install unless we run the Norton Removal Tool. Problem is, we're migrating ~200 machines to ESET (via script) and keep running into this. There's no automated way to run the Norton Removal Tool. So we spent hours pouring over a machine in question. Not one thing on the hard drive we can find reference Norton, Symantec, etc. Also did the same in the registry. Finally did a snapshot of the registry and hard drive before and after running the removal tool and still can't find anything being cleaned up. But ESET always installs fine after we run the tool. Any ideas? Is there some kind of "definition" file that we can look at to see what ESET actually looks for when it comes to conflicting apps?

Would prefer to use the notification manager inside of ERA instead of relying on the clients themselves to send notifications.

We've been using ERA forever and have some basic notifications setup. It wasn't until a virus hit a machine yesterday and we didn't get any alerts that I realized we had no working notification for threats. So I setup a new notification and it appeared what looked best to me was a "Received Log Event" against the threats log for critical warnings. The system in question with the virus has a myriad of critical warnings (And still does as we're cleaning it up.) But I'm not getting any notifications. Is there a better way to do this?