• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3724
  • Last Modified:

Best way to remove symantec enterprise client version 8.1

We are finally planning the move from Symantec Corporate Enterprise 8.1 to Symantec End Point Protection 11.0.

We want to have a clean client before installing version 11.  

We called Symantec support to inquire about tools available to remove the client version 8.1 without using the normal add remove programs method.  Their reply was there are no tools available since they no longer support version 8.1.

I would like to learn how others have done this.  Is add remove programs the best method?  I get the feeling at times that this method leaves residual files and registry entries.
0
dalva
Asked:
dalva
  • 3
  • 2
  • 2
  • +3
2 Solutions
 
klj2361Commented:
Use NoNAV.  It is simple to use and will automatically remove all traces of Symantec Corporate 8.x.  Download it here.
0
 
RTSCCFLAXCommented:
I agree with NoNav I would also run SCScleanwipe.  

The Last question Choose No

Here is the link for it
http://www.sendspace.com/file/zbvepg 

It is in a .rar format you can use Winrar to open it.  Is a free trial.
0
 
huntleyjCommented:
I can't take the credit for this but if you originally pushed the AV clients out from a server you can make a small change on the servers VPRemote.dat file and push the clients out again. But this time when you push it out it uninstalls it.
Here is the link , look at the accepted answer there. I just used this method 2 weeks ago uninstalling Corp Ed 9 across a small 60 pc network
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
MaerosCommented:
I've rolled out SEP 11 on networks before where old versions of Norton Antivirus Corporate Edition 8 were installed.  I have found that uninstalling through add/remove programs of both NAV CE and the older accompanying LiveUpdate followed by a reboot worked like a charm before installing SEP 11.

Just make sure whichever client install package/method you choose to use is set so that is does not preserve and use old and existing settings.  That way the new install of SEP will completely ignore old settings and policies, and will grab the newest ones from SEPM.

I should also note that pushing installs through for example the Find Unmanaged Computers tool will cleanly preform a silent uninstall of versions 9 and 10 of NAV CE on the target machine before installing version 11.  However that being said, Symantec has admitted the automatic uninstall when pushing installs will not remove version 8.
0
 
MaerosCommented:
By the way, if you already have a pre-existing AV infrastructure using the old Symantec System Console, I highly recommend when installing SEPM on a server that you create a new infrastructure instead of importing and "grafting" on the old one.  It'll save you a lot of grief down the road.
0
 
xmachineCommented:
Hi,

I feel your pain, you should use a batch file to automate the removal procedure.You need Psexec (Pstools) to push the batch to all machines and execute it remotely.  

(import them from Symantec server, use excell to export ip addresses and save them into a text file"

Check the attached code:

(double check the Symantec GUID from the registry under HKEY_LOCAL_MACHINE\software\microsoft\wi ndows\currentversion\uninstall\)

save the batch file as e.x: uninstall.bat

- prepare a list of IP addresses (one IP at a line) and save it as e.x: old-sav.txt

the downlod Pstools from here:
http://download.sysinternals.com/Files/PsTools.zip

extract it and go to CMD.exe

replace domain with your domain name
replace admin with your domain admin account
type password when you asked to

the command:

Psexec.exe @old-sav.txt  -u domain\admin -c -d -low uninstall.bat

if everything went as the plan, go to the SEPM and deploy SEP using "Find unmanaged computers" .

thats it.

@echo off
if not exist "C:\Program Files\Symantec AntiVirus\RTVSCAN.EXE" goto EndSymantec
start "" /wait msiexec.exe /x {848AC794-8B81-440A-81AE-6474337DB527} /qb
pause 
:EndSymantec
 

Open in new window

0
 
dalvaAuthor Commented:
Hey Guys,
Thanks for all the options.  It will take me a few days to test these out before I close this question.
dalva
0
 
xmachineCommented:
Hi,

Any updates ? Are you able to remove SAV 8 ?
0
 
dalvaAuthor Commented:
Thanks for your patience.  We have spent some time this week trying some of these ideas and thought we had it.  Here is where we are at.

Quick reminder: We are trying to remotely uninstall Symantec Anti-virus version 8.1 from 200 clients.

The first attempt was to run this PSTools command line
psexec \\PCTEST03 MsiExec.exe /forcerestart /l* c:\temp\log7.txt /q/x{0EFC6259-3AD8-4CD2-BC57-D4937AF5CC0E} REMOVE=ALL

which produced this error:
MSI (s) (9C:14) [10:00:05:882]: Product: Symantec AntiVirus Client -- Error 1327.Invalid Drive: F:\

Turns out we have previously mapped the F drive to the Shell Folders path.

When we push the remote the F drive is not mapped to the domain account doing the push.

With that in mind we ran the next two commands successfully before running the uninstall command as shown in the beginning.

psexec \\PCTEST03 net share temp=c:\temp
psexec \\PCTEST03 net use F: \\PCTEST03\temp

Then this command which continues to fail with the same error.
psexec \\PCTEST03 MsiExec.exe /forcerestart /l* c:\temp\log7.txt /q/x{0EFC6259-3AD8-4CD2-BC57-D4937AF5CC0E} REMOVE=ALL

Error message:
MSI (s) (9C:14) [10:00:05:882]: Product: Symantec AntiVirus Client -- Error 1327.Invalid Drive: F:\

Has anyone run into this drive letter problem and how did you overcome it?  Any suggestions?

Our backup plan is to run the uninstall from a login script which we confirmed works.  But this takes away the precision targeting we were looking for.


0
 
dalvaAuthor Commented:
We ended up using a batch file with the lines shown below.  Basically the batch file performs an command line add / remove after installing the file and print service.

By allowing the normal drive mapping to the F drive to occur before the uninstall we were able to avoid the error from previous attempts.  Points were allocated based on tip to use add remove method and batch file.

rem this script installs file and print services
rem then removes symantec version 8.1

rem our normal login placed first to insure F drive is mapped before the symantec uninstall
\\ServerAD1\NETLOGON\MAPLOGINSERVER
PATH = C:\WINNT\SYSTEM32;C:\WINDOWS\SYSTEM32;K:\Program Files\Citrix\System32\Citrix\IMA;C:\WINDOWS\COMMAND;Z:\
ECHO Loading XP Login script, please wait...
Z:\KIX32.EXE Z:\LOGON.KIX

rem symflag prevents this part of script from running more than once
IF EXIST c:\temp\symflag.txt GOTO END
rem snetcfg installs file and print services
\\Serverad1\NETLOGON\snetcfg.exe -v -u MS_Server
\\Serverad1\NETLOGON\snetcfg.exe -v -l %windir%\Inf\NETSERV.INF -c s -i MS_Server

rem Uninstalls symantec version 8.1
MsiExec.exe /norestart /le \\Serverdb1\share\tempshare\symantec\%COMPUTERNAME%.log /q/x{0EFC6259-3AD8-4CD2-BC57-D4937AF5CC0E} REMOVE=ALL
date /t > c:\temp\symflag.txt
time /t >> c:\temp\symflag.txt

:END
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 3
  • 2
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now