RE: Vipre and deployment

2010-11-01 Thread Phil Garven
://www.sunbeltsoftware.com Tel: +1 877-757-4094 From: Cameron [mailto:cameron.orl...@gmail.com] Sent: Friday, October 29, 2010 2:08 PM To: NT System Admin Issues Subject: Re: Vipre and deployment Unless the uninstaller has changed, it didn't work very well for us either

Re: Vipre and deployment

2010-10-29 Thread David Minich
Yes Joseph L. Casale jcas...@activenetwerx.com wrote: For you guys with experience using Vipre (I presume it's come a long way by now...) I am curious about a couple things. I gave up on Avira, my first point of support was the var in Canada who proved beyond a shadow of a doubt to be

RE: Vipre and deployment

2010-10-29 Thread Jim Holmgren
410.625.2200 (main) 443.524.8573 (direct) 443-506.2400 (cell) www.xlhealth.com -Original Message- From: David Minich [mailto:dmin...@datamovers.us] Sent: Friday, October 29, 2010 11:49 AM To: NT System Admin Issues Subject: Re: Vipre and deployment Yes Joseph L. Casale jcas

Re: Vipre and deployment

2010-10-29 Thread Eric Wittersheim
You can deploy Vipre as an MSI from the console. I suppose that you can push the MSI with GP if you like. On Fri, Oct 29, 2010 at 10:46 AM, Joseph L. Casale jcas...@activenetwerx.com wrote: For you guys with experience using Vipre (I presume it’s come a long way by now…) I am curious about

RE: Vipre and deployment

2010-10-29 Thread Joseph L. Casale
GPO's... -Original Message- From: Jim Holmgren [mailto:jholmg...@xlhealth.com] Sent: Friday, October 29, 2010 9:52 AM To: NT System Admin Issues Subject: RE: Vipre and deployment Just curious, what is your deployment method? We packaged the Sophos .exe file with SCCM

RE: Vipre and deployment

2010-10-29 Thread Joseph L. Casale
Yea, if I do it with the Console, I need to enable file and print services on the wkst etc... If I use a GPO, I don't. From: Eric Wittersheim [mailto:eric.wittersh...@gmail.com] Sent: Friday, October 29, 2010 9:55 AM To: NT System Admin Issues Subject: Re: Vipre and deployment You can deploy

RE: Vipre and deployment

2010-10-29 Thread Holstrom, Don
...@activenetwerx.com] Sent: Friday, October 29, 2010 11:56 AM To: NT System Admin Issues Subject: RE: Vipre and deployment Yea, if I do it with the Console, I need to enable file and print services on the wkst etc... If I use a GPO, I don't. From: Eric Wittersheim [mailto:eric.wittersh...@gmail.com

RE: Vipre and deployment

2010-10-29 Thread Alex Eckelberry
http://www.sunbeltsoftware.com/Business/Agent-Uninstallers/ From: Holstrom, Don [mailto:dholst...@nbm.org] Sent: Friday, October 29, 2010 12:41 PM To: NT System Admin Issues Subject: RE: Vipre and deployment We still use Symantec on all our workstations. Would love to move over to Vipre. We

Re: Vipre and deployment

2010-10-29 Thread Eric Wittersheim
and deployment Yea, if I do it with the Console, I need to enable file and print services on the wkst etc… If I use a GPO, I don’t. *From:* Eric Wittersheim [mailto:eric.wittersh...@gmail.com] *Sent:* Friday, October 29, 2010 9:55 AM *To:* NT System Admin Issues *Subject:* Re: Vipre

RE: Vipre and deployment

2010-10-29 Thread John Aldrich
29, 2010 12:52 PM To: NT System Admin Issues Subject: RE: Vipre and deployment http://www.sunbeltsoftware.com/Business/Agent-Uninstallers/ From: Holstrom, Don [mailto:dholst...@nbm.org] Sent: Friday, October 29, 2010 12:41 PM To: NT System Admin Issues Subject: RE: Vipre and deployment We

Re: Vipre and deployment

2010-10-29 Thread Cameron
System Admin Issues Subject: RE: Vipre and deployment http://www.sunbeltsoftware.com/Business/Agent-Uninstallers/ From: Holstrom, Don [mailto:dholst...@nbm.org] Sent: Friday, October 29, 2010 12:41 PM To: NT System Admin Issues Subject: RE: Vipre and deployment We still use Symantec

RE: Vipre and deployment

2010-10-29 Thread Don Guyer
mailto:don.gu...@prufoxroach.com From: Cameron [mailto:cameron.orl...@gmail.com] Sent: Friday, October 29, 2010 2:08 PM To: NT System Admin Issues Subject: Re: Vipre and deployment Unless the uninstaller has changed, it didn't work very well for us either with Symantec. It ended up being