Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

SEP - Package Installation (SAV related)

Updated: 04 Oct 2010 | 9 comments
Khue's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

I noticed today, that after deploying SEP to replace SAV, the SAV folder still remains on the computers that SEP is deployed to. I've browsed the computers services and there doesn't seem to be anything left that runs executables from the SAV folder. I do see services that run from the SEP folder. Is this a normal behavior? To still have a large portion of the SAV folder remaining after deploying to the machines? Is this perhaps the result of a specific method I used to upgrade these machines from SAV to SEP?

Thanks in advance.

Comments

Vikram Kumar-SAV to SEP's picture
01
Sep
2010
0 Votes 0
Login to vote

Thats perfectly normal

Thats perfectly normal behaviour.. SEP gets installed in SAV folder.when migrated from SAV to EP

Khue's picture
01
Sep
2010
0 Votes 0
Login to vote

For some reason on a few

For some reason on a few machines, I can still bring up the old 10.1.6 console. The Symantec Antivirus and Symantec Endpoint Protection are both in the program files group from the start menu.

Vikram Kumar-SAV to SEP's picture
01
Sep
2010
0 Votes 0
Login to vote

Well..then thats not

Well..then thats not normal..on those machines you need remove both and then install SEP fresh..
Whenever you upgrade from SAV to SEP there are always few machines which won't upgrade as expected..for them you can use Cleanwipe then deploy SEP again
However number of these machines will be very less

Brian81's picture
01
Sep
2010
0 Votes 0
Login to vote

I've hit this issue on many

I've hit this issue on many machines. I usually end up running cleanwipe to do a full removal then re-install SEP. Not ideal but usually quick and easy.

VKalani's picture
01
Sep
2010
0 Votes 0
Login to vote

That is very  strange....you

That is very  strange....you would have to uninstall both , and then re-install SEP. This time, because it would be a fresh install( an not an upgrade  from SAV), you would see that it is installed in the  folder: C?program files/Symantec/Symantec Endpoint protection.

-VKalani

Khue's picture
03
Sep
2010
0 Votes 0
Login to vote

Sorry for the long delay in

Sorry for the long delay in updates on this. It's interesting. SEP always installs but on these few machines, its like SAV is still available to be active... but it isn't. The other weird issue is that SAV is not available from the Add/Remove Programs listing. I will continue to work through this. For now, the SEP installs seem to be 100% ok. They are recieving daily updates and the scanning technology seems to be spot on when check with the eicar test string. 

sandra.g's picture
03
Sep
2010
0 Votes 0
Login to vote

What is the OS that most

What is the OS that most seems to be affected, what's the SEP build, and what is your method of deployment?  Your description reminds me of this:

Title: 'Client deployment to Vista machine results in both Symantec AntiVirus and Symantec Endpoint Protection to be installed simultaneously'
http://service1.symantec.com/SUPPORT/ent-security....

(This document refers to SCSCleanwipe--which is just Cleanwipe now :) )

Let us know if you see a "value 3" in the installation log (%temp%\SEP_INST.log).

sandra

Symantec Technical Support Engineer, LAM/NAM //  SAV/SEP for Mac
Don't forget to mark your thread as 'solved' with the answer that best helped you!
 

Khue's picture
03
Sep
2010
0 Votes 0
Login to vote

This is happening on Windows

This is happening on Windows XP SP2 machines. We are taking SAV 10.1.9 and installing SEP 11.0.6 to the machines. I have tried it 2 ways. I have seen it happen on the auto deployment tool (Find Unmanaged Clients) and through the standalone executables you can build. 

I'll check out that link. Thanks!

Vikram Kumar-SAV to SEP's picture
03
Sep
2010
0 Votes 0
Login to vote

As i Recommended above

As i Recommended above running Cleanwipe and re-deploying the client will fix it..I have seen this issue very rarely however I have seen them starting from RTM version till latest one..