

How to export/import an existing Symantec Endpoint Protection, policy. Once the export has completed, a window will appear and display: Communications settings file has been exported successfully! In my case, this exports as My Company_SEP VDI 12.1_sylink.xml. Such exclusions can be configured for managed SEP clients using Centralized Exceptions policies in the Symantec Endpoint Protection Manager (SEPM) console. By default, the file name will export as the parent-policy_policy-name_sylink.xml. A file, folder, file extension or application needs to be excluded from being scanned by one or more features of the Symantec Endpoint Protection (SEP) client. Right-click on the policy and select Export Communication Settings.Ī new menu will appear, prompting you to save the file to a location. In the example shown, I want to export SEP VDI 12.1. Once logged in, navigate to Clients. Next, select the policy to be exported. How To install EPSEC Drivers for vShieldįirst, open up the server containing the Symantec Endpoint Protection Manager.Configuring a SEPM Policy for vShield and Symantec SVA.Exporting a Policy from Symantec Endpoint Protection Manager.Deploying vShield with the Symantec Security Virtual Appliance.How to Configure VMware vShield Manager and vShield Endpoint.How To Deploy OVA / OVF Template Using VMware vSphere Client.This article is the fourth part of a series explaining how to deploy vShield with Symantec Endpoint Protection for VMware Horizon View. This article provides instructions on how to export those settings. This file configures communication with Symantec Endpoint Protection Manager Server.

When deploying the Symantec Security Virtual Appliance on an ESXi host, one of the requirements for installation is you must have access to the sylink.xml file.
