We're getting ready to make a switch across all servers and workstations from Symantec to McAfee, and I've run into some snags in regards to removing existing installations of the Symantec Antivirus client. Our Symantec client was configured to hook into outlook 2000 for E-mail scanning, therefore the application cannot uninstall while outlook is running. I'm thinking about building a condition to check to see if outlook.exe is loaded, and if it is, kill the process before continuing, but I'm not exactly sure how to wrap this around the uninstall. Has anyone else had any great successes or failures removing Symantec Antivirus Client across your enterprise? Any thoughts or suggestions on this would be greatly appreciated!

Kind Regards,
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I think if you did not change the default password from symantec from the corporate edition it will work. The MCafee 8.X Installation with the Framepackage did uninstall Norton CE 8.6 clean and nice without rebooting.
Answered 12/02/2004 by: pharma
Yellow Belt

Please log in to comment
0
Thanks for the reply, pharma.

We were able to kick off the uninstall silently, and it does remove the Symantec Antivirus client, but I'm still running into a situation that if outlook is opened on a workstation when this is performed, it leaves symantec pointers in outlook that can only be removed by running a repair against Microsoft Office, then moving forward with the McAfee installation. When this is done verbosely, it does ask you to close outlook before the uninstall will continue. The silent install process seems to ignore this dependency. So I think what I'm facing is that a completely silent process might not be achievable here, unless there is a way to conditionally kill outlook if it is running.

Any more suggestions are greatly appreciated!! If I uncover anything new, I will make sure to update this post as well.
Answered 12/02/2004 by: Toupeiro
Senior Yellow Belt

Please log in to comment
0
Just a little update.

I think I found a band-aid for this for now until I can find a cleaner way to handle it. I am adding in a custom action to call kill.exe from the resource kit with a -f switch, and pointing it to outlook.exe. It's kind of a rude way to do it, but its the only method I have right now.
Answered 12/03/2004 by: Toupeiro
Senior Yellow Belt

Please log in to comment
0
Do you use McAfee Epolicy Orchestrator?

With this tool you can deploy the ePO agents to your entire network, then create an ePO policy that will remove Symantec's AV and install NAI's AV with your settings defined.

Fairly painless when you let their tools do the work for you.

If you don't have ePO, ignore this post.

hth,
Nate
Answered 12/06/2004 by: nmead
Senior Yellow Belt

Please log in to comment
0
I'm currently midway through an enterprise wide virus agent conversion (Symantec 8.1 to McAfee 8.0i) And using McAfee ePolicy Orchestrator for deployment and policy enforcement. ePO is one of the greatest policy management programs I've ever seen for this type of a solution, but McAfee has left something to be desired in their upgrade from Symantec's client to Mcafee on a windows workstation with Outlook. McAfee is using that NetOp Fead II installer (gag) which has the .MSI encapsulated into it. The ugliness behind that is that there is a temporary file created called uninst.ini which contains the GUID based uninstall of Symantec with the /QN switch. The problem with this in a real world environment is that QN doesn't prompt you for anything, and if Outlook is open, and your symantec installation had the email scanning plugin, be prepared to do repairs and reinstalls of Microsoft Office across your enterprise! I'm working with McAfee support on this right now, but so far I've come up short handed. The other unfortunate part of this is that the McAfee package is registered into ePolicy Orchestrator via a .z proprietary file, therefore simply extracting the MSI won't work if you had planned to use ePO to upgrade current symantec enabled workstations. I'm currently using the Install designer McAfee has, and adding a .reg file to remove the remaining keys in the registry that the uninstall of Symantec AV leaves behind, but I am not sure if this is going to work yet. I attended a 4 day ePO class, to which the instructor couldn't give me an applicable workaround, and told me to call up support. I'll keep an update going in this.
Answered 03/10/2005 by: Toupeiro
Senior Yellow Belt

Please log in to comment
0
I have come up with a fix for this. Takes a couple of steps, but this could save your rollout if you are upgrading from Symantec/Norton enterprise 8.x / 9.x.

The first thing you have to do is get the source out of the FEAD II installer.. So from the commandline, run "setup -nos_ne"

this simply does an extraction of the McAfee sourcefiles to c:\documents and settings\*useraccount*\local settings\temp\Network Associates <*>\

The next step, navigate to that folder and edit the uninst.ini file. Make changes to the following lines:

For Norton 8.x client, Change:
UninstStep2_2=/X{0EFC6259-3AD8-4CD2-BC57-D4937AF5CC0E} /qn REBOOT=R PASSWORDVALID=True

to

UninstStep2_2=/X{0EFC6259-3AD8-4CD2-BC57-D4937AF5CC0E} /qb+! REBOOT=R PASSWORDVALID=True


For Norton 8.x Server, Change:
UninstStep2_2=/X{7D2B86CA-2D5D-469E-92ED-E56B62BD1D3C} /qn REBOOT=R PASSWORDVALID=True

to

UninstStep2_2=/X{7D2B86CA-2D5D-469E-92ED-E56B62BD1D3C} /qb+! REBOOT=R PASSWORDVALID=True


For Norton 9.x, Change

UninstStep2_3=/X{848AC794-8B81-440A-81AE-6474337DB527} /qn REBOOT=R

to

UninstStep2_3=/X{848AC794-8B81-440A-81AE-6474337DB527} /qb+! REBOOT=R

Save and Exit the file.

Next, get Network Associates Installation Designer 8.0.0 (Free when you buy VirusScan 8i)
Walk through the custom installation wizard, tell it you want to make a new installation source based on an existing installation source, and point it to the directory where you extracted the original setup files. Make sure you create your destination directory before telling the installer where to put the newly created install. Make any changes you want to the install, but for best results with their product, make sure you do the enhanced install which requires 256MB of ram. This will recompile the package into a FEAD II self-installer, including the modified uninst.ini, and create a new .z file to check into ePO.

Doing this will put a status bar on the uninstall portion of Norton, but doing so will also pause the install and prompt you to take action if any dependency is open that will break the uninstall and any other product, in this case Microsoft Outlook.

I hope this will help someone else out who is getting ready to encounter the same project.
Answered 03/11/2005 by: Toupeiro
Senior Yellow Belt

Please log in to comment
0
Is the Outlook issue only if outlook is open? Would the normal silent install of McAfee remove Symantec correctly if out look is not open? If this is the case can AD's Software installer be used to deploy McAfee?

Thanks
Answered 03/16/2005 by: brownmatrix
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity