Symantec endpoint definitions not updating on manager

Traditional signature and heuristic file scanning engines form the backbone of Symantec’s security solutions; these engines use dozens of techniques to scan files for both known as well as unknown threats.

The desktop workstation is configured the exact same way as every other desktop workstation that I've pushed out the SEP client to, but it's the only one that will connect to the SEP Management Console successfully.If you choose to participate, the online survey will be presented to you when you leave the Technet Web site. Filed under: Symentec Related — Tags: Antivirus And Antispyware Protection, SEPM 11.0, Symantec Endpoin Protection. M]to protect our clients and servers from Virus / Spywares / and Network Threats.After few minutes , it will automatically push the definition to SEPM console and it will be distributed to clients in few minutes, All of my clients (100 ) took about 20 minutes to update. I have Symantec Endpoint Protection Manager installed on a Windows Server 2008 R2 machine and I've attempted to push the SEP client out to Windows 7 workstations on my domain.If the definitions on the SEP client and SEPM server are less than 24 hours old, the Antivirus and Antispyware policy is likely configured to warn after definitions are one (1) day out of date.This is against best practices as new definitions are not made available immediately at midnight.Symantec Endpoint Protection (SEP) clients display warning messages about out-of-date virus definitions.The SEP client is utilizing the latest definitions provided by the Symantec Endpoint Protection Manager (SEPM).This issue can be resolved by ensuring that the virus definition policy used by affected clients provides enough time before warning about outdated definitions.The configured time should be no lower than the amount of time it takes all clients in the environment to receive updated definitions plus one day.