Two versions of SEP 11 on same machine.

Jack Wilson's picture

For my first test of RU5, I created an Export Client Install Package and ran that on a client that had MR4 MP2 installed. The install seemed to go ok - no errors, etc.

Today, I noticed that there were two Symantec Endpoint Protections listed in add/remove programs. Running the SEP_SupportTool just complained that SPBBCDrv was not running.

I eventually managed to get rid of both versions, but it took a few hours and a few passes of uninstalls/cleanwipes to do it. The reinstall of SEP11 RU5 went fine after that.

Any idea why this happened?

Jeremy Dundon's picture

I have seen this before

It was on a terminal server and the upgrade was run in a non-admin (non-console) session; Both versions tried to run after the reboot (in my case it was SAV and SEP both, not two versions of SEP).

snekul's picture

Shouldn't the install fail if

Shouldn't the install fail if the user lacks admin rights?

Eric C. Lukens
IT Security Policy and Risk Assessment Analyst
University of Northern Iowa

Jack Wilson's picture

This was XP and on the console.

This was XP and on the console.

ben_cSEPticons_secured's picture

yes if the user doesn't have

yes if the user doesn't have admin rights or even a power user account, then setup will not succeed..

ShadowsPapa's picture

LOL - see my thread on

LOL - see my thread on needing a manual remove process that wasn't a shotgun!
YES, this happened to us on a SERVER, a Windows 2003 R2 32bit server.
The upgrade was via a package assigned to the group.
If you tried to launch SEP, MSI install would start and abort. It complained that Outlook protection couldn't start, however outlook protection wasn't enabled in the group. Several issues I explained in the threads I started yesterday and another I responded to yesterday.
BOTH were in add/remove programs.
There was a mix of file dates and versions - MR4 files were there as were RU5 files.
It was as if it got part way then stopped - leaving a few old files in place, and not updating the MSI install list or add/remove programs.
I DID finally get it solved after HOURS of manual manipulation, doing add/remove and choosing "change" and disabling or removing some minor features one at a time, and at least (NO KIDDING!) 12 reboots, probably more, of a SERVER during the day.....
I could NOT use cleanwipe or the published manual removal methods as we had other Symantec products on that server. They had no process for removing ONLY SEP (baaaad thing) so I was on my own. Took almost all day, but she's done and running.

My guess is that there is a problem with the install from upgrade package assigned to a group - since I've seen this, and you have seen VERY similar (but different) within the first couple of days..............

Personal sites -> http://theamcpages.com and http://antique-engines.com
Shadow: Toy: