OK.I have to export the sylink.xml from the new INSTALL and MANUALLY import it to every workstation and then it will show up on the new SEMP server. The instructions above omit information on entering the new SEPM server into the XML file so I assumed I change it manually.did that.ran the Skylink replacer app on my workstation and I've been waiting 10-15 minutes for my workstation to show up in the SEPM screen and nothing yet. Replace the now Sylink.xml on older cleints using sylink replacer.Īfter few minutes clients will start communicating with the new SEPM and showing online. Install the New SEPM version on the Machine.Ĭreate a new test packager and test it with polices that they are working correctly. If have fewer clients and polices then you can follow the below mentioned steps:Įxport the Polices from the existing SEPM. I did finally get an email back from Symantec.they said the sylink process is the best: There were several ways of migrating the SEP database from our old Windows 2003 server to our new shiny Windows 2008 server. Suggestions are really needed as I want to get this step said: We are migrating our network to new servers, therefore I needed to move the Symantec Endpoint Protection Manager (you guessed it, SEPM) to a new server. In addition, I thought I handled this part (it found a recovery file from our current server that I manually copied to the new one) and I tried to restore database (again, copied the backup DB to the new server) and restore says it cannot connect to the database and it never asks me to point to it. So, I am a little confused as to what I need to do here. I have no such options in my existing SEP. It also says to go to on the original server: 3.Click Policies > Policy Components > Management Server Lists > Add Management Server List I understand what it says here but I never get the option to choose Custom Configuration and Use Recovery File. When the Management Server Configuration Wizard runs, choose "Custom configuration" and "Use a recovery file". Reinstall Symantec Endpoint Protection Manager using a disaster recovery file (gathered in Step 2 above). I've installed the same version but it says use the procedures described in the Disaster Recovery. Use the procedures described in the Disaster Recovery in order to restore the database that you backed up from the old server, as well as the configuration files. I've studied and attempted to follow the steps (solution B) here and it just doesn't seem very clear:įor example, when it says: Install the same version of the SEPM you have now on the new machine (1). Accessed July 14, 2014.I am having frustrating problems moving SEPM Small Business Edition from our (soon to be) old server to my new one.
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. By default, the file name will export as the parent-policy_policy-name_sylink.xml. 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.