Endpoint Protection

 View Only
  • 1.  Moving to New SEPM and New SQL Servers

    Posted Oct 27, 2010 05:39 PM

    Current Configuration

    Location 1 3000 Clients
    Server 1: Windows 2003 SP2 Server SEPM
    Server 2: Windows 2003 SP2 SQL Database 2005

    Location 2 3000 Clients
    Server 1: Windows 2003 SP2 Server SEPM Embedded Database

    New Hardware for Location 1:
    2 x WINDOWS 2008 R2 Servers

    I want to move Location 1 to a new SEPM Server, New hardware, Name and IP address. As well as move the SQL Database to a new Server to New hardware, Name and IP address.

    Location 1 and Location 2 had Replication Enabled but had to be broken when moved to SQL database. I would like to re-enable replication once move to new hardware is complete as we will be moving Location 2 to SQL database in a few weeks.

    ***Questions about Location 1***

    Move SEPM or SQL to new Hardware first?

    Moving Database form 2k3 to 2k8 - Any issues?

    What is best option in regards to moving SEPM and ensure clients respond/report to new SEPM Server?

     

     



  • 2.  RE: Moving to New SEPM and New SQL Servers

    Posted Oct 27, 2010 05:58 PM

    These steps should be pretty solid for you:

    -Install SQL

    -Install SEPM on the new machine

    -During the new install, select "additional site" to replicate with the original SEPM

    -Replicate all the data over, this may take time (hours)

    -Create a Management server list with the NEW ip/hostname as priority 1 and the OLD ip/hostname as priority 2. Assign this to ALL groups

    -Leave this setup as is until you see all/most of your clients have moved to the new SEPM

    -After everyone is moved over, open SEPM, go to ADMIN, select SERVERS, and delete the replication partner listed

    -Edit the management server list to remove the priority 2 holding the old machine info

    -At this point you can do whatever you want with the old server

    If you have any straggling clients that dont connect you can replace the sylink.xml on them to get them connected to the new sepm.

    I know it was brief...speak up if you have any questions.



  • 3.  RE: Moving to New SEPM and New SQL Servers

    Posted Oct 28, 2010 03:59 AM

    John Explained it very well

     

    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/854fa02b4f5013678825731a007d06af/9bb60351f8fa6d3f65257409007f5774?OpenDocument

     

    How to point Symantec Endpoint Protection(SEP) clients to a new Symantec Endpoint Protection Manager after you have either uninstalled, are going to decommission or replace the Existing Primary Symantec Endpoint Protection Manager (SEPM).

    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/23d0a77b280a618988257567007caec1?OpenDocument

     

    these two documents should help, wait for the links to get redirected  :) 



  • 4.  RE: Moving to New SEPM and New SQL Servers

    Posted Oct 28, 2010 11:16 AM

    Thanks for the Help...

    Regarding the Replication, I've read that once replication is established and then broken i would would be able to setup Replication with the 2nd location once all the clients have moved over to the new servers. is this true? 



  • 5.  RE: Moving to New SEPM and New SQL Servers

    Posted Nov 12, 2010 12:01 PM

    Create the managment server list on the old machine or the new machine?



  • 6.  RE: Moving to New SEPM and New SQL Servers

    Posted Nov 12, 2010 12:05 PM

    old machine has all the info, so u need to create on it.



  • 7.  RE: Moving to New SEPM and New SQL Servers

    Posted Nov 12, 2010 12:08 PM

    You would need to create the new server management list on the new server once, as described above by John, the clients have been moved over to the new server.

    Once this is accomplished, you can go ahead and create the second new server and follow the steps John mentionned above again and that will create your replication partnership between your 2 new servers.

     

    Cheers