Endpoint Protection

 View Only

  • 1.  Clients not communicating after migrating SEPM(12.1.5) server from windows server 2003 to 2008 with embedded database

    Posted Sep 06, 2015 01:46 PM

    Hi,

    I had performed DR process for migrating the SEPM server , the new server has the same IP and Hostname as the old SEPM server and the DR completed ok, but the clients are showing as Offline on SEPM, Can someone provide a quick resolution please as am pretty confused on this.



  • 2.  RE: Clients not communicating after migrating SEPM(12.1.5) server from windows server 2003 to 2008 with embedded database

    Posted Sep 06, 2015 02:09 PM

    Have you tried forcing a check-in?

    Is the SEPM service started?

    Did you shutdown the old SEPM?

    Try replacing the sylink on a client using the SEPM to see if it connects:

    Restoring client-server communications with Communication Update Package Deployment



  • 3.  RE: Clients not communicating after migrating SEPM(12.1.5) server from windows server 2003 to 2008 with embedded database

    Posted Sep 07, 2015 04:00 AM

    Have you restored the server private key backup ? if yes can you try to restore a different server private key backup ? and also please make sure the windows/anyother firewall is not blocking the client communication port (by defualt 8014).



  • 4.  RE: Clients not communicating after migrating SEPM(12.1.5) server from windows server 2003 to 2008 with embedded database

    Posted Sep 07, 2015 08:36 AM

    HI Brian,

    The SEPM service is started on the new server, and can you let me know how to force a checkin . I have already given Update content command on all the groups.

     

    The Old SEPM server has not been shut down but it is not in our domain. tried replacing Sylink.xml on a client and it connects to the new SEPM but others are connected to old one and shows online on the old one 



  • 5.  RE: Clients not communicating after migrating SEPM(12.1.5) server from windows server 2003 to 2008 with embedded database

    Posted Sep 07, 2015 08:46 AM

    You force a check in by right clicking the SEP icon on a client and selecting 'Update Policy'

    Please turn off the SEPM service on the old SEPM. It does not matter if in the domain or not. It need to be turned off if using the new SEPM.



  • 6.  RE: Clients not communicating after migrating SEPM(12.1.5) server from windows server 2003 to 2008 with embedded database

    Posted Sep 07, 2015 10:06 AM

    I have turned off the SEPM service on the old server. Checked on one of the clients by forcing the checkin before turning the SEPM service and it showed the old servers IP. Hopefully it pulls the latest policy and connects to the new SEPM.



  • 7.  RE: Clients not communicating after migrating SEPM(12.1.5) server from windows server 2003 to 2008 with embedded database

    Broadcom Employee
    Posted Sep 08, 2015 02:23 PM

    Do you have backup of recovery_timestamp.zip files? If yes, try to import them in the SEPM.

    OR

    If the SEPM IP and hostname remains same & If the client-server communications breaks, you can quickly restore communications by replacing the Sylink.xml file on the client computer. You can replace the sylink.xml file by redeploying a client installation package. Use this method for a large number of computers, for the computers that you cannot physically access easily, or the computers that require administrative access.

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