1 2 Previous Next 11 Replies Latest reply on Apr 1, 2012 5:57 PM by kmcin11

    VirusScan 8.8 failing authentication for client tasks after upgrade

    bccol

      I've deployed VirusScan 8.8 (currently in evaluation branch) from a deployment task in EPO to the machines in our office for testing before pushing it out to our remaining clients (60 servers and over 1700 workstations). The machines I've deployed to were previously running VSE 8.7 patch 4 but the scheduled tasks now fail on authentication after upgrading. I've installed the new extensions and migrated the 8.7 policies and tasks to 8.8 using the policy migration tool before deploying 8.8 to our machines.

       

      The only way it seems to get VSE 8.8 working properly and to run scheduled tasks is by removing 8.7 manually, force the agent to send and collect properties so it then deletes our self-created scheduled tasks, reboot the machine and then install 8.8 from the setupvse executable. It seems if we install 8.8 directly over 8.7 (by deployment or by running the setup.exe) the scheduled tasks will not run as they fail on authentication. I've tried re-entering the Windows authentication information into the migrated 8.8 client tasks in the system tree but this has had no effect. The Windows account we have specifically for EPO use is not being locked out either and the schedules for previous versions we are still using are running fine along with EPO server tasks.

       

      We are using EPO version 4.5 patch 1, our agent version is 4.5.0.1270 and our client PCs are running Windows XP Pro service pack 3.

       

      Thanks for any help.

       

      Message was edited by: bccol on 01/06/11 16:42:33 IST
        • 1. Re: VirusScan 8.8 failing authentication for client tasks after upgrade
          bccol

          I've tried updating to agent version 4.5.0.1810 (patch 2) but scheduled tasks are still failing on authentication after installing 8.8 directly over 8.7, again if I remove 8.7 first manually in then install 8.8 scans work properly. I have noticed when it fails it seems to be not using the network account I've specified it to in the client tasks. I've posted the scan log below, the top scan is with VSE 8.7 and the scan below that is failing to run after deploying VSE 8.8 to the machine.

           

           

          03/06/2011 09:41:09  Engine version                          = 5400.1158
          03/06/2011 09:41:09  AntiVirus   DAT version                 = 6365.0
          03/06/2011 09:41:09  Number of detection signatures in EXTRA.DAT = None
          03/06/2011 09:41:09  Names of detection signatures in EXTRA.DAT  = None
          03/06/2011 09:40:54 Scan Started FLK\svc.bcepo01 (managed) VSE 8.7 On-Demand Scan Idle
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Scan Settings
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Scan Archives     : Enabled
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Scan Mime         : Enabled
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Macro Heuristics  : Enabled
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Program Heuristics: Enabled
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Primary Action    : Clean
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Secondary Action  : Delete Files
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Apply Unwanted Program Policy : Enabled
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Primary Unwanted Program Action : Clean
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Secondary Unwanted Program Action : Delete Files
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Extension Option  : Scan All
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Scan Sub Folders  : Enabled
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Scan Boot Sectors : Enabled
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Scan Offline Files: Enabled
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Exclusions
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01 Scan Items
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01  Memory for rootkits
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01  Running processes
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01  All local drives
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01  Cookies
          03/06/2011 09:40:54 Scan Settings FLK\svc.bcepo01  Registry
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 Scan Summary
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 Processes scanned    : 5
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 Processes detected   : 0
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 Processes cleaned    : 0
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 Boot sectors scanned : 0
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 Boot sectors detected: 0
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 Boot sectors cleaned : 0
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 Files scanned        : 0
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 Files with detections: 0
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 File detections      : 0
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 Files cleaned        : 0
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 Files deleted        : 0
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 Files not scanned    : 1
          03/06/2011 09:41:27 Scan Summary FLK\svc.bcepo01 Run time             : 0:00:33
          03/06/2011 09:41:27 Scan Terminated FLK\svc.bcepo01 (managed) VSE 8.7 On-Demand Scan Idle
          
          Deployed 8.8 over 8.7, scan fails as below..
          
          03/06/2011 09:57:05  Engine version                          = 5400.1158
          03/06/2011 09:57:05  AntiVirus   DAT version                 = 6365.0
          03/06/2011 09:57:05  Number of detection signatures in EXTRA.DAT = None
          03/06/2011 09:57:05  Names of detection signatures in EXTRA.DAT  = None
           00:00:00 Scan Terminated FLK\SYSTEM Authentication failed
          

           

          If I remove 8.8 and then force the agent to collect and send props to remove the tasks first before rebooting the machine, once it's rebooted if I reinstall VSE 8.8, the scheduled tasks will now run. This is the case with upgrading from 8.7 as well when going up to version 8.8. It seems I have to reboot the machine after manually removing VSE and agent tasks to get 8.8 to run tasks properly once installed as below 8.8 will now run scheduled tasks.

           

          03/06/2011 10:50:05  Engine version                          = 5400.1158
          03/06/2011 10:50:05  AntiVirus   DAT version                 = 6365.0
          03/06/2011 10:50:05  Number of detection signatures in EXTRA.DAT = None
          03/06/2011 10:50:05  Names of detection signatures in EXTRA.DAT  = None
          03/06/2011 10:50:05 Scan Started FLK\svc.bcepo01 (managed) VSE 8.8 On-Demand Scan Idle
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Scan Settings
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Scan Archives     : Enabled
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Scan Mime         : Enabled
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Battery deferred scan : Disabled
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Full Screen deferred scan : Disabled
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 User deferred scan : Disabled
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 System Utilization : Low
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Peristent Scan Cache : Enabled
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 ODS Uses Cache : Enabled
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Macro Heuristics  : Enabled
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Program Heuristics: Enabled
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Primary Action    : Clean
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Secondary Action  : Delete Files
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Apply Unwanted Program Policy : Enabled
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Primary Unwanted Program Action : Clean
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Secondary Unwanted Program Action : Delete Files
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Extension Option  : Scan All
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Scan Sub Folders  : Enabled
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Scan Boot Sectors : Enabled
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Scan Offline Files: Enabled
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Exclusions
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01 Scan Items
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01  Memory for rootkits
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01  Running processes
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01  All local drives
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01  Cookies
          03/06/2011 10:50:05 Scan Settings FLK\svc.bcepo01  Registry
          
          • 2. Re: VirusScan 8.8 failing authentication for client tasks after upgrade
            Laszlo G

            I don't remeber where I saw this (I think somewhere in this forum) but someone reported that VSE 8.8 could not launch ODS with authentication through ePO because it doesn't work so it must be a product bug

            1 of 1 people found this helpful
            • 3. Re: VirusScan 8.8 failing authentication for client tasks after upgrade
              bccol

              Seems a bit temperamental as I have got it to work depending on how it's installed but not the way we can effectively deploy it system wide. We shall wait for a patch I guess and see if it gets resolved, shame as 8.8 does scan better than version 8.7 and we've seen an increase in system performance from it.

              • 4. Re: VirusScan 8.8 failing authentication for client tasks after upgrade
                mark.tizzard

                I am seeing the same issues with my ODS scan task failing with the error "authentication failed" - I'm testing right now to see what other work arounds are available, so far I've been able to create brand new ODS tasks and leave all parameters as default and the tasks runs successfully as far as I can tell. Its not completely conclusive as I don't remember if my test box was a fresh 8.8 install or an ePO upgrade from 8.7 but i am testing now to get some more conclusive evidence.

                 

                One thing that i will note is that those ODS tasks for 8.8 were auto generated by ePO so recreating them as new ones may do the trick.

                 

                We are using the following:

                 

                ePO 4.5 P4 HF1

                VSE 8.8

                McAfee Agent 4.5.1810

                 

                Mark

                • 5. Re: VirusScan 8.8 failing authentication for client tasks after upgrade

                  I was having the same issue, but mine was an easy fix. When setting up the task, under task tab I entered a domain admin login credentials to run the task. I spoke with a McAfee tech that told to leave it blank, save it, and wake up the agents and force a policy and task update. I'm no longer getting Authentication Failed on the clients.

                  • 6. Re: VirusScan 8.8 failing authentication for client tasks after upgrade
                    mark.tizzard

                    I will echo what sturner has posted - When I created new scan tasks and left the credentials blank it worked fine, I tested this in a few different scenarios and each time it was successful. Perhaps if you were using a service account or domain admin account before in the ODS task for VSE 8.7 when installing VSE 8.8 into ePO these tasks where automatically duplicated for VSE 8.8 based upon the VSE 8.7 ODS task, I guess these tasks fail now because VSE 8.8 has to use the system account to scan now?

                     

                    Not sure but leaving the credential area blank when creating ODS task did the trick

                     

                    Mark

                    • 7. Re: VirusScan 8.8 failing authentication for client tasks after upgrade

                      Glad it worked for you, happy networking.....

                      • 8. Re: VirusScan 8.8 failing authentication for client tasks after upgrade
                        adminfn

                        I had the same issue with a standalone install on a Windows Server 2003 which I upgraded from 8.7 to 8.8. The formerly working ODS job failed with the following log entry (german): "00:00:00          Scanvorgang beendet          AFN-K-S1\SYSTEM          Prüfung fehlgeschlagen". With version 8.7 I had scheduled the scan to run under the domain admin account. After removing these credentials from the tasks properties it finishes with no errors.

                        • 9. Re: VirusScan 8.8 failing authentication for client tasks after upgrade
                          rogerover

                          As a lowly desktop user, how do I resolve the subject problem on my desktop computer at home?

                           

                          My employer provides access to this software to install at home, but when I upgraded to 8.8 on my Windows 7 Ultimate SP1 computer at home, the VirusScan Console say my On-access Scanner is Disabled.

                           

                          In an attempt to resolve the problem,I tried to uninstall the only McAfee program that appears in Programs and Features (McAfee Agent). However, Windows Installer (c3c4b2.exe) says, "McAfee Agent cannot be removed because other products are using it."

                           

                          What now? (I don't expect that the overworked Help Desk staff at work will volunteer to stop by my house to troubleshoot this issue.)

                          1 2 Previous Next