Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Endpoint Protection 12.1.4100

Created: 22 Aug 2014 | 7 comments

We are having issues deploying SEP 12.1.4100 via SCCM 2012 R2 Task Sequence.

If we deploy a pre-built Windows 7 machine through the same task sequence, with SEP it builds without issue.  If we then deploy SEP via deployment it installs without issue.

If we add SEP to the TS (running as a package) it fails the build with an 0x00000001 error.  It looks like it is failing at the copying logs section of the task sequence.  I can't see anything in the logs to suggest a failure, so have no point to refer to.

Has anyone seen this before or can suggest where to look to see where it fails?

Operating Systems:

Comments 7 CommentsJump to latest comment

AJ_01's picture

How many client having issue?

Is it deploy success on any system?

Can any sep_inst.log file generated on system where it deploy?

Check this

https://www-secure.symantec.com/connect/forums/sep...

Error Codes list for Microsoft technologies

Article:TECH12638  |  Created: 2006-02-23  |  Updated: 2008-04-25  |  Article URL http://www.symantec.com/docs/TECH12638

Regard

AJ

therossatron's picture

We are still in testing phase for the WIndows 7 deployment, so it hasn't gone to production.  However this issues happens to all machines and we have seen it across physical and virtual machines.

We don't have internet access in the testing enviornment and initially thought it may be this, but I can deploy the app without issue via standard deployment.

I see nothing in the SCCM logs and it looks like it hasn't failed.  I see it at least parsing the install and looks like it is running the package.

Is there a certain step that this needs be added in the Task Sequence?  Is there a pre-req that is needed for this to run.

.Brian's picture

It sounds like SEP is not even making it where it would get installed, correct? If you check the %temp% directory, do you see a SEP_INST.log or SIS_INST.log?

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

therossatron's picture

Nothing in the %temp% directory at all.

It looks like something we have in the TS breaks of prevents it installing.  We have removed all apps and just run the SEP install line.

Has anyone noticed anything that has prevented SEP installing?

AJ_01's picture

Can you try the autoupgrade on one small group and check it update or not

How to upgrade Symantec Endpoint Protection clients using the Auto-Upgrade feature

Article:TECH96789  |  Created: 2009-01-14  |  Updated: 2014-04-11  |  Article URL http://www.symantec.com/docs/TECH96789

https://www-secure.symantec.com/connect/articles/u...

Regard

AJ

therossatron's picture

Hi AJ,

These are totally new clients using Windows 7.  Currently we only have XP clients.  If we deploy to the Windows 7 machines after they have finished building we have no issue.  We just can't install SEP during the build phase.

We need the software present during the build phase to decrease the amount of engineer involvement.

Ross

AJ_01's picture

There is the 2 way which can be decrease your man power.

First is that deployment wizard. If the client is in local barnch then follow it

How to push deploy clients in Symantec Endpoint Protection 12.1.x

Article:TECH164327  |  Created: 2011-07-11  |  Updated: 2014-04-30  |  Article URL http://www.symantec.com/docs/TECH164327

Second one is installed with OS.

You want to be prepare cloning for symantec

How to prepare a Symantec Endpoint Protection 12.1.x client for cloning

Article:HOWTO54706  |  Created: 2011-06-27  |  Updated: 2014-02-07  |  Article URL http://www.symantec.com/docs/HOWTO54706
 

Regard

AJ