Endpoint Protection

SEPM is currently installed on one server but needs to be migrated to another server (different hardware and OS, XP to Server 2008). How do I successfully migrate SEPM over (this would be a 11.0.3001 to 11.0.4202 migration)??

TIA

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

https://www-secure.symantec.com/connect/forums/move-sepm-another-server

adding to Vikram's comment, once you move server. You need to upgrade the SEPm to MR4 then to MR4 MP 2.

Follow the DR steps as well.

good luck.
Pete

Okay, so I didn't check the replies to this post before proceeding with the migration. I got impatient and simply uninstalled SEPM from the XP machine (the original server) and just installed SEPM on the 2008 server (the new server). The problem now is it looks like the clients are not linked to the new SEPM. As a test I tried to run Update Content on a client and I got an error saying some of the clients haven't connected to the server yet, they have to connect to the server first before I can run that command. This is weird because I was able to successfully deploy the latest SEP client version to all the clients (from this new server/SEPM installation).

Any ideas how to get the clients successfully linked to the new server?

Can you explain what is your current situation.

1.Did you install SEPM on 2nd servers as a replication partner of the first one ?
2.Total how many clients do you have ?
3.After deploying SEP are these clients showing up on the new SEPM console ?

Possible solutions.
1. Run Sylinkreplacer 
2. Read these documents carefully.

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

or

How to restore/retain client-server communication using custom installation settings without having to use the sylink drop tool.

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008052008163148?Open&seg=ent





 

1. I did NOT install SEPM on the 2nd server as a replication partner of the first one. I installed it as is, (i.e. standalone)
2. 13 clients
3. They are not showing up automatically. I added 3, stopped and tried to run Update Content on one of them and got the error.

Just stop the SEP service replace the sylink.xml files on your SEP clients with the sylink.xml from the new server.

On each SEP client
- Stop the smc.exe service
- Copy and over write the file called SyLink.xml in C:\Program Files\Symantec\Symantec Endpoint Protection\
- Start the smc.exe service

You can follow this KB article as well - Restoring communication to clients with a new Sylink.xml file

 Do not ADD clients..that will not work

Follow this doc
How to restore/retain client-server communication using custom installation settings without having to use the sylink drop tool.

service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008052008163148

Vikram - why would you reinstall the SEP client when you can simple replace the sylink.xml with the one from the new SEP manager?
That is complete overkill and only really worth doing if you have a need to upgrade the SEP client or things are really not working out for you.

Z

For 13 clients you can follow any option you want.
Either go the 13 computers replace the sylink.
Run sylink replacer 
Or deploy this modified package.

Its basically what an administrator feels easy or wants to do, for communication issues you have N numbers of ways of acheiving the same goal ..it depends which way you want to go with.

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008052008163148?Open&seg=ent

Worked [somewhat] beautifully! Thanks everyone, thanks Vikram!