What is the error in the migration path we have choosen
Our present setup has SEPM 11.0 MR2 (Manager) and SEP 11.0 MR2 Clients.
Since we wanted to migrate the SEPM on a new server machine, and at the same time upgrade was also avaialble from Symantec, we have done the following.
#1. Install a new SEPM 11.0 MR4 MP2 on a new physical server machine.
#2. Old SEP continues to run on the old machines.
#3. Generated the new EXE from a MR4 MP2 console, and tried to install on couple of machine.
Till this time out of the 100 machines we have, we could successfully install the first 5 machines.
Can anyone tell me is this way of migration correct?
Now, one of the problem we faced on the client machine was...
#1. When we install SEP Client of a newly setup Win XP SP2 client, the SEP 11.0 MR4 MP2 client get installed correcly.
#2. However, when we run the SEP 11.0 MR4 MP2 EXE on the SEP 11.0 MR2 machine, the installation happens succefully, the Green Dot also comes, however the SEP 11.0 MR4 MP2 clients get connected to SEPM 11.0 MR2 (i.e. old one)
I am not very sure what is going wrong, but we need some assistance.
Tejas
Comments
Hi, As per the release
Hi,
As per the release notes this maintenance pack cannot be installed over any versions of Symantec Endpoint Protection or Symantec Endpoint Protection Manager prior to MR4. It must be installed over Maintenance Release 4 (MR4), (MR4-MP1), or (MR4-MP1a). Therefore the upgrade path ideally would be from MR2 to MR4 and then to MR4 MP2.
Once your SEPM is upgraded then you can use the following option.
Thanks & Regards Sandip C Sali
There are 4 ways in which we
There are 4 ways in which we can move SEPM from one server to another.
1. Disaster Recovery
2. Move SEPM form one server to another with the same ip address
3. Replication
4.Clean install on the new server and then replace the sylink.
1. Disaster Recovery :
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007082112135948
2. Move SEPM form one server to another with the same ip address
http://service1.symantec.com/support/ent-security.nsf/docid/2008031204405448
3. Replication : Add a replication partner to the old SEPM. Stop all SEPM service on the old SEPM so that all the cleints move to the new SEPM, then Uninstall the old SEPM
4.Clean install on the new server and then replace the sylink.: Uinstall SEPM from the old server. Install SEPM on the new server and replace the sylink using sylink replacer: Now in your senario since both the SEPM are running this is causing the issue.
What you had to while creating the pacakge you had to clear the logs and commuinaction settings
Title: 'How to restore/retain client-server communication using custom installation settings without having to use the sylink drop tool.'
Document ID: 2008052008163148
> Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2008052008163148?Open&seg=ent
Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)
It is not recommned to
This migrtaion path is not supported.
Symantec Endpoint Protection 11.0.4202 (MR4 MP2) can migrate seamlessly over the following:
Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)
Would you like to reply?
Login or Register to post your comment.