How to uninstall SAV 8.0 remotely in the background.
I'm trying to install the new Symantec Endpoint Security, but it will not install over top of SAV 8.0. So as opposed to going to each computer, is there a way to uninstall 8.0 remotely in the background that won't affect users? I guess the last part isn't as important, but it would be nice.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
TY Vic...... Lets hope it fits the bill....
:^)
:^)
We used PSEXEC (combined with NoNav.exe) to completely remove all versions of all Symantec and Norton applications off our geographically extended (several thousand square miles) WAN.
We had over 2,300 boxes and probably had 75-80 % success.
Great tool (as is NoNav).
Vic
We had over 2,300 boxes and probably had 75-80 % success.
Great tool (as is NoNav).
Vic
ASKER
Since I'm not the best with batch files, I did some looking and Symantec has something already called SCSCleanwipe 3.1. Now, how do I go about running this from Active Directory? There's the main batch file, but it then calls other files, so do I just point it to everything when I create a startup batch file to run in Active Directory.
ASKER
Any suggestions on using the SCSCleanwipe? I just need to know what I point to in Active Directory to use this batch file.
I never had much luck using Symantec tools to fix Symantec problems.
Here is some good scoop on creating the batch command needed to run PSEXEC+any Executable against a list of computers.
Vic
Here is some good scoop on creating the batch command needed to run PSEXEC+any Executable against a list of computers.
Vic
ASKER
I'm not seeing how to use PSEXEC, could you please give me a little help on getting started with it, or possibly a link about it.
Oh, you mean I should actually include the link when I mention it?
Just ask me how dumb I feel right now.
Back in a minute.
Vic
Just ask me how dumb I feel right now.
Back in a minute.
Vic
https://www.experts-exchange.com/questions/22397407/deploying-DST-package.html
Read the comments from 'sirbounty' - he is the one who actually solved that one - not me.
"Two seperate routes posted actually...
If you have a list of computers, then use:
for /f %a in (C:\Computers.txt) do psexec \\%a c:\pathtofile\file.exe
That's just a command-line command.
If you need to add it to a batch file, change %a to %%a (both instances).
Otherwise, just using psexec's builtin 'loop' method:
psexec @C:\computers.txt c:\pathtofile\file.exe
and both will use your current logged in credentials.
-u 'username' -p 'password'
(added to psexec parameters) allows you to change the user credentials)"
Read the comments from 'sirbounty' - he is the one who actually solved that one - not me.
"Two seperate routes posted actually...
If you have a list of computers, then use:
for /f %a in (C:\Computers.txt) do psexec \\%a c:\pathtofile\file.exe
That's just a command-line command.
If you need to add it to a batch file, change %a to %%a (both instances).
Otherwise, just using psexec's builtin 'loop' method:
psexec @C:\computers.txt c:\pathtofile\file.exe
and both will use your current logged in credentials.
-u 'username' -p 'password'
(added to psexec parameters) allows you to change the user credentials)"
ASKER
I didn't use PSExec, but I did use a batch file and pushed it out as a startup batch file with Active Directory. Worked like a charm, thanks.
i have a similar problem, how did you create your batch file, i posted a help topic, thank you
:)