/build/static/layout/Breadcrumb_cap_w.png

Symantec Endpoint Protection 11.0

hi I will need to create an mst for symantec endpoint protection

I have 2 questions to ask

1) I need to set up EPP server to
Target client to a particular update server for dynamic updates from a local EPP Server
If no local EPP server then default to <default> server

2) how do I deploy the sklink.xml file

cheers

0 Comments   [ + ] Show comments

Answers (10)

Posted by: GrassyKnoll63 13 years ago
Senior Yellow Belt
0
I'm getting an error message on both my x64 and x86 deployments using WDS after attemping to install the Symantec Endpoint Protection 11.0 application (using Lite Touch/Thin Client):

Operating system deployment completed successfully.

The computer is now ready to use.

During the deployment process, 1 errors and 0 warnings were reported.

Details...

"Application Symantec Endpoint Protection x64 11.0 returned an unexpected return code: 193"

Any ideas?
Posted by: pjgeutjens 13 years ago
Red Belt
0
Generally this error means %1 is not a valid Windows 32 program

What does the sep_inst.log file tell you? You should be able to find it in the %temp% folder of the installing user.

Kind regards,

PJ
Posted by: GrassyKnoll63 13 years ago
Senior Yellow Belt
0
I can't find the sep_inst.log file. I have this same error message whether deploying a 32 or 64 bit SEP on a 32 or 64 bit Win 7 image. It's not located unser Users\Administrator\AppData\Local
Posted by: Lucid 13 years ago
Purple Belt
0
Did you search the drive for *.log files? And as far as I'm aware, you can't install the 64-bit SEP client on a 32-bit OS, or the 32-bit SEP client on a 64-bit OS. So are you sure you're deploying the right SEP client to the right OS platform?
Posted by: GrassyKnoll63 13 years ago
Senior Yellow Belt
0
yes. I am positive i am installed the 64bit SEP onto Win7 64bit and 32bit SEP for Win7 32bit. I can't find any logs created from the Symantec install failure.
Posted by: GrassyKnoll63 13 years ago
Senior Yellow Belt
0
i don't understand it cause i can launch a silent install of the app from the command line after OS is already installed.
Posted by: pjgeutjens 13 years ago
Red Belt
0
While I have worked with SEP packages a lot, we don't have x64 infrastructure here so that part I do not know. Can you tell me if you are using 2 different installers, or if it's one installer for both 64bit and 32bit that then installs the appropriate version for the infrastructure?

Reason I ask is that maybe at the time of your install, something goes wrong with the check to determine x64 or x32...

as for the log file, assuming your installs run under localsystem credentials, try using psexec to get a cmd line running under localsystem and from there go to the %temp% folder for the account. This should be where the log is.

PJ
Posted by: GrassyKnoll63 13 years ago
Senior Yellow Belt
0
I need to add a correction:
When I try to install SEPx64 with Windows Deployment Server, I get:
"Application Symantec Endpoint Protection x64 11.0 returned an unexpected return code: 193"
When I try to install SEPx86 with Windows Deployment Server, I get:
"Application Symantec Endpoint Protection x86 11.0 returned an unexpected return code: 193"

...still can find the relevant log files...
Posted by: spartacus 13 years ago
Black Belt
0
What command line are you using for your Lite Touch deployment ?

Should be msiexec /i <Path to MSI> /passive

Spartacus
Posted by: hahaman 11 years ago
Yellow Belt
0

Hi, any solution for this?
can share?

thanks so much.

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ