cookie_monster Posted January 20, 2010 Posted January 20, 2010 So were there any exclusions missed or were you not on the latest version? I'm not quite sure what you have and haven't tried. You could try installing NOD and setting it to run a scan each night but turn off active scanning, if it happens again during the day then you can rule out NOD. 1
ICT_GUY Posted January 20, 2010 Author Posted January 20, 2010 Ok, its done. No import feature for the exclusions? May the software engineers at eset suffer with RSI. If Nod32 knackers up my servers again then it will be banished to the cardboard box of shame, along with my collection of windows ME install discs.
cookie_monster Posted January 20, 2010 Posted January 20, 2010 (edited) No no import feature but you can now export the current configuration and import that onto other servers or keep it for future installs. Edited January 20, 2010 by cookie_monster 1
ICT_GUY Posted January 20, 2010 Author Posted January 20, 2010 (edited) Export file is XML, this is the exclusion code, this might be useful to someone in the future. i have not tested this though. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Edited January 20, 2010 by ICT_GUY
ICT_GUY Posted January 20, 2010 Author Posted January 20, 2010 (edited) Part 2 - - - - - - Edited January 20, 2010 by ICT_GUY
ICT_GUY Posted January 20, 2010 Author Posted January 20, 2010 If you put that into will it display better? kind of
steele_uk Posted March 18, 2010 Posted March 18, 2010 How are you guys finding V4 with the exceptions now? I have just been through two weeks of hell with unresponsive DC's. I have just found this post.
ICT_GUY Posted March 19, 2010 Author Posted March 19, 2010 I still have not put it on the main DC My second DC is still slow and not as responsive as it should be. 1
cookie_monster Posted March 19, 2010 Posted March 19, 2010 (edited) Since I set all of the exceptions about three months ago my DC hasn't frozen up at all on V4.0.474.0 You need to set every exclusion that I posted on the last page and follow all of the ESET recommendations as well, limiting scanned extensions turning off email scanning etc. http://kb.eset.com/esetkb/index?page=content&id=SOLN2144 Edited March 19, 2010 by cookie_monster 1
tom84 Posted June 4, 2010 Posted June 4, 2010 Found this thread last night after troubleshooting one of our file servers (2k3 Datacenter). It had been running fine for months until I moved our main fileshare and files across to it, I've been seeing random lockouts at different times in the day. I can telnet to SMB/RDP and ping the guest (it's running under vSphere) but these services are unresponsive. I also can't login via the vSphere console. I've upgraded to nod32 v.4.2.35.0 from 4.0.474.0, followed the exclusions/tweak guide as outlined by NOD32. I'll let you know how I get on...
tom84 Posted June 9, 2010 Posted June 9, 2010 Haven't had the issue since I made the changes above! 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now