Dear all,

i want to move the SEPM from our 2003 Server to the 2012. I have done:

http://www.symantec.com/business/support/index?page=content&id=TECH104389&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1400657423990S2458B1mKwTVP92k9QlaLEvHR4zQ3bAks6Wws

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

but when i want ot restore the database on the new server i get this message. What i am doing wrong?

IP and Seervername will be different.

Both have the latest version installed which is available

Thanks a lot for your kind help

Failure when using 11.x disaster recovery files with Symantec Endpoint Protection Manager 12.1

Thanks James,

used this lionk already. no success

Hi,

If you using as per articles choose option 3.

SEPM server has a differenet IP and different hostaname.

If the new SEPM server has a different IP and host name, there are two alternatives:

1. Use replication to install a new SEPM and keep the policy the same with old SEPM. See "How to move Symantec Endpoint Protection Manager from one machine to another"

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

Note: Replication is an option, if you do replication and remove the old server that is the Primary SEPM, in future if you want to do replication you will not be able to do so.

2.Follow disaster recovery method & Create a new MSL.as per following

1. Follow "Best Practices for Disaster Recovery with Symantec Endpoint Protection" (see Related Articles below) to backup and reinstall SEPM on MACHINE_2
2. Log in to the old SEPM on MACHINE_1
3. Click Policies > Policy Components > Management Server Lists > Add Management Server List
4. Click Add> Priority and a new Priority would get added named as "Priority2"
5. Add MACHINE_1 under Priority 2 and add MACHINE_2 under Priority 1, and assign this New Management Server List to all the groups.
6. Clients will then move from old SEPM to new one gradually
7. Stop the "Symantec Endpoint Protection Manager" and "Symantec Embedded Database" service on MACHINE_1 to verify whether all client now report to the new SEPM on MACHINE_2
8. Once verified that all the clients are reporting into the new SEPM, and have moved away from the old one, proceed to the next step.
9. Uninstall SEPM from MACHINE_1

OR

Install a new fresh SEPM, then use the Sylink.xml file to establish the communication between new SEPM and the existing SEP clients with the help of Sylink replacer tool.

This option is effective if having limited number of clients in the network.

Helpful Publick KB Articles:

SEP 11

How to move Symantec Endpoint Protection Manager from one machine to another

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

SEP 12.1

How to move Symantec Endpoint Protection Manager 12.1 from one machine to another

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

all done. Still the Fuc§$%6 message appears.

have you take proper backup as per below articles

Symantec Endpoint Protection 12.1: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

yep

Same erro another thread

https://www-secure.symantec.com/connect/forums/out-memory-when-upgrade-sepm-11-12

I suggest you can raised support ticket.

• TECH58873 How to create a new case in MySymantec (formerly MySupport)

• HOWTO78022 FAQ - Symantec's New MySymantec Online Support Portal (formerly MySupport)

• HOWTO84096 MySymantec Entitlement Super User - How to view cases

Regional Support Telephone Numbers:

United States: https://support.broadcom.comhttps://support.broadcom.com">https://support.broadcom.com">(407-357-7600from outside the United States)

Australia: 1300 365510 (+61 2 8220 7111from outside Australia)

United Kingdom: +44 (0) 870 606 6000

Additional contact numbers: http://www.symantec.com/business/support/contact_techsupp_static.jsp

Are you able to extract the recovery zip fle and see what's inside?  The one from my test sepm contains the files shown in the attached screenie.  Does your one match, or are you trying to use a SEP11 one as suggested by James007?

If you cannot import the old certificate, then you're going to have to build this SEPM without it, and get the clients talking to this new SEPM by replacing their communications settings files using one of the methods described in the below article:

How do I replace the client-server communications file on the client computer?

You might also want to script this file replacement using the my post in the below threads:

https://www-secure.symantec.com/connect/forums/need-make-unmanaged-client-managed-client-must-be-done-remotely#comment-8676611
https://www-secure.symantec.com/connect/forums/sep-1107-sepm-1212-communication-update-package-fails#comment-8763371

Bit more background info on orpahned clients can be found in the below article:

Why do I need to replace the client-server communications file on the client computer?

YEP same Stuff

Hi,

With reference to the following article, verify you are doing right steps.

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

You have only one revoery file to restore?

Hi,

i hope i am doing the right steps!?!? Refering to symatec article

Backing up the database on Machine_1 -> old

try to install the new fresh SEPM on the machine_2 -> new

while using the option  on machine_2

-custom  configuration.....  &

-use a configuration fie. Here it stucks

Hi,

What's the version code of both SEPM? Do you have any other recovery file to restore?

12.1.4104.4130

Thanks for the update, could you take the database backup again on primary SEPM and try to restore.

will do, and report -fingerscross.

GREEEAT. AFTER 3rd time reinnstall backup restore it worked. Thanks a lot for your help.