asked on

sylink.xml appears to be wrong..

I and install a new site with Symantec Endpoint. Manager is version 111.0.5 and I have pushed out the SEP to the clients, but they do not appear to be talking to the server.

The sylink.xml file has the servers of:

- <ServerPriorityBlock Name="Priority1">
<Server Address="169.254.241.225" HttpPort="8014" HttpsVerifyCA="0" VerifySignatures="1" />
<Server Address="10.10.14.2" HttpPort="8014" HttpsVerifyCA="0" VerifySignatures="1" />
<Server Address="JRFSBS2008" HttpPort="8014" HttpsVerifyCA="0" VerifySignatures="1" />
</ServerPriorityBlock>

My Concern is the first listing that is a auto generated IP..

Is this the problem? and how do I get it fixed on the clients I have rolled out?.. should I just push them out again?

jimmymcp02

is any of the information on the sylink.xml correct?

If so then try the following.

Restart the sep server and one client then check sep manager to see if its showing up as managed.

also if you check the client is sep installed?

If you dont want to reinstall then you will have to use the sylink replacer and sylinkremote tools from symantec.

911bob

ASKER

Just the line:

<Server Address="169.254.241.225" HttpPort="8014" HttpsVerifyCA="0" VerifySignatures="1" />

Is wrong..

The rest is OK..

I have done the sylink replacer from one omachine and am waiting for it to show up with the green dot.. and I have manually added it to the group.. so we will see.

there are about 15 machines, so I am not sure if uninstall/ re-install may not be the easiest..

Where doe it pick up that file from when you do the push install (find unmanaged clients and then push the install..)

Thanks

ASKER CERTIFIED SOLUTION

jimmymcp02

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

911bob

ASKER

Main cause was firewall was blocking the port it needed..

Secondly I edited the sylink.xml file to remove the 169.. IP entry to get rid of it.. not really necessary as it will supposedly skip entries that do not "work"

jimmymcp02

Thank you.

You can add the port exception to your windows firewall to prevent this from happening in the future if you are already running the sep firewall then having 2 firewalls might cause some problems. so either use one or the other one.