3 Replies Latest reply: Mar 19, 2014 7:53 PM by yanl RSS

    Deploy VirusScan 8.8 via SCCM Task Sequence

    Superhoop

      Hi All,

       

      We are install VSE 8.8 P2 as part of the build for our Windows 7 workstations. Using SCCM and build as part of a Task Sequence. Other apps are installing in the expected time frame.

       

      All is well until the machine starts the update of the DAT. This takes around 30 minutes ! I understand it's 120mb but that's still a long time. Have tried different repositories but that doesn't make a difference. Normally on the network this would take around 2-3 minutes.

       

      The build is actually in W7 at the time of update and past PE build, It has spoken to ePO and pulled down the policy.

       

      Any ideas why this takes so long ?

       

      Thanks

      Superhoop

        • 1. Re: Deploy VirusScan 8.8 via SCCM Task Sequence
          yanl

          Hello Superhoop did you ever find the culprit? I'm having the same issue in SCCM 2012 R2 OSD Win 7 pushing VSE Patch 3 or Patch 4. As far as I can tell the issue is only happening on a single desktop. I can reproduce on that perticular desktop but as of yet all other desktops and VMs are ok??? The difference with this desktop is SDD and dedicated video card.

           

          Desktop is HP 8200 Elite

           

          Looking at the cC:\ProgramData\McAfee\DesktopProtection\UpdateLog.txt clearly shows a 30 min delay running mcupdate.exe

          • 2. Re: Deploy VirusScan 8.8 via SCCM Task Sequence
            Superhoop

            Hi Yanl,

             

            Our problem wasn't so much the delay but the actual DAT update taking ages ! We used super DATs for while and updated them in the sequence every thirty days as we found when it didn't have to pull the large 130mb+  it wasn't too bad.

            In the end we found if we point them to specific repositories the updates took only 5 minutes. Never figured out why some repositories were slow and some were not.

             

            Sorry I couldn't be more help.

             

            Is yours not actually starting the update for 30 minutes after the build? Haven't got a 'Run missed task' with a delay setting or something like that in the actual VSE update task ?

             

            Thanks

            Superhoop

            • 3. Re: Deploy VirusScan 8.8 via SCCM Task Sequence
              yanl

              Than you for replying. After doing some tests here are my findings; I ran the same task sequence on the same computer 3 times with the same result: 30 minutes downloading/installing avvdat-7380.zip. I ran the same task sequence on another computer of the same model and ssd. No issues. My last test was to delete the problematic device from ePO and bingo the update was fast.

               

              18/03/2014 4:39:16 PM NT AUTHORITY\SYSTEM Starting task: AutoUpdate

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Checking update packages from repository ePO_CIRB-VASA.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Initializing update...

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Verifying catalog.z.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Extracting catalog.z.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Loading update configuration from: catalog.xml

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM These updates will be applied if they are in the repository:  Engine, DAT, VSCANCEU1000, EXTRADAT1000, BOCVSE__1000, SUPERDAT1000, VIRUSCAN8800.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Downloading PkgCatalog.z.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Verifying PkgCatalog.z.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Extracting PkgCatalog.z.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Loading update configuration from: PkgCatalog.xml

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Verifying V2engdet.mcs.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Product(s) running the latest Engine.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Downloading PkgCatalog.z.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Verifying PkgCatalog.z.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Extracting PkgCatalog.z.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Loading update configuration from: PkgCatalog.xml

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Verifying V2datdet.mcs.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Downloading PkgCatalog.z.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Verifying PkgCatalog.z.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Extracting PkgCatalog.z.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Loading update configuration from: PkgCatalog.xml

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Starting DAT update.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Downloading DAT.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Downloading gdeltaavv.ini.

              18/03/2014 4:39:54 PM NT AUTHORITY\SYSTEM Downloading avvdat-7380.zip.

              18/03/2014 5:10:44 PM NT AUTHORITY\SYSTEM Pre-notifying for DAT update.