*Bump* Anyone.. We have spoken with our local distro for nod32 & our area rep from eset.. Still no resolution....
We currently have this issue on multiple sites, (nod32, exchange, mailmarshal 6.1 & 6.2-current versions) Current & old versions of Nod32...
2x 2K3 R2 STD, Exchange 6.5SP2, latest patches from MS Nod32 2.5.26 Xmon 2.51.15 Amon set to exclude Exchange runtime & datastores. 5x...
Workin' good.. good work eset.... :) 7 servers updated... no further issues.. passed infected files through the exchange, picked up and cleaned..
Well, yes.. It would be nice.. But, I'm still happy.... Ever tried to get help from Symantec or Mcaffee? ...... I highly doubt you'll get reply...
To be honest... Eset have been very quick to respond and rather helpful, Having recently changed from another vendor and not having had to deal...
We had the above dirs excluded from the Amon on our sites, the issue still occured... Only solution i found to work 100% was to disable Xmon....
We have had the same issue across about 5 or so sites, sadly.. best you can do is disable Xmon, I have contacted our local distro for nod32.. and...
Separate names with a comma.