![]() Part of Symantec sĢ protection against attacks on its services is to protect changes to its files and registry keys. The note describes how to remove the Windows registry entries and a file where these unique identifiers are kept. ![]() To prepare a VM for a virtualized environment, Symantec describes a process to remove all unique identifiers from the golden image prior to deployment (see Symantec s Tech Note How to prepare a Symantec Endpoint Protection 12.1.x client for cloning. You may choose to skip it and proceed to the deployment sections that follow. Summary This section explains the technical reasons why SEP was previously failing in deployed Synchronizer VMs. ![]() You will, however, still need to make sure they are used as described here for proper deployment of SEP. The sample code and OS Profile provided in the appendices are included in Synchronizer version 5.5 and newer and thus, you will not need to create or import them into the Synchronizer. These problems can be fixed by following the directions provided in this guide. The images below illustrate how Windows depicts a disabled network and how the Symantec console may report issues with its services. 1 Recommended Solutions for Installing Symantec Endpoint Protection 12.1.x in Shared and PvD Virtual Machines Applicability When Symantec Endpoint Protection (SEP 12.1.x is installed in a virtual machine (VM using a Citrix s Synchronizer with a version older than version 5.5 and subsequently deployed to end- users, the resulting VM in the end- user s machine may show the network as disabled and/or Symantec s console may report several problems.
0 Comments
Leave a Reply. |