Endpoint Protection

 View Only

  • 1.  Clients are not reporting into a new SEPM with same hostname and IP as the old SEPM.

    Posted Jan 23, 2017 01:10 PM

    Clients are not reporting into a new SEPM with same hostname and IP as the old SEPM.

    The only thing I can see being different are the policy serial numbers. SSL on the new SEPM is disabled.

    I ran the SymDiag tool and it says client\server communication is fine.

    What am I missing?

     

    Thanks, Steve.



  • 2.  RE: Clients are not reporting into a new SEPM with same hostname and IP as the old SEPM.

    Posted Jan 23, 2017 01:13 PM

    Did you follow the DR method, install the recovery key when setting up the new SEPM and restore from backup?



  • 3.  RE: Clients are not reporting into a new SEPM with same hostname and IP as the old SEPM.

    Posted Jan 23, 2017 01:19 PM

    Hey Brian,

    I did attempt to do so at the time but it complained about the file. I proceeded without. I do however have a backup of the key file, so I should be able to import into the new console, correct?

    Steve.



  • 4.  RE: Clients are not reporting into a new SEPM with same hostname and IP as the old SEPM.
    Best Answer

    Posted Jan 23, 2017 01:27 PM

    When you reinstall the SEPM, this is when you input the recovery key. This typically comes first before doing the DB restore:

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

    Was there a specific error it threw?



  • 5.  RE: Clients are not reporting into a new SEPM with same hostname and IP as the old SEPM.

    Posted Jan 23, 2017 02:54 PM

    I believe the recovery key is the issue. I'm reinstalling as we speak using the key. I'll post here if and when it's successful. Fingers crossed.



  • 6.  RE: Clients are not reporting into a new SEPM with same hostname and IP as the old SEPM.

    Posted Jan 23, 2017 03:30 PM

    That was it. Thanks Brian for the quick response. Steve.