This issue has been solved.

Best way to upgrade SEP from 12.1 RU1 MP1 to 12.1 RU2 MP1

Created: 25 Apr 2013 • Updated: 25 Apr 2013
RamaG's picture
Login to vote
-1 1 Vote

Hi,

We are upgrading SEPM and 3000+ clients from 12.1 RU1 MP1 to 12.1 RU2 MP1 .

I have read all the release notes for both RU2, and RU2-MP1.

We plan to upgrade the SEPM first, then clients.

Could someone who has done this before, please confirm my following understanding?

1. SEPM must be upgraded to 12.1 RU2 first, then upgraded to 12.1 RU2 MP1?

2. Clients must be upgraded to 12.1 RU2 first, then upgraded to 12.1 RU2 MP1? (resulting in two reboots)?

 

Thanks.

Rama

 

Quick Look Solution

Yes, that is the correct and

Yes, that is the correct and recommended way to go per best practice.

Upgrading or migrating to Symantec Endpoint Protection 12.1.2100 (RU2 MP1)

Article:TECH204449  |  Created: 2013-03-28  |  Updated: 2013-04-04  |  Article URL http://www.symantec.com/docs/TECH204449

 

Migration paths
Symantec Endpoint Protection 12.1.2100.2093 (RU2 MP1) can migrate seamlessly over the following:

 

Symantec Endpoint Protection 12.1.2015.2015 (RU2)

 

I've just successfully upgraded a small environment for a client. I would only caution that one bug was found which affects only XP machines when the firewall component is in use. It causes a lag in network copies. Multiple cases have been opened so far. You can see the thread here about it:

https://www-secure.symantec.com/connect/forums/slow-network-after-upgrading-endpoint-protection-1212-mp1from-previous-version

Filed Under

Comments

_Brian's picture
_Brian
Trusted Advisor
Certified
25
Apr
2013
SOLUTION

Yes, that is the correct and

Yes, that is the correct and recommended way to go per best practice.

Upgrading or migrating to Symantec Endpoint Protection 12.1.2100 (RU2 MP1)

Article:TECH204449  |  Created: 2013-03-28  |  Updated: 2013-04-04  |  Article URL http://www.symantec.com/docs/TECH204449

 

Migration paths
Symantec Endpoint Protection 12.1.2100.2093 (RU2 MP1) can migrate seamlessly over the following:

 

Symantec Endpoint Protection 12.1.2015.2015 (RU2)

 

I've just successfully upgraded a small environment for a client. I would only caution that one bug was found which affects only XP machines when the firewall component is in use. It causes a lag in network copies. Multiple cases have been opened so far. You can see the thread here about it:

https://www-secure.symantec.com/connect/forums/slo...

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

RamaG's picture
RamaG
Partner
Accredited
25
Apr
2013

Thank you Brian81, very

Thank you Brian81, very helpful indeed!

We are still running a large population of XP machines, which will be migrated to Windows 7 eventually.

By the looks of it, Win7 seems unaffected by this upgrade.

What I am concerned is by the fact that the client needs to be upgraded twice! To RU2 first, then to MP1. Or uninstall the previous version, then install new version?

This is hardly seamless!. Has anyone tested direct upgrade of client to RU2MP1 and does Symantec support that path?

 

 

_Brian's picture
_Brian
Trusted Advisor
Certified
26
Apr
2013

Similar thread here, check

Similar thread here, check Mithun Sanghavi's comment regarding your question. It does need to go in order per migration path.

https://www-secure.symantec.com/connect/forums/sep...

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

SMLatCST's picture
SMLatCST
Partner
Accredited
26
Apr
2013

As per my thread which Brian

As per my thread which Brian kindly linked, my own testing shows that client upgrades direct to RU2MP1 (skipping past RU2 itself) do usually work, but are currently not supported by Symantec.

If you feel it'd be beneficial to be able to upgrade directly to SEP12.1RU2MP1 on the client side, the please pop in a vote for my IDEA below:

https://www-secure.symantec.com/connect/ideas/support-more-sep-121-client-migration-paths

As it stands, my current recommendation is to use the Symantec Management Platform (or other similar software management solution) to remove the old SEP Client and install the new one in order to circumvent the stepped process.

RamaG's picture
RamaG
Partner
Accredited
01
May
2013

Update: Successfully upgraded

Update:

Successfully upgraded the two 12.1RU1 MP1 SEPMs with a remote SQL database, and the DR SEPM with an embedded database to 12.1.RU2 MP1 as per the best practices without any incidents.

We then went ahead and pushed the RU2MP1 client to an existing Win7 RU1MP1 client, and it worked (needed a reboot). I agree with SMLatCST that a direct upgrade of client should be supported by Symantec.

Thanks all.