Posted on 07-09-2018 11:38 AM
I'm trying to set up Symantec Endpoint Protection Cloud to distribute through Jamf and I'm wondering if anyone has gotten this working.
Symantec's instructions to do so are...incomplete? https://support.symantec.com/en_US/article.HOWTO128513.html
Posted on 07-09-2018 12:48 PM
That one can be a bit confusing...
What you need to do is to launch the "Symantec Endpoint Protection Installer" package, accept the message that says that you need to restart after the installation has completed, click "Tools" from the menu bar and choose "Create Remote Deployment Package". Then give your package a name and save location, then hit "Save"...
Once you have that done, then it's normal deployment from there...
Posted on 07-09-2018 12:58 PM
So the problem is that it creates two mpkg files, along with a requirements.plist and a fsdmanifest.js file. This is specifically for their cloud product, which seems to be slightly different than their normal SEP product. Previously I've always used either a pkg or dmg file to use
Posted on 07-10-2018 08:10 PM
I'm not familiar with this particular product, but in the past I've embedded packages inside of a package (using Composer to do this), along with config files that "manually" need to be installed to a particular location, then used post-install scripts to install the embedded packages.
Posted on 07-17-2019 07:34 AM
im experiencing issues with this as well, those 2 files do not seem to work properly for remote installs
Posted on 07-17-2019 01:46 PM
Replace the sylink.xml file with your configuration.
Upload pkg to jamf admin.
Posted on 07-22-2019 11:12 AM
thats for SEP14 we are on the SEPCLOUD version which is different and doesnt have that option anymore. thanks for taking a look though
Posted on 10-04-2019 11:26 AM
I don't know if this is still a topic for you, but as we also struggled with deploying our Symantec Cloud v15 (using the SEP 14.2 client) I will give you a short step-by-step instruction:
Hope that helps you :)
It seems this doesn't work any longer. This is our workaround at the moment:
This is a really bad solution. Hopefully Symantec is able to build a working deployable package, soon.