Video Screencast Help

Support more SEP 12.1 Client Migration Paths

Created: 26 Apr 2013 | 4 comments
SMLatCST's picture
8 Agree
0 Disagree
+8 8 Votes
Login to vote

While it's a given that a SEPM upgrade to any given Maintenance Patch (MP) level must follow a given upgrade path, I've never understood why the SEP Client must adhere to these paths as well.

Since SEP12.1, part of the SEP Client upgrade process is that it pulls down all relevant files for the new client into a silo'd folder, and swaps these around on reboot.  As the complete files for the newer version are pulled down, I'd like to see more varied upgrade paths for clients.

As it stands, I've tested and successfully upgraded test clients from various versions to SEP12.1RU1MP1 and SEP12.1RU2MP1, while skipping past RU1 and RU2 respectively.  It seems to work fine, I'd like Symantec to support these client-side jumps, and include them as supported migration paths in the documentation.

This would greatly simplify upgrades and migrations and ensure easy, supported, implementation of the latest version of SEP.

Comments 4 CommentsJump to latest comment

Mithun Sanghavi's picture

Hello,

Your suggestion has been forwarded to the correct people.

Mithun Sanghavi
Associate Security Architect

MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

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

0
Login to vote
Mithun Sanghavi's picture

Hello,

Technically an MP can upgrade any version of the product.  However the reason we don’t support this is because of testing.  The MPs are smaller releases, we always smoke test them and we've never had an issue.  We don't block the migration path because we do have customers that opt to take the risk and do the migrations.  However, since we haven't certified them, we can't support them.

Hope that helps!!

Mithun Sanghavi
Associate Security Architect

MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

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

0
Login to vote
SMLatCST's picture

Hi Mithun,

That is consistent with my testing and is as I had surmised.  The purpose of this thread and the IDEA is to ask Symantec to support it.

Presumably, you must have tested upgrades direct to SEP12.1RU2MP1 from various older SEP versions, for the purposes of the below fix entry:

Migration from Symantec Endpoint Protection 11.0.5 or higher to Symantec Endpoint Protection 12.1 RU2 and removing Network Threat Protection causes network instability
Fix ID: 3063813
Symptom: When upgrading from a later version of Symantec Endpoint Protection with the firewall component installed to a Symantec Endpoint Protection 12.1 RU2 install package without the firewall, the network may not load upon reboot.
Solution: Updated the migration mechanism for removing Teefer3 components from prior Symantec Endpoint Protection versions during the firewall uninstall.

As these upgrades from older versions of SEP to 12.1RU2MP1 have been tested, then please support them.

0
Login to vote
RamaG's picture

I agree with SMLatCST, Symantec should support direct client upgrades to 12.1RU2MP1.

I tested this in our environment and pushed a 12.1RU2MP1 client to a 12.1RU1MP1 client. It worked (with a reboot). This is much better than staged upgrade, to RU2, then MP1, which involves multiple reboots and potential issues.

Large environments will definitely benefit from this.

+1
Login to vote