I posted this when the Nod rant began late last year. The real issue is that you technically should deploy the software with the realtime disabled, or you risk it doing damage before you can push the config out. I found some ways of editing the xml by hand while building the package to access features not correctly implemented by the config editor, but gave up before I tested this process as v3 wreaked so much havoc here, I likely won't look at it again.
YMMV :) jlc -----Original Message----- From: Andy Ognenoff [mailto:[EMAIL PROTECTED] Sent: Thursday, January 03, 2008 11:12 AM To: NT System Admin Issues Subject: FYI: NOD32 Exclusion Lists Just an FYI for anyone daring enough to use NOD32 v3. I've confirmed with support that the Config Editor DOES NOT correctly write exclusion lists to the XML config file. You have to either manually add the exclusions (for stuff like AD, spools, etc.) on each server or manually add the exclusions on one server, and pull the config back and push it out using RA as long as each server needs the same exclusion list. PIMA... - Andy O. ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
