dalva
asked on
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.
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.
Use NoNAV. It is simple to use and will automatically remove all traces of Symantec Corporate 8.x. Download it here.
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.
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.
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hey Guys,
Thanks for all the options. It will take me a few days to test these out before I close this question.
dalva
Thanks for all the options. It will take me a few days to test these out before I close this question.
dalva
Hi,
Any updates ? Are you able to remove SAV 8 ?
Any updates ? Are you able to remove SAV 8 ?
ASKER
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-BC
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-BC
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.
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-BC
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-BC
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.
ASKER
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\MAPLO
PATH = C:\WINNT\SYSTEM32;C:\WINDO
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\snetc
\\Serverad1\NETLOGON\snetc
rem Uninstalls symantec version 8.1
MsiExec.exe /norestart /le \\Serverdb1\share\tempshar
date /t > c:\temp\symflag.txt
time /t >> c:\temp\symflag.txt
:END
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\MAPLO
PATH = C:\WINNT\SYSTEM32;C:\WINDO
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\snetc
\\Serverad1\NETLOGON\snetc
rem Uninstalls symantec version 8.1
MsiExec.exe /norestart /le \\Serverdb1\share\tempshar
date /t > c:\temp\symflag.txt
time /t >> c:\temp\symflag.txt
:END