Symantec Endpoint Protection Manager Auto-Upgrade using RU6/RU6a Manager pushes full client instead of delta

Article:TECH137774  |  Created: 2010-08-14  |  Updated: 2012-02-24  |  Article URL http://www.symantec.com/docs/TECH137774
Article Type
Technical Solution

Product(s)

Subject

Issue



When using the auto-upgrade feature with Symantec Endpoint Protection Manager (SEPM) 11.0 RU6 or RU6a, a full .zip is pushed out to the client after importing packages using a setup.exe file.

When utilizing the auto-upgrade feature within the Symantec Endpoint Protection Manager 11.0 RU6 or RU6a, and a client package is imported using a setup.exe file rather than an .info file, the auto-upgrade package deployed will be a full.zip instead of a delta package.  The setup.exe file could be used from any of the \SEP, \SEPWIN64, \SNAC or \SNACWIN64 directories.  The deployment will be successful, and the clients will install and function correctly.  However, the network utilization will be greater than normally expected during the auto-upgrade deployment.  This does not occur using the Symantec Endpoint Protection Packages.

Auto-upgrade is configured in the Symantec Endpoint Protection Manager under Clients > Install Packages, or by using "Upgrade Groups with Package under Admin > Install Packages.

Once an affected client package has been deployed to a client, the next auto-upgrade installation from an impacted client deployment will be a full.zip.  Future auto-upgrades beyond the first one will be functioning as expected unless they too are imported using a setup.exe file.

To determine whether the client package has been imported using a setup.exe file, on the Symantec Endpoint Protection Manager, browse to %Program Files%\Symantec\Symantec Endpoint Protection\Inetpub\ClientPackages.  There will be sub-directories for each client package (32-bit and 64-bit) for each client version uniquely identified by a hexadecimal GUID.  Inside each client package directory GUID there is a folder named full, and a file named full.zip.  Affected packages from imports using a setup.exe will yield a full.zip that is approximately twice as large as expected (for example, a RU6 client package would appear as approximately 250MB instead of 125MB).


Cause



This is caused by importing a client package using any setup.exe file into the RU6 or RU6a Symantec Endpoint Protection Manager.  This is not an issue with any previous or future builds of Symantec Endpoint Protection Manager.

 


Solution



If you are using RU6, but have not imported any client packages
To import packages into Symantec Endpoint Protection Manager 11.0 RU6 or RU6a, use the .info files that are provided in the \SEPM\Packages directory on the CD Layout.  For further information on importing packages using the .info files, see the article How to import client install packages manually into the Symantec Endpoint Protection Manager.

If you want to import packages using a setup.exe file, you must upgrade to RU6 MP1 Symantec Endpoint Protection Manager first in order to avoid this problem.

If you have imported packages into RU6 or RU6a Symantec Endpoint Protection Manager
You can remove the old packages under Admin --> Install Packages --> Client Install Packages.
Notes

  • You cannot remove the latest packages, only older packages.  If you need assistance removing the latest package, please contact Symantec Technical Support.
  • Do not remove any packages that are actively used within your environment. When you use the "Auto-Upgrade" feature, if the server has both the clients' old packages, plus the clients' new package, it can create a delta file that is much smaller than the original package. It then sends this delta file to all the clients instead of the original package. If you delete the old client packages from the database, this delta cannot be created and the whole package is deployed.

 

Brazilian-Portuguese: http://www.symantec.com/business/support/index?page=content&id=TECH153984&locale=pt_BR



Legacy ID



2010081217202548


Article URL http://www.symantec.com/docs/TECH137774


Terms of use for this information are found in Legal Notices