Smart Security is different package that contains NOD32, but also includes a firewall client.
Yes, there is a seperate NOD32 3.0 client that is seperate from Smart Security. Also with 3.0, there is a differentiation between Home and Business NOD32. Business NOD32 (for servers) requires a different installer - although the licensing appears to be the same. At least for updates it is. On Jan 30, 2008 12:27 PM, Sam Cayze <[EMAIL PROTECTED]> wrote: > Finally setting this up in my test lab. > > Does NOD32 3 = Smart Security? > > Are they the same? Is there just an 3.0 AntiVirus client that does not > have the Spam Filter and Personal Firewall? (I don't want those > installed, although I do know that I could just disable them...) > > > > > > -----Original Message----- > From: Rod Trent [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 30, 2008 11:16 AM > To: NT System Admin Issues > Subject: RE: FYI (vLite) > > Uh, it's sysprep. There are no environment variables available when > preparing the system for imaging, unless you generate a boot device with > the variables you define. > > -----Original Message----- > From: Ben Scott [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 30, 2008 12:06 PM > To: NT System Admin Issues > Subject: Re: FYI (vLite) > > On Jan 30, 2008 11:41 AM, Rod Trent <[EMAIL PROTECTED]> wrote: > >> It's been possible all along, it's just a lot of things (including > >> Microsoft's own stuff) assume C:\WINDOWS or C: and won't work if you > >> change things. > > > > That's not true. > > It is true. (I can make empty statements, too.) > > > The OS uses a %windir% variable that that points to where the OS files > > > are no matter what directory it is in. > > I'm aware of %WINDIR% and %SystemDrive%, thanks. But there's stuff > that wrongly assumes certain locations. Obviously deficient software, > but there's a lot of that out there, and some of it comes from > Microsoft. > > To pick an example I just saw mention of recently, the docs for the > recent SYSPREP releases say it should be run from C: drive only. > Maybe it might work elsewhere, but Microsoft says C: is the only way to > do it. So maybe you should tell the people maintaining SYSREP about > %SystemDrive%, eh? > > I've encountered random cases like this plenty of times over the > years. The MSKB may "confirm that this is a problem in the Microsoft > products listed", but that doesn't really help you if you're stuck. > > -- Ben > > ~ 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> ~ > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > -- ME2 ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
