Good morning Ninjas,

I'm having trouble with a post-install task for Symantec Endpoint Protection (SEP) in my images. The package was freshly created, tested on my computer, and the normal manual installation is fine. The package is good and works on both Win7Pro and Win10Enterprise.

I then created a Managed Installation (MI) in my K1 for a silent installation I can deploy to existing targets using the following parameters, and with great success: setup.exe /s /v"/l*v log.txt /qn RUNLIVEUPDATE=1 SYMREBOOT=REALLYSUPPRESS". I can deploy this to any existing computer, and I also have a script running that calls this MI in the event there is a computer out there on our network that for some reason does not have SEP installed.

I exported this MI from the K1 and imported it to the K2, added the same parameters in the Post-Install (PI) details, but when I test the image, this task fails every time. The package is being pushed to the target, Setup.exe appears in my Task Manager, but then disappears almost immediately.

I'm not sure if I need to manually script this entire Post-Install task or not, as all my other PIs have been MIs from the K1 which I exported to the K2 and otherwise had no issues with. Or, in the Detail for the PI on the K2, can I add a /wait switch somewhere after my installation parameters?

Thoughts?

Thanks,

-- Ray

1 Comment   [ + ] Show Comment

Comments

  • So I am new to KACE but I found that this artical helped me so that I did not have to move scripts from K1 into K2.
    http://www.itninja.com/blog/view/install-k1000-installations-in-k2000
    • I've thought about doing that but declined for a couple reasons.

      1. I can see individual install processes with separate post-installation tasks, narrowing down troubleshooting if an all-in-one install task completes 9/10 installations, but shows a failure because of the 1 failure.

      2. Different images require different software.

      Basically, most anything that's going to be available in an image is also something that I want as a stand-alone Managed Installation item. Exporting/importing from K1->K2.

      Good luck with Kace. I'm on year 2 of being the admin. Learned lots of stuff here and have had good help from several users.
Please log in to comment

Answers

1
cant say i have had that problem with SEP as i have recently done it for windows 10 machines but the deployment tool was HPCA and SCCM

what we run is the following as we have set it to deploy in a maintenance window and are happy with the reboot, and the machines are hitting our servers for their updates post reboot.

"setup.exe" /v"/qn /l*v C:\Windows\Temp\MSILogs\SYT_SEPLIVEW10_A_12_6_R01_Install.log"
Answered 07/29/2016 by: sparky86
Fourth Degree Brown Belt

  • I figured it out.

    I created a new post-install Application, created a bat file to run setup.exe with my parameters, zipped it up into the SEP zip, and called the bat with a /wait switch.

    Worked in the latest deployment. Thanks for your response.
Please log in to comment
Answer this question or Comment on this question for clarity