OMG, heh, many areas. The official report from Level 2 Tech is to push it out unconfigured, it's so broke. I honestly was so frustrated with the release I went back. I don't know what functional improvements exist in v3, but it broke so much stuff. I am not sure what the release really provides over v2.7.
jlc -----Original Message----- From: Andy Ognenoff [mailto:[EMAIL PROTECTED] Sent: Thursday, January 03, 2008 3:32 PM To: NT System Admin Issues Subject: RE: NOD32 Exclusion Lists I remember you posting about the config editor but I didn't realize it was about exclusion lists - I wasn't that far into my implementation so I probably skipped over it. :) Have you found other areas where the config editor doesn't push the correct settings? I just updated to the latest build and haven't seen anything else, but who knows. <rant> One thing that REALLY bugs me is that if you deploy settings via a config file, like disabling real-time protection, email protection, or the http scanning piece, everything reports as being fine. If you even go into the client manually and click the OK button - not even changing a setting - it will start reporting that something is misconfigured and is not providing protection. The fix is to pull back the manually edited config and then turn around and push it back out - apparently they assume if you used the config editor you know what you're doing but if you configure on the client directly, you're clueless and need to be reminded of that. </rant> - Andy O. >-----Original Message----- >From: Joseph L. Casale [mailto:[EMAIL PROTECTED] >Sent: Thursday, January 03, 2008 4:17 PM >To: NT System Admin Issues >Subject: RE: NOD32 Exclusion Lists > >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. ~ 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> ~
