Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Migrating a group of SEPM 11.0 client on existing server to a new server with different IP and hostname

Created: 10 Dec 2012 • Updated: 11 Dec 2012 | 12 comments

Hi

 

Currently one of the customer is requesting solution how to migrate group of users on the existing server  to  a new server with different ip and hostname.  Please the existing server will still be used..

 

I have found this article.

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

 

Below is the step as i modifed a few the last few step. pls advise if it is able to work based on the steps. Tks

 

 

  1. Install Symantec Endpoint Protection Manager on New SG server

NOTE: The version installed to the new server must be the same version as on the old server. The new management console can be migrated to a newer version once the transition is complete.

       2.     In the Management Server Configuration Wizard panel, check Install an additional site, and then click Next

      3    In the Server Information panel, accept or change the default values for the following boxes, and then click Next

•Server Name

•Server Port

•Server Data Folder

   4.     In the Site Information panel, accept or change the name in the Site Name box, and then click Next

 

   5.     In the Replication Information panel, type values in the following boxes:

•Replication Server Name

The Name or IP address of MACHINE_1

•Replication Server Port

The default is 8443.

•Administrator Name

The Username used to log on to the old console.

•Password

The password used to log on to the old console.

   6.    Click Next

  7.      In the Certificate Warning dialog box, click Yes

  8.      In the Database Server Choice panel, do one of the following, and then click Next:

Check Embedded database or Microsoft SQL server (whichever database type you'd prefer to install), then complete the installation.

 9.  Log in to the new SEPM on new Server  and ensure that all the clients and policies have Migrated successfully.

10. Click Policies > Policy Components > Management Server Lists > Add Management Server List

11. Click Add> Priority and a new Priority would get added named as "Priority2"

12. Add old server under Priority 2 and add new server under Priority 1, and assign this New Management Server List to specific  groups SG

13 .Wait at least one replication cycle.

14. Once verified that specific group of  the clients are reporting into the new SEPM, and have moved away from the old one, proceed to the next step.

15. Delete the Replication Partner from new server  SEPM: Click on the Admin button | Under View Servers, Expand Replication Partners and select the partner to delete | Under Tasks, choose Delete Replication Partner | Type Yes when asked to verify deletion of the replication partner.

 

 

 

 

Comments 12 CommentsJump to latest comment

Mithun Sanghavi's picture

Hello,

Your Question - 

Currently one of the customer is requesting solution how to migrate group of users on the existing server  to  a new server with different ip and hostname.  Please the existing server will still be used..

Solution:

In your case, you simply want certain groups to be migrated from Existing Server to a new SEPM with different IP address and host name.

In other words, these clients would be reporting to the new Server only. Correct?

Incase of you want to migrate all groups, then in that case, the above steps would help.

Also, check this Thread with similar issue - 

https://www-secure.symantec.com/connect/forums/how-move-sepm-one-server-another-different-ip-address-and-host-name

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

npvice's picture

Yes,

Only certain IP address range  will be  assigned to the new server. Is there a way to select specific client to set the priority to the new server,

Pls advise Tks

 

 

Mithun Sanghavi's picture

Hello,

Since you need only certain IP address to be reporting to the Latest SEPM server, then I would suggest you not to follow the Steps provided above.

The Steps provided above are for Replication of 2 SEPM server where all the groups and the clients under them would start reporting to the Latest SEPM.

In your case, do you want these 2 SEPM's to replicate as well OR do you want these 2 SEPM's to work as individual SEPM's??

In case, you want them to work as individual SEPM, you can use the SylinkReplacer Tool for SEP 11.x, available on 

https://www-secure.symantec.com/connect/downloads/sylinkreplacer-tool-connecting-sep-clients-sepm

This Tool would replace the Sylink.xml from the client machines letting them report to the Latest SEPM server.

However in case, you want them to work as Replication SEPM, then you may change the MSL under Communication Settings so that the clients from specific groups may report to correct SEPM.

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

npvice's picture

Hi

 

Thanks fot your reply

Pls advise if we can install the new symantec 12.1 and apply the  SylinkReplacer Tool on the new server  for SEP 12 and can get work on the SEPM client runinng 11.0 or it has to be thje same version 11.x

 

Mithun Sanghavi's picture

Hello,

You could surely Install SEPM with the Latest Symantec Endpoint Protection Manager version 12.1.

However, here you would not be able to Replicate the 2 SEPM's as both are of different versions.

Replication would require both SEPM's of same version.

In case if these SEPM's are not Replicating then, then apply the SylinkReplacer Tool to the clients to report them to the Latest SEPM 12.1

NOTE: There is a different SylinkReplacer Utility Available for Symantec Endpoint Protection 12.1 (available only through Symantec Technical Support). However, in your case all the SEP clients are of version 11.x

Hope that helps!!

 

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

npvice's picture

Hi Mithun,

 

Does the SylinkReplacer utility able to carry out the folllowing setup ?  

 

Migration PC in three main group

               - Parent domain (e.g test.com)  but install in Singapore

                - Singapore sub-domain – pacific.test.com

                - Production PC in workgroup

Tks

npvice's picture

Hi

 

Pls advise the utility whether it can work workgroup as the basic requirement for this utility need a domain user to carried out this task.

 

Tks

Ashish-Sharma's picture

HI,

You can use syslink replace tool for workgroup envirement but provide local Administrator user name and password .

Thanks In Advance

Ashish Sharma

 

 

Ashish-Sharma's picture

Hi,

Check this artical

How to move SEPM from one server to another server

https://www-secure.symantec.com/connect/articles/hot-move-sepm-one-server-another-server

If you want to specify ip address range to assgin new server.

you can replace the sylink.xml file with help of sylinkreplacer tool.

download it from here, 

https://www-secure.symantec.com/connect/downloads/sylinkreplacer-tool-connecting-sep-clients-sepm

Thanks In Advance

Ashish Sharma

 

 

SameerU's picture

Hi

There could be 2 possible steps to perform the migration.
 
1.       Recommended or the best way:
 
Configure the second new server as a replication partner of the existing one. Then configure the “management server list to point the clients to the new server. Keep the setup for some time so that all the clients receives the policy and then delete the replication and de-commission the old server. Following this method will have no downtime and orphan clients.
 
Note: Following this method needs the server name to be different as well.
 
·         Reference Documents:
 
URL: http://www.symantec.com/docs/TECH105928
 
URL: http://www.symantec.com/docs/TECH104582
 
Note: Please follow the “Defining Management Server Lists” section. Remember you need to set up the new server as Priority 1.
 
2.        Disaster recovery Method:
 
Follow the normal Disaster Recovery Method to install the Symantec Endpoint Protection Manager on the new server. This method may lead into downtimes and orphan clients.
 
·         Reference documents:
 
URL: http://www.symantec.com/docs/TECH104389
 
URL: http://www.symantec.com/docs/HOWTO26644

Regards