Endpoint SWAT: Protect the Endpoint Community

 View Only
Expand all | Collapse all

Exporting SEP package from console- Vdef is 1MB big...

ThaveshinP

ThaveshinPJun 30, 2014 04:47 AM

  • 1.  Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 03:45 AM

    Found something strange this morning. Trying to export a package with full content - multiple files and the vdef files are 1MB big - this cant be right?

    SEP 12RU4MP1. Anyone else experiencing this issue?



  • 2.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 03:54 AM

    What's the total size to sep package ?

    How to export Symantec Endpoint Protection (SEP) client install packages without any definitions or package with Basic Content.

    Article:TECH178698  | Created: 2012-01-11  | Updated: 2012-07-28  | Article URL http://www.symantec.com/docs/TECH178698

     



  • 3.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 04:00 AM

    160MB full content included with all features except firewall.



  • 4.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 04:04 AM

    Normal SEP package size 400-500 MB,

    You can delete old package and again import

    How to manually import client packages into Endpoint Protection Manager (SEPM)

    Article:TECH122824  | Created: 2010-01-29  | Updated: 2014-01-28  | Article URL http://www.symantec.com/docs/TECH122824


  • 5.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 04:08 AM

    I know. Will first get the SQL DBA to restart DB and then thereafter reimport the package.



  • 6.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 04:23 AM

    I did the same thing in a lab and same results - has Symantec somehow changed the size of the defintions?



  • 7.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 04:25 AM


  • 8.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 04:47 AM

    Can anyone from Symantec investigate this.



  • 9.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 05:23 AM

    Virus defs size vary everyday. You can create a package with no Defs, then put the virusdef.zip file back in there

    How to add new Virus definitions from SEPM 12.1 to existing SEP 12.1 client install package

    http://www.symantec.com/business/support/index?page=content&id=TECH204910



  • 10.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 05:27 AM

    Same here, happnening to me too.  Also occurs exporting older client packages.

    Looks like a proper bug to me!  I find it quite amusing noone raised it earlier (other than the below thread that is):

    https://www-secure.symantec.com/connect/forums/installer-packages-are-missing-antivirus-signatures

    I guess in the meantime, we can worksround it by copying the full defs from "<Program Files>\Symantec\Symantec Endpoint Protection Manager\Inetpub\content" into the client installer folder and renaming as vdefs.zip.

    Note: For the correct defs, look inside the ContentInfo.txt file in the above location, as it will list which GUID corresponds to which defs (i.e. 32bit and 64bit vdefs).  Once you have the right one, just pick the subfolder with the latest definition date & revision and nab the full.zip file



  • 11.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 05:41 AM

    Console does not allow me to delete the client packages as it has the latest package already.



  • 12.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 05:43 AM

    How come only now - a "bug" - how will it get resolved? We used to export packages after we upgraded to the latest SEP version but now what has changed?



  • 13.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 05:54 AM

    As a fellow partner, I'm nto aware of any reason why this would suddenly start happening I'm afraid.

    Ruling out a stealth upgrade of some sort, I can only assume this is the result of some change to the way the defs are structured.



  • 14.  RE: Exporting SEP package from console- Vdef is 1MB big...
    Best Answer

    Posted Jun 30, 2014 11:22 PM

    Symantec is aware of this problem and will update this document when a solution becomes available.

     To work around this problem until it is fixed, see Manually updating the Virus and Spyware definitions content included with an Endpoint Protection client installation package, or use a basic content installation package and allow newly installed clients to download content from their configured source after installation

    Exported client packages with full content do not contain full Virus and Spyware Definitions content.

    Article:TECH222397  | Created: 2014-06-27  | Updated: 2014-06-30  | Article URL http://www.symantec.com/docs/TECH222397


  • 15.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jun 30, 2014 11:24 PM

    It's a bug:

    Exported client packages with full content do not contain full Virus and Spyware Definitions content.

    Article:TECH222397  |  Created: 2014-06-27  |  Updated: 2014-06-30  |  Article URL http://www.symantec.com/docs/TECH222397


  • 16.  RE: Exporting SEP package from console- Vdef is 1MB big...

    Posted Jul 11, 2014 12:58 PM

    Fixed:

    Exported client packages with full content do not contain full Virus and Spyware Definitions content.

    Article:TECH222397  |  Created: 2014-06-27  |  Updated: 2014-07-11  |  Article URL http://www.symantec.com/docs/TECH222397

     

    Solution

     
    This problem was resolved with an updated product catalog released to LiveUpdate on July 10, 2014. To resolve this problem, run LiveUpdate on affected Symantec Protection Manager computers.