Skip to main content

I have to ask a question that I should know the answer to, but for some reason am struggling.
Trying to deploy the Symantec DLP 15.7 agent.
It used to be you could invoke a create_package script in the same directory as the extracted zip of the agent install and it would create a .pkg with the certs that are needed. Well apparently Broadcom deprecated this.



So from what i've heard from Broadcom I need to cache all files for the installation on the workstation then invoke their agent_install script.



I'm trying to figure out how I cache all files from the zip in the JAMF Waiting Room? If I utilize Composer and copy them to say /private/tmp it never recognizes the changes. If I use composer and just drag the folder with all files to Composer and build a package, the package shows up, un extracted in the waiting room when i push it via policy, and the script invocation fails because it can't find the files needed.



So, again something i should know, but how can i accomplish this?

I built a pkg that places all of the files from the zip into a folder in /tmp, but I replaced the agent_install script with my own postflight script that uses the installer command to install the AgentInstall_15_8.pkg. Then it's just another package, executed like any other.



You might be having issues with the path if you are executing their agent_install script. Their script expects to be run from the directory it lives in (with all the other files) so it might not be able to find the AgentInstall pkg. I hard-coded the full path since I know where the files will be.

@alexjdale - how did you build the package to deploy the files from the zip to /tmp? I seem to be striking out with Composer. My intent was to utilize the agent_install script after caching the files from the zip. So it is a script in jamf that i just call in the policy.

Right, with what you've done so far, if the zip file is already cached, then you could just run a script that will unzip it and then install the pkg inside. You should probably just ignore the agent_install script since it doesn't have a hard-coded path for the pkg, and the shell would have to be set to the right directory (the script doesn't do anything special, it only installs the pkg).



You could do this with the "unzip" and "installer" commands.

Thanks I ended up just installing the package which included all the files and then running the post flight script to do the install, which worked. I for some reason was under the impression that a package that contains files to deploy to a location had to be cached, but i have come to find that that only puts that package in the waiting room. Thanks for the help.

Can you elaborate on this? Is there an example of the script you use postflight? We are stuck at the same fork in the road as well.



@brianmcbride99

Reply


Terms & ConditionsCookie settings