Had a couple of clients mistakingly installed with a very old SEP 11 RU4 MP2 client and put into a group that has auto upgrade to SEP 12 RU4 client on it but a few of machines have failed to upgrade and rolled back. Can these machines be directly upgraded? or do the clients need to be uninstalled and SEP 12 installed directly.

Had a look at the SEP_Inst.log and can't see anything in there that suggests why the roll back happened. 

Yes it can be

Upgrading or migrating to Symantec Endpoint Protection 12.1.4 (RU4)/12.1.4a (RU4a)

http://www.symantec.com/business/support/index?page=content&id=TECH211821

Upgrade and migration paths

Symantec Endpoint Protection 12.1.4013.4013 (RU4)/12.1.4023.4080 (RU4a) can upgrade seamlessly over the following:

• Symantec Endpoint Protection 11.x (can be upgraded to enterprise version only

hi Geogeo,

Please provide OS type ?

You can upgrade directly SEP 11 to SEP 12.1.4.

These are widows 2003 servers SP 2 

Current SEP client 11.0.4202.75

Install failed , rolled back 12.1.4013.4013

Please upload the sep_inst.log so it can be reviewed

Can you post the SEP_INST.log and SIS.INST.log files?

What logs do I need to gather in order to troubleshoot a failed SEP 12.1 client installation?

Here is the install log

Attachment(s)

SEP_INST_131.txt   3.09 MB 1 version

From the log it says

ScriptGen: ShowServiceProgress() script execution failed.

which points out to this document

http://www.symantec.com/business/support/index?page=content&id=TECH205042

Is tamper protection off and also you have disabled password to stop smc uninstall and smc stop?

HI Rafeeq

Tamper protection is set to log only, I didn't get a chance to disable the stop/uninstall password as they didn't inform me the machines were being moved to the new manager. It was the stop/install password which I thought might be effecting it as it's different on the two managers. 

"Thumbs Up" to the peeps above! 

Here are a couple more articles that seem relevant to the errors you're seeing (if not the same version of the client or OS):

http://www.symantec.com/docs/TECH169938
http://www.symantec.com/docs/TECH170259

try disabling those pass and check

Hi,

Thank you for posting in Symantec community.

I would be glad to answer your query.

Q. Can an SEP 11 RU4 MP2 client be upgraded directly to 12.1 RU4?

--> Yes, it's supported upgrade path.

To identify the point of failure of an installation,

1) Check Secars log (% SEPM Install Path %\data\inbox\log\exsecars.log).

2) Check the SEP_Inst.log file under %temp% directory.

In a text editor, open the log file that the installation generated.

To find failures, search for the following entry:

Value 3

The action that occurred before the line that contains this entry is most likely the action that caused the failure. The lines that appear after this entry are the installation components that have been rolled back because the installation was unsuccessful.

SEP 12.1 employs a side-by-side, replace on reboot installation strategy. Side-by-side means that new files are written to a new folder, referred to as a silo, isolated from the existing operational folder. Because the two versions are separated from each other, during a migration the older software is left running unchanged until the next reboot.

The primary benefit of side-by-side installation and replace on reboot is that the system continues to be protected by the existing software until the new version is in operation after the reboot.

This technique enables you to change the normal portion of the installation path during a migration, when applicable.