Endpoint Protection

Is there any way to prevent a "Roll back" I have never seen ANY program outside of Symantec install then up and remove itself.

Initially what happened was I was removing SEP 12.1.2015 2015, but the user logged the PC off and signed in under his own name, this killed all processes that were currently running, I was also running a Malwarebytes scan at the time the user logged off. I was not able to find SEP installed after I had logged back in under the administrator account. I decided to run Cleanwipe, which I did, and it took two restarts and I saw that it had completed, I also checked the registry for HKLM and HKCU for Symantec folders and they were not there, they were also NOT in the program files (x86). I figured ok, all is clear so I can install the newest version of SEP, I was installing SEP Client 12.1.2100.2093 to a Windows 7 64BIT PC. I had downloaded the package from the Fileconnect, and copied and unzipped it on the PC. When I went to install it the installation looked fairly normal, but near the end, the rollback began, and NOTHING was installed. After the rollback was complete, I checked for the SEPInst logs and found nothing, both the Windows\temp and the C:\temp folder were empty.

1. Why wouldn't this install properly after I had run the cleanwipe?

2. Is there anyway to PREVENT rollbacks from happening?

3. Why does SEP even HAVE a rollback? I have never seen that on any program outside of SEP

4. What would even CAUSE a "Roll Back"

5. Is there a new version of Cleanwipe out?

I have one that I downloaded like a year ago.

The latest version of cleanwipe is 12.1 RU2. Was posted on 4/15/13 so you have an old one.

Basically, SEP hits the rollback when it conflicts with "something". The SEP_INST.log file will give more information but in some cases, support is needed so they can take a deeper dive into it.

Generally, Symantec will update the CleanWipe tool with each new version of SEP, so I'd recommend logging a support case to grab the latest version now that you're running v12.1.2100.*

A rollback is meant to revert the machine to its original state before you ran the install, so you aren't left with half an install and various orphaned files.  MS Office does the same thing if you cancel the install halfway through.  The causes for a rollback are varied, but generally stem from the installer hitting an issue preventing it from completing.

There's no way to anticipate if an install is going to fail, beyond checking pre-requisites and for any known issues.

I'd suggest looking inside the %temp% folder of the user you tried to run the install as, for the SEP_INST.log.  It only goes to the Windows\temp folder if the installer was running under the SYSTEM account.  A user's temp folder is normally in:

C:\Users\<user>\AppData\Local\Temp

Hi

What the SEP client version ?

Regards

I also installed a package for SEP 10 clients and also back.
I've used a number of ways, and the machine has finished installing.
You can use the SAV10 NoAV.bat in full to delete the entire package to install the symantec.
Then run to Cleanwipe.exe. Reboot the workstation and install SEP proceed.
please send to my mail address to get Nova.bat Tool and Cleanwipe
Wish you success.

Hi, 

Installation is getting rolled back because of various issues on client so it can’t be prevent.

As a better practice we can stop it to some extent while meeting the prerequisites.

Regards

Ajin

Hi, 

From installation log file we can understand that which point client installation getting fails.

SEP_INST.LOG located at %temp% by default.

Please sahre the same.

Regards

Ajin

Find the thread

http://www.symantec.com/connect/forums/sep-not-installing-windows-7-professional-sp1-64bit#comment-8665541

2093 installed properly on the PC, but not on the server. Still in limbo on this one.

You can try RU3, just came out yesterday.