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 upon the version of the SEPM which manages them. This includes managed clients that receive content from Group Update Providers (GUPs) and managed clients that update using LiveUpdate instead of connecting to a SEPM. Newer versions of SEPM receive the update before older versions. The version of the clients does not matter.
- Example: 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.6 SEPM, they will receive the new definitions at the same time, and before any clients managed by a 12.1.5 SEPM. Note: The versions of the SEPM used in the previous example are for example purposes only and do not necessarily reflect the SEPM version used in staged rollouts.
- Unmanaged clients do not receive staged content. These clients receive content only when it is released to all clients.
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.
Imported Document Id