Symantec endpoint protection manager 12 clients not updating
Upgrading to the current version of Symantec Endpoint Protection involves the following steps, in order: Before you install the Symantec Endpoint Protection client, manager, and any administration upgrades, you should have a solid understanding of your network topology and create a streamlined plan to maximize the protection of your network during the upgrade.Best practices: Before you upgrade, you must manually stop the Symantec Endpoint Protection Manager service on every management server in your site.The upgrade to Symantec Endpoint Protection Manager 12.1.6 takes significantly longer than previous upgrades, if upgrading from a version older than 12.1.5.This article provides best practices for upgrading to the latest version of Symantec Endpoint Protection (SEP) 12.1.x. Note: For more information on upgrading to version 14, see Upgrade best practices for Endpoint Protection 14.A previous version of Symantec Endpoint Protection (SEP) 12.x or 11 exists on the network or on individual computers.You need to migrate to one of the following versions of Symantec Endpoint Protection 12.1.The over install process saves the client settings, and then upgrades the client to the latest version.Note: Clients that are Group Update Providers (GUPs) should be upgraded before other Endpoint Protection clients.
TEM managed clients should receive updates automatically from the server.Configure the necessary policies in your SEPM before the creation of the install package.This document does not cover the policy and group configuration.We'd like to implement some change at the OS or application level to throttle the traffic without needing some heavyweight Qo S deployment at 100s of offices.Ideally we would like to be able to throttle the amount of traffic used per client for SEP updates.
After you upgrade, the management server automatically starts the service.