Endpoint Protection

 View Only
Expand all | Collapse all

Sylink.xml contains a nonexistent server

  • 1.  Sylink.xml contains a nonexistent server

    Posted Jan 20, 2015 04:33 PM

    We have one SEP server but the xml file contains a second server in the ServerList section. That server happens to be the previous SEP server before migrating to this one. The nonexistent server does not show up in the Servers list in the Manager. How to fix?

     



  • 2.  RE: Sylink.xml contains a nonexistent server

    Posted Jan 21, 2015 10:47 AM

    Is there anything showing in your mamagemen server list?

     



  • 3.  RE: Sylink.xml contains a nonexistent server

    Posted Jan 21, 2015 11:23 AM

    first export the new sylink file as per this document

    Exporting the client-server communications file (Sylink.xml) manually

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

     

    verify if the IP shows up, if it shows up then its picking it from your network connection settings,

    then deploy it using this method

    How to deploy/update communication settings from your SEPM to your SEP clients machines with SEP 12.1 RU2 or newer

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

     



  • 4.  RE: Sylink.xml contains a nonexistent server

    Posted Jan 22, 2015 01:27 PM

    No the phantom server does not show up there, just the existing server shows up.

    This is how it shows up in the sylink.XML when I Export Communications Settings for a group:

        <ServerList Name="Default Management Server List">
          <ServerPriorityBlock Name="Priority1">
            <Server Address="existing.mydomain.com" HttpPort="8014" HttpsVerifyCA="0" VerifySignatures="1"/>
          </ServerPriorityBlock>
          <ServerPriorityBlock Name="Priority2">
            <Server Address="phantom.mydomain.com" HttpPort="8014" HttpsVerifyCA="0" VerifySignatures="1"/>
          </ServerPriorityBlock>
        </ServerList>

    Also, I just checked a few clients and thier sylink.xml is identical.

    I wonder where it's getting that phantom server info from?



  • 5.  RE: Sylink.xml contains a nonexistent server

    Posted Jan 22, 2015 01:43 PM

    Have you tried exporting the latest sylink or was this it?



  • 6.  RE: Sylink.xml contains a nonexistent server

    Posted Jan 22, 2015 01:47 PM

    That's it.



  • 7.  RE: Sylink.xml contains a nonexistent server

    Posted Jan 22, 2015 01:59 PM

    from the sylink, it says

    ServerPriorityBlock Name="Priority2">
            <Server Address="phantom.mydomain.com" HttpPort="8014" HttpsVerifyCA="0" 

    Priory 2 is defined in Management server list Only, 

    Do you have a different domain set up within SEPM?

    You can check that under Admin - Servers Tab.. Multiple domains or you have just the Default?



  • 8.  RE: Sylink.xml contains a nonexistent server

    Posted Jan 22, 2015 03:21 PM

    No multiple domains. Just one Site (Local Site). Two servers are listed, Existing (the current SEP server) and localhost (the database host - Embedded (SQL Anywhere)). No other server is listed in the Site Properties either.



  • 9.  RE: Sylink.xml contains a nonexistent server

    Posted Jan 22, 2015 05:17 PM

    Whats the version of SEPM?



  • 10.  RE: Sylink.xml contains a nonexistent server

    Posted Jan 22, 2015 05:22 PM

    12.1.5



  • 11.  RE: Sylink.xml contains a nonexistent server

    Posted Jan 23, 2015 07:37 AM

    Just to clarify, newly exported Sylink.xml files are correct and do not show the old server.

    In which case, which sylink.xml file caused you to open this thread?  If it's the one in the SEP Client on the SEPM itself, then is it possible that the client was installed when the old SEPM still existed?

    After install, the sylink.xml file doesn't get updated again (unless you manually do so using sylinkreplacer/sylinkdrop/comms package update/etc), so it's perfectly normal for the sylink.xml file on older clients to still contain references to old SEPMs.  Changing the MSL assigned to clients in the SEPM Console  will correctly tell them to talk to whatever you define, but does nothing to the sylink.xml file held locally on those clients.



  • 12.  RE: Sylink.xml contains a nonexistent server

    Posted Jan 23, 2015 10:53 AM

    No, the newly exported sylink.xml files are incorrect. They are showing the old server.



  • 13.  RE: Sylink.xml contains a nonexistent server
    Best Answer

    Posted Jan 23, 2015 12:49 PM

    Oh ok.  And you've confirmed that the group that you're exporting the comms file from is using the Default MSL rather than a custom one?



  • 14.  RE: Sylink.xml contains a nonexistent server

    Posted Jan 23, 2015 01:49 PM

    OK, finally got it. Thanks! I have been confusing the list of servers under Admin and the MSL. I had forgotten about the MSL under Policy Components. I did have that set properly at one time. After doing the migration over to this server I created a new one without a Priority 2 listing the old server and assigned it. Some how the old MSL listing both servers became assigned again. Hmmm...