Question, are you sure you upgraded to the right version of Vipre for your key? If you upgraded to Vipre Enterprise premium, then your key will not work and it will display the problems you are having as that is an upgrade from the previous version (aka, new firewall support). You need to download the Vipre Enterprise (non-premium) and it should work with your old key. (Just throwing this out there just in case).
Also, what we found that seems to work pretty well is we built up a new server, and on the old one we updated our policy's to point to the new server. All the clients have moved over, and we can now start the upgrade process and we still have a fail back if needed. Once we're done we'll decom the old vm. -Greg -----Original Message----- From: Todd Lemmiksoo [mailto:[email protected]] Sent: Tuesday, March 09, 2010 10:28 AM To: NT System Admin Issues Subject: RE: VIPRE 4 Enterprise For #3 You will need to limit the SQL memory to 1 GB, will allow the OS to function better. Todd Lemmiksoo -----Original Message----- From: Phil Brutsche [mailto:[email protected]] Sent: Tuesday, March 09, 2010 1:00 PM To: NT System Admin Issues Subject: Re: VIPRE 4 Enterprise For #2: The remote console works fine. If you're having trouble connecting with the console it's probably because of an SQL service configuration issue - the remote console talks directly to the SQL engine and not the VSS. I had to configure SQL Express to listen for connections on the ethernet interface rather than just on the loopback. For #3 It works fine on non-R2 2003. The VSS makes *heavy* use of MSSQL, and if you've "only" got 2GB in the machine you could be running into memory shortage issues. In my setup the SQL Express instance VIPRE is using is currently sitting at 1.4GB of memory, even though the VIPRE DB itself is well under 100MB. Granted, the SQL instance hasn't been restarted since the upgrade; it'll be interesting to see what it does after the reboot for today's patches. [email protected] wrote: > 2. I am currently needing to work off the server console. In previous > VIPRE versions, I could install the console on my desktop machine, > point it to the VIPRE server, and then I could manage everything from there. > No such luck with V4! I simply cannot connect to the "site > database", the server, or much of anything else. > > 3. I do not have a "spare" copy of R2. My server, which was fine for > V3.1 (2 Gb RAM) is painfully slow to do much of anything. The > slowness could be related to either or both of these. > > I've been using the beta versions of Home Premium since November, and it > has been pretty sweet! This "Enterprise" version, though, :-@ -- Phil Brutsche [email protected] ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
