cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Level 10
Report Inappropriate Content
Message 1 of 7

VSE Debug Long Scan Times

Jump to solution

Our company runs a full scan after a DAT update each night. On our dev laptops this can take 10 hrs or more and is a real resource hog. Obviously things like .zip and .iso files cause issues but what I'm wondering is if there is a way to turn on some debug logging on the VSE agent to see exactly how long its taking on each stage and what files are causing long scan times?

2 Solutions

Accepted Solutions
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 7

Re: VSE Debug Long Scan Times

Jump to solution

Hello @shocko 

Please refer the below KB article for enabling the debug for McAfee Agent Non-Windows machine:

https://kc.mcafee.com/corporate/index?page=content&id=KB69542

If Using VSES check the below KB:

https://kc.mcafee.com/corporate/index?page=content&id=KB81934

Please do check Page 41 General Setting in Product Guide:

https://docs.mcafee.com/bundle/virusscan-enterprise-linux-v1-9-0-product/resource/PD24546.pdf

Was my reply helpful?

If you find this post useful, please give it a Kudos! Also, please don't forget to select "Accept as a Solution" if this reply resolves your query!

View solution in original post

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 7

Re: VSE Debug Long Scan Times

Jump to solution

Hello @shocko 

Thanks for your response.

I would like to inform you that we do have an Internal Article available and that cannot be discussed over here.

I would like to request you to please open a Service Request with Support Team to have a discussion over it.

Thanks for understanding.

Was my reply helpful?

If you find this post useful, please give it a KudosAlso, please don't forget to select "Accept as a Solution" if this reply resolves your query!

View solution in original post

6 Replies
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 7

Re: VSE Debug Long Scan Times

Jump to solution

Hello @shocko 

Please refer the below KB article for enabling the debug for McAfee Agent Non-Windows machine:

https://kc.mcafee.com/corporate/index?page=content&id=KB69542

If Using VSES check the below KB:

https://kc.mcafee.com/corporate/index?page=content&id=KB81934

Please do check Page 41 General Setting in Product Guide:

https://docs.mcafee.com/bundle/virusscan-enterprise-linux-v1-9-0-product/resource/PD24546.pdf

Was my reply helpful?

If you find this post useful, please give it a Kudos! Also, please don't forget to select "Accept as a Solution" if this reply resolves your query!

View solution in original post

Highlighted
Level 10
Report Inappropriate Content
Message 3 of 7

Re: VSE Debug Long Scan Times

Jump to solution

Apologies I should have stated these are Windows 10 1809 machines. Is there an option for windows?

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 7

Re: VSE Debug Long Scan Times

Jump to solution

Hello @shocko 

Thanks for your response.

I would like to inform you that we do have an Internal Article available and that cannot be discussed over here.

I would like to request you to please open a Service Request with Support Team to have a discussion over it.

Thanks for understanding.

Was my reply helpful?

If you find this post useful, please give it a KudosAlso, please don't forget to select "Accept as a Solution" if this reply resolves your query!

View solution in original post

Highlighted
Level 10
Report Inappropriate Content
Message 5 of 7

Re: VSE Debug Long Scan Times

Jump to solution

Thanks. I'm an enterprise customer so I can check with support 😉

Highlighted
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 6 of 7

Re: VSE Debug Long Scan Times

Jump to solution

In my experience, long on-demand scan times are always the result of scanning large compressed files (eg, .JAR, .ZIP, .7Z, .CAB, self-extracting .EXE, etc.) -- as you have noted. To improve scanning speed, I might recommend excluding files in trusted locations that are >800+ MB, and those files that have not been modified >2+ yrs ago. Perhaps create a separate on-demand scan policy for developer's PCs that excludes scanning inside archives during the work week (and defer it until weekends), but perform more frequent daily in-memory scans. Identifying trusted developer tools and common build folders can also improve performance if using Low-risk Processes on-access scanning policies.  Hope this info helps.

Highlighted
Level 10
Report Inappropriate Content
Message 7 of 7

Re: VSE Debug Long Scan Times

Jump to solution

I agree! I was interested though if there was a way to debug this for an arbitrary user say , put the agent into debug mode so an admin could analyse the logs rather than the user looking around their system for those files. 

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community