Endpoint Protection

 View Only
  • 1.  Abandon a broken server and migrate clients

    Posted Jun 23, 2010 08:33 PM
    Hi,

    I have a SEP server running RU5 that is an absolute disaster.  Several virtual hardware changes were made (without consulting me!) to the machine, resulting in very strange behavior from it.  I'm planning to build a new server with 11.0.6 and I don't want to bring anything from the old server or database unless necessary.  I'm going to export/import my old servers to the new server, that's about all.

    I've got around 500 clients and for a while I expect to have two independent SEPM servers.  I'm thinking of using the migration tool to scan subnet by subnet and add the clients that way.  I really don't want to have to dump a new xml file and restart every machine to add them to the SEPM.  Any suggestions, or has anyone done something this strange before?


    Thanks!


  • 2.  RE: Abandon a broken server and migrate clients

    Posted Jun 24, 2010 12:33 AM
    Keep same name and IP address for new server and follow this procedure
    Best Practices for Disaster Recovery with Symantec Endpoint Protection



  • 3.  RE: Abandon a broken server and migrate clients

    Posted Jun 24, 2010 03:00 AM
    Or if you are not planing to have the same IP and Host Name for the other server follow the instructions on following article, But yes you will have to first upgrade the existing sepm to 11.0.6

    How do I move Symantec Endpoint Protection Manager from one server to another with a different IP address and host name?

     http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008031204405448 

     



  • 4.  RE: Abandon a broken server and migrate clients

    Posted Jun 24, 2010 10:02 AM

    I had a similar scenario where in I want to move the clients from one server to another server that has a newer version. Upgrading is not an option.
    What I did was change the primary server in the policies page to the new one. Went to clients and right click on the group to update content.
    I'm not sure if that is really working.

    But what I did was use the Sylink Replacer on the PCs. The only problem here is that the PCs must be turned on during this procedure.

    I'll also try Mugged's advice if I can squeeze it in. My problem is that the server does not have a backup so if everything fails. I'll have to rebuild from what's left.