Endpoint Protection

 View Only
  • 1.  Vdefs.zip

    Posted Mar 27, 2014 10:56 AM

    Hello,

    I'm extracting a RU4 package from the console for my SEP clients. First time I did it, vdefs.zip was about 350Mo, that matchs with what I can find in the Inetpub/content and the Whatsnew.txt inside the zip was at the good date.

    I extracted the same package another time and now the vdefs.zip is about 260Mo and the whatsnew.txt is marked september 2013! All tries I do now give me a package with a suxh vdefs.zip file !

    => how is that possible ?

    => The vdefs cannot be extracted from inetpub/content because not enough revisions kept for september 2013... Is that extracted directly from the database ?

    => Is there a log of the package creation where I can have information about the source files ?

    Thanks in advance for your help.

    Regards



  • 2.  RE: Vdefs.zip

    Posted Mar 27, 2014 11:14 AM

    AFAIK it would overwirte everytime new defs arrive, its like superseeded patches in windows.



  • 3.  RE: Vdefs.zip

    Posted Mar 27, 2014 11:24 AM

    Was it from the same created package?



  • 4.  RE: Vdefs.zip

    Posted Mar 27, 2014 11:36 AM

    yes. Doing the same export as the first one but now all provide a vdefs.zip file of sept.2013...

    Another thing I noticed is that the setup doesn't contain anumore the Iron*.zip files, EFAVTdefs.zip... but the files of the client are correct (RU4).

    I checked the temporary creation of the Full.zip during the export process. I could see the correct file used (360Mo) but when using this file to create the final vdefs.zip, only 250Mo... and sept.2013 again..

    Is there a log to check what happens ?

    regards



  • 5.  RE: Vdefs.zip

    Posted Mar 27, 2014 11:50 AM

    I did the test on a test server and I saw that the export package, during it's creation, used the 360Mo vdefs.zip file, and created a final 260Mo first. But after that, folder of export seems to be updated in order to add all missing files such as the Iron*.zip... and the vdefs.zip of 360Mo !

    So maybe a process during the export that cannot finalyze correctly the setup, even if result is success...