AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() Am I overlooking something, would sylink debugging help? Thanks from a SEP newbie. Is there a restriction when performing an upgrade to move from one sylink.xml file type to another? I noticed there is a tool SylinkDrop.exe, and have included that to run after the upgrade has taken place, but that does not appear to work even though it says sylink.xml file has been successfully replaced. Then performing a reboot overwrites the Sylink.xml file with the original region/location sylink type. ![]() > the sylink.xml file is not updated in the below locations: C:\ProgramData\Symantec\Symantec Endpoint Protection\\Data\Config\SyLink.xml C:\ProgramData\Symantec\Symantec Endpoint Protection\CurrentVersion\Data\Config\SyLink.xml I checked the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\SYLINK\SyLink and the "PreferredGroup" is updated, but the "CurtentGroup" is the previous Sylink group. A fresh brand new install works as expected and installs the different sylink.xml files, but if I perform an upgrade e.g. Each package type (x86 or 圆4) will install a different sylink.xml file based on location or region of device. Being a packager I have packaged various versions of SEP, e.g. Hi people Being relatively new to SEP, I thought I would try and get my answers here.
0 Comments
Read More
Leave a Reply. |