Endpoint Protection

A company that has been brought into our WAN has their own V11.x SEPM server and clients that are pointed at it in their LAN.  I replaced the sylink file on a server at their site so it would point to our central SEPM server and made it the GUP for their local LAN.  I did this in preparation for a deploy to their site so their clients would not come over the WAN for definition updates.

Created a V12.x client install package from our SEPM server.  Installed this on one of their clients but it is still pointing to their SEPM server.  Why did the client not change to point to our SEPM server?

Also, in V12.x what is the correct sylink file to replace to get a client pointed at a new or different SEPM server?

you can use teh sylink drop on the installed client.

If you want to use sylink replacer tool, then you need to get the tool for SEP 12.x from technical support.

Sylink replacer for sep 11 and sep 12 are different.

Hi,

What is the location for Sylink.xml in Symantec Endpoint Protection 12.1?

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

Restoring communication to clients with a new Sylink.xml file

http://www.symantec.com/business/support/index?page=content&id=TECH106288

Replace Sylink.xml file on 2-3 computers manually & check whether client reports to correct SEPM or not?

Check MSL list also because the management server list specifies the order in which clients in a particular group connect.

Clients and optional Enforcers first try to connect to Symantec Endpoint Protection Managers that have been added with the highest priority. If Symantec Endpoint Protection Managers with the highest priority are not available, then clients and optional Enforcers try to connect to management servers with the next higher priority.

I guess what I expected to see was when the V11.x client was upgraded to V12.x that the client would automatically be pointed to the new SEPM server since the package would have contained a different sylink file with our SEPM server information.  Are you saying that this will not work?  The V12 upgrade would not replace the existing V11 sylink file?

We use Microsoft's SCCM for mass deploys so what I was trying to avoid was doing a separate deploy to replace the sylink file for V11 to get them pointed to our SEMP's and another to upgrade to V12.  In the past when a new company has come into our network we just did an SCCM deploy of sylink to their V11 clients to get them pointed to our central SEPM servers which are located in our datacenter.  We know the specific location of sylink for V11 clients.  We did not need to use the sylink drop tool.

So if we bring in a new company that is already running V12 is this no longer an option?  Isn't there a specific sylink file that the client looks at to determine what management servers they should be communicating with?

SCCM is used because distribution servers are setup on the local LAN and these will push out software updates and upgrades from this server rather than going over the WAN.  Bandwidth is a concern even though these sites may have T1's or larger pipes going into the site.  A company like the one that has been brought into our infrastructure has several physical locations.

Hi,

Q: I guess what I expected to see was when the V11.x client was upgraded to V12.x that the client would automatically be pointed to the new SEPM server since the package would have contained a different sylink file with our SEPM server information.  Are you saying that this will not work?  The V12 upgrade would not replace the existing V11 sylink file?

--> Ideally it should work because it contains new sylink file within it. However I would suggest try with following option.

While exporting package select Remove all previous logs and policies and reset client-server communication settings.

Path: Admin --> Install Packages--> Client Install Settings --> Under upgrade settings select Remove all previous logs and policies and reset client-server communication settings.

Q: So if we bring in a new company that is already running V12 is this no longer an option?  Isn't there a specific sylink file that the client looks at to determine what management servers they should be communicating with?

--> Client will look into sylink file which will be at following location

What is the location for Sylink.xml in Symantec Endpoint Protection 12.1?

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

Hi,

Any update on this.

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.

got a question, assuming that existing SEPM server is the same as the new upgraded SEPM, can I just re-use the same SYLINK.xml file for SEP v 12.1 client exported from SEP 11 client ?

No,

You need to use the 12.1 only then only it will work.

Hi,

You can't use same sylink file for SEP v 12.1.

SEP v 12.1 has introduced new ports & those are required to establish communication between SEPM and SEP clients.

While doing an upgrade it will ask you to change the Reporting port (8445) and Web Service port (8445).

Check following article for more details:

SEP 11.x to SEP 12.1 Upgrade process graphical overview

https://www-secure.symantec.com/connect/articles/sep-11x-sep-121-upgrade-process-graphical-overview

Oh no, What shall I do ?

because in some of the WORKGROUP server which is not joined to the Windows domain, in the SEP client directory I overwrite the default SYLINK.XML with the existing SYLINK.XML in the existing DMZ servers.

So far it's been good the client can get the green dot which talks to the SEPM server.