Support more SEP 12.1 Client Migration Paths
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.