How long will an old Symantec Endpoint Protection (SEP) engine receive compatible signature updates for, after a new version of the engine has been released?
Article ID: 261916
Updated On:
Products
Issue/Introduction
Engine updates implement new features and updates by updating drivers and other binary code. Symantec thoroughly tests new engine updates internally using test systems that mimic as wide of a variety of customer environments as possible, but it is not always possible to anticipate every possible interaction.
When a new engine is released, customers have the possibility to lock a specific engine in the Live Update policy, so that they can carry out tests and verifications before releasing the engine to all SEP clients in the environment
However, the definitions released for SEP components are "engine version - dependent" (where it applies as not all SEP components have engines) and they will continue to be released for the older engine for 2 weeks after the new engine has been released.
Environment
SEPM with LU content policy configured with locked engines
Cause
There is a hard limit of 2 weeks once the engine release has been completed. After 2 weeks, the old engine version will no longer receive new signature updates.
Resolution
Complete all tests and checks within 2 weeks period after a new engine is released, to avoid functionality issues with specific SEP components due to engine-definitions incompatibilities.
You could also avail of the Early Adopter System program which allows users to download pre-release Symantec Endpoint Protection (SEP) engines with updated protection technologies and features before they are generally available.
Additional Information
Feedback
