Endpoint Protection

Howdy,

 

I have looked for some info and found this http://www.symantec.com/business/support/index?page=content&id=TECH223884. 

Does this apply to a Windows system as well?  The SEPM is a 64 bit server and it is currently running 12.1.4.  One of my colleagues needed to test a deployment of the latest version on a Win 8.1 client, so I DL'd the latest, imported it into the SEPM, and created an install package.  As soon as the install starts, it immediately fails.

Thanks!!

Les

Should only apply to Mac per the article. You post the SEP_INST.log file for review

can you post the SEP_inst.lgo as well as SIS

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

Brian - SEP_INST.log is on the client?

Rafeeq - SIS?

 

Thanks!!  Willl search the client now for the log you both requested.

Located in %temp% directory

in the system Event Log > Windows Logs >> Application, this event is noted;

Windows Installer installed the product. Product Name: Symantec Endpoint Protection Client. Product Version: 12.1.5337.5000. Product Language: 1033. Manufacturer: Symantec Corporation. Installation success or error status: 1602.

 

Even though it is logged as a successful install, it did not load up.  Does not load on any Win 8 system I try.

Are you trying to install a 32 bit package on 64 bit OS? either case it will create a log

Neither file created during a failure.  Just tried a fresh install of both an .exe package and an .msi package.  Did a complete search of the system that failed the install - neither file created.

64bit.   Sorry - no file created on several systems now.  All systems are brand new out of the box, just set up on the domain and install package run - immediate failure of the package (but the above message is logged in the system event logs).

are you installing it manually or using SCCM or Altiris? try running an unmanged install in interactive mode, what does it say?

If I run the installer without creating a package first (importing/exporting with SEPM), the install flies right through and works fine.  Creating a 12.1.5 package with a 12.1.4 SEPM has not worked yet (and no log is created).

manually installing the SEPM created package - no SCCM or Altiris involved.  Unmanaged works fine.
 

can you create a package with this setting

Workaround:
Create an install package or create a custom setting under the “Client Install Settings” options to not use “Add the program to the Start Menu”, leave this unchecked.
If the install is successful, manually create the shortcut on the desktop that points SymCorpUI.exe.

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

creating....

That was checked - and I also noted the log file location.  Mine was %TEMP% which does not exist on these systems (MS Surface, if it matters).  Changed the log file location - see attached SEP_INST.log

 

Oh - forgot to say - still did not install.

Was the log file helpful at all - did it show anything that I could change on the package creation that would let it run?

#Edit

Hi,

How you could import SEP 12.1 RU5 package into the SEPM 12.1 RU4 console?

upgrade the SEPM to 12.1 RU5 & export the package. 

 

are you answering your own thread? :) 

Hi,

How you could import SEP 12.1 RU5 package into the SEPM 12.1 RU4 console?

Ideally it should give an error while importing it manually.

This is not a best practice also, upgrade the SEPM to 12.1 RU5 & export the package. 

 

You might want to look at;

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

 

No - letting the poster of the previous comment know how helpful his comment was  --  guess it should have been "reply" to him instead of "post new comment"

Ohh thanks I had some misunderstanding.

Hi,

If this is the only affected client then install unamnaged client and then replace the sylink.xml to make it managed client.

or you wish to deploy the same package on multiple operating system follow these steps

1) Run the upgrade.bat file. File should be available under SEPM\bin folder. Create a new SEP 12.1 RU5 package again and try to deploy.

2) Use client only patch 

Symantec Endpoint Protection 12.1.5 client-only patches

http://www.symantec.com/docs/TECH224745 

The problem was that the downloaded files (the entire 12.1.5 update from fileconnect) had some issues.  The 64bit client package was missing an entire folder - no system 32 folder was packaged inside.   I "re" downloaded everything a few days ago when I updated the SEPMs and started doing a comparison of everyting - that is when I noted that the 64bit client folders were different.  Still had a broken package inside the SEPM however and it is impossible to remove that package or add a new 64bit package to the SEPM (because it is the latest).  Many forum posts refer to a tool to remove a corrupt package from the SEPM - tech support had no idea about this.  Working with tech suppor though, we were able to modify the package .info file.  That basically tricked the SEPM into thinking it was a differnt package which then allowed me to add a new/good 64bit package to the SEPM - so now I have a 12.1.5_64Bit-NEW package and a 12.1.5_64Bit-DoNotUse package in my SEPM - that's all cool, now that I know what the issue is.

Thanks for the update. That tool will be available with Backline engineers and it seems your case did not reach there. Anyway it's good to know you could import the latest package by modifying .info file & it solved the problem. 

 

It would be good to know what these "hidden" tools are, like CleanWipe and this tool (and there are probably others). It would also be good to have a means to be able to refer to them by name (if you don't know that the tools exist, hard to ask for it with support - as I said, the guy I talked to had no idea of this tool, and none of his counterparts that he kept asking, knew about it either). Quite understandable that Symantec does not make the tools available for the everyday user, but if they exist, there should be an easier way to get them.

Support should know about these, if they don't, that's a different issue. The tool you reference for deleting bad packages has been around a long time.

Please let us know the trick :) might be useful for other, what exactly u modified in the info file.

In the info file which is attached, and hopefully has some highlighted areas, every spot that referred to the current package, we incremented by 1 number - hence ....5337... became ...5338...

That did not really work until we incremented the Sequence as well - for some reason that one was incremented by two (I think the tech support guy just forgot was was there when he told me to make it what I did).

That left the old package hanging out in the SEPM, but that's cool. I was able to add the new package again.

The info file is on the "CD" (the dowload files) that you get from fileconnect. Start at the root, then "SEPM", then, "Packages", and in there are all the info files. I'd be careful with them - you can probably jack up a SEPM beyond funtioning if you are not careful. Everything I did was at the direction of tech support.

Brian - I sure would have rather done all of this with the "tool", probably would have made this a lot easier. But again, nobody near the tech support guy I was talking with knew anything about this. I asked for it several times, several.....

(here's hoping the attachment retained the formatting so that the highlights show for you)

Les

forgot to add - in the SEPM, it does say I have package 12.1.5338.5000 - when it gets loaded on a machine though, it shows the correct version of ...5337.