About Endpoint Protection staged content rollouts
|Article:TECH206118|||||Created: 2013-05-10|||||Updated: 2014-10-06|||||Article URL http://www.symantec.com/docs/TECH206118|
In order to reduce the potential impact of unforeseen issues in certain content updates such as definition engines (Eraser engine, AV Engine, and so on), Symantec is implementing a system of staged rollouts for these updates. This document describes the concept of staged rollouts, and how clients and managers receive definitions during a staged rollout.
Staged rollouts are Symantec's way of slowing down the release of certain updates, so that in the unlikely event of problems with the updates, fewer computers are affected. This is implemented by updating Symantec Endpoint Protection Managers (SEPMs) of certain versions before other versions.
A staged rollout works as follows:
- Managed clients receive the new update based on the version of the SEPM. Newer versions of SEPM receive the update before older versions. This includes managed clients that use LiveUpdate either to the Symantec or a LiveUpdate Administrator 2.x (LUA 2.x) server, and clients that receive content from Group Update Providers (GUPs) The version of the clients does not matter; if a Symantec Endpoint Protection (SEP) 12.1.0 client and a SEP 12.1.1 client are both managed by a version 12.1.2 SEPM, they will receive the new definitions at the same time, and before any clients managed by a 12.1.1 SEPM.
- Unmanaged clients receive the new update based on the client version. Newer versions of the client receive the update before older versions.
- Roaming clients follow the pattern of managed clients when they update from a SEPM, but follow the pattern of unmanaged clients when updating from LiveUpdate.
Since most environments use a single version of SEPM (multiple SEPM versions in a single environment are not supported), staged rollouts should cause no visible effects in most cases.
Article URL http://www.symantec.com/docs/TECH206118