Endpoint Protection

 View Only
  • 1.  Importing Sylink File Directly into installer file set

    Posted Jun 20, 2016 02:45 PM
      |   view attached

    Hello,

    Quick question.  Our deployment environment requires each computer be registered to the correct set of policies by use of a Sylink.xml file.

    If you see the screenshot below, you can seee that I copied our current sylink.xml file into the install folder (replacing the old one--though I renamed the old one to .old so I could keep it for reference).

     

    Just want to make sure this is a) functional and b) good practice.

     

    Thanks,

    Adam



  • 2.  RE: Importing Sylink File Directly into installer file set

    Posted Jun 20, 2016 02:48 PM

    It should work, yes. But why don't you just export the package from the group you want the clients to drop into?



  • 3.  RE: Importing Sylink File Directly into installer file set

    Posted Jun 20, 2016 03:17 PM

    I can't really say, since I'm not sure.  We were given packages but they were old, and we had to move to this specific version for Windows 10.  Apparently nobody knows how to provide the correct packages.

    or...  my guess is that this sylink files was written explicitly for these systems we are deploying to.  My department doesn't have access to the SEP Server.

     

    Either way, thanks for the input! :)



  • 4.  RE: Importing Sylink File Directly into installer file set

    Posted Jun 20, 2016 03:20 PM

    It should work, it's just manual effort.



  • 5.  RE: Importing Sylink File Directly into installer file set

    Broadcom Employee
    Posted Jun 21, 2016 01:56 PM

    Symantec Endpoint Protection (SEP) adds support for Windows 10 from 12.1.6 MP1 onwards. 12.1.6608.6300 is supported version.

    It should work becuase you have just renamed the old Sylink.xml file & not modifed anything within it.