Endpoint Protection

I am working on a batch file to run on sales force who don't come inhouse and use vpn to access our network.

The sales force currently has 2 versions of SEP 12.1 installed on the laptops:  12.1.671 and 12.1.1000.  I need to replace the sylink on the machines so they will check into the SEPM server.  Most will have 12.1.671 version on the laptops. 

I need a batch file to send to the sales force so they can run it and be done with it.

What I need is a call that will find which version of SEP is installed on the machine and then call the correct cmd to run Sylinkdrop.exe on the computer.

I have been told an "IF" statement will work to call to the C:\Program Files\Symantec\Symantec Endpoint Protect\12.1.xxxx  but once it reaches there, how to do I get the information to find the version 12.1.x to call the sylinkdrop.exe?  Then if it isn't the version called how do I get it to run the other version of Sylinkdrop.exe?

Hello,

Why Create a Batch File for Sylink replacing For SEP 12.1 when it is already available with Symantec Technical Support?

Create a Case with Symantec Technical Support for Sylink_Replacer_v.12.1 Utility and they would provide the same.

QuickStart Guide - Create and Manage Support Cases in SymWISE

http://www.symantec.com/docs/HOWTO31132

How to update a support case and upload diagnostic files with MySupport

http://www.symantec.com/docs/TECH71023

OR

Regional Support Telephone Numbers:

United States: https://support.broadcom.com (407-357-7600 from outside the United States)

Australia: 1300 365510 (+61 2 8220 7111 from outside Australia)

United Kingdom: +44 (0) 870 606 6000

Additional contact numbers: http://www.symantec.com/business/support/contact_techsupp_static.jsp

Secondly, you may like to check these Downloadable Scripts available on Symantec Connect Downloads Section - (NOTE: These scripts are not provided by Symantec)

https://www-secure.symantec.com/connect/downloads/script-convert-unmanaged-system-managed-system

https://www-secure.symantec.com/connect/downloads/replace-sylink

Hope that helps!!

I have created a case with support to receive the tool.  I will keep you up to date.

http://www.symantec.com/connect/sites/default/files/SylinkReplacer.pdf

Are you trying to run Sylink only on machines with either SEP 12.1.671 or 12.1.1000?

If you want to move the machines irrespective of the version, the above comments are good.

I am trying to run the Sylinkdrop.exe on the machines with either 12.1.671 or 12.1.1000.  However, Sylink Replacer will not work for this situation.  I will not know when the external sales reps will connect to the internal network, which is why I was thinking a batch file that can be emailed to them with instructions to run.  I have created a batch file for each version to run the SylinkDrop.exe on the machine but don't know how to find out what version is currently installed on the machines. 

The SylinkReplacer tool can be found here:

https://www-secure.symantec.com/connect/downloads/sylinkreplacer-tool-connecting-sep-clients-sepm

This tool will automatically replace the sylink.xml on multiple clients based on subnet. Much better than trying to use sylinkdrop.

Mike

Hello,

The SylinkReplacer Tool provided in the Link above is not for Symantec Endpoint Protection version 12.1. However, could be used if the clients are running the Symantec Endpoint Protection version 11.x.

Hope that helps!!

You will need to fill in the information from your own existing installations, as I have custom install folders and they will most likely not meet your envirinment. You can add this your local logon script for the people coming into your network.

Keep in mind, once you update their Sylink, when they leave your network, they will need to have it switched back...

You could consider creating other rules, such as location awareness, so that when they leave your network, the system will switch back and forth.

[Tweak file as necessary; I have put in bold what you will Need to change]

* * * * * * * * Begin Batch File * * * * * * * *

IF EXIST [path to symantec installatoin directory]\12.1.1101.401.105 (
  IF EXIST [path to symantec installatoin directory]\12.1.1101.401.105\Bin64\sylinkdrop.exe (
    [path to symantec installatoin directory]\12.1.1101.401.105\Bin64\sylinkdrop.exe -silent [-p *password*] [\\path to sylink.xml file]
)
IF NOT EXIST [path to symantec installatoin directory]\12.1.1101.401.105\Bin64\sylinkdrop.exe (
  IF EXIST [path to symantec installatoin directory]\12.1.1101.401.105\Bin\sylinkdrop.exe (
    [path to symantec installatoin directory]\12.1.1101.401.105\Bin\sylinkdrop.exe -silent [-p *password*] [\\path to sylink.xml file]
    )
IF EXIST [path to symantec installatoin directory]\12.1.671.4971.105 (
  goto exit
)
IF NOT EXIST [path to symantec installatoin directory]\12.1.1101.401.105 (
  goto next
    ) 
  )
)

:next

IF EXIST [path to symantec installatoin directory]\12.1.671.4971.105 (
  IF EXIST [path to symantec installatoin directory]\12.1.671.4971.105\Bin64\sylinkdrop.exe (
    [path to symantec installatoin directory]\12.1.671.4971.105\Bin64\sylinkdrop.exe -silent [-p *password*] [\\path to sylink.xml file]
)
IF NOT EXIST [path to symantec installatoin directory]\12.1.671.4971.105\Bin64\sylinkdrop.exe (
  IF EXIST [path to symantec installatoin directory]\12.1.671.4971.105\Bin\sylinkdrop.exe (
    [path to symantec installatoin directory]\12.1.671.4971.105\Bin\sylinkdrop.exe -silent [-p *password*] [\\path to sylink.xml file]
      )
IF EXIST [path to symantec installatoin directory]\12.1.671.4971.105 (
  goto exit
)

:exit
Exit

* * * * End Batch File * * * * * *

This may or may not work.  I m pretty sure I terminated my arguments properly.  Test it out.  There might be some tweaking to get done.

Either way, it is a solid base to get started with. 

*** Edit 1 ***

The -p *password is optional* to pass the password parameter if you need a password to Start and Stop the services in order to update the Sylink.xml file.

*** Edit 2 ***

This batch file considers that SEP 32 bit or 64 bit is installed. 

If you know for sure, that only 32 bit or only 64 bit is installed, than the batch file can be further reduced in length.  Seeing as it is a script, it should run quickly either way.

I was able to make the proper adjustments to the scripts so that it would work. 

I really appreciate everyones input.