cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
McDuff
Level 10
Report Inappropriate Content
Message 1 of 3

On-Access Scan Settings for MOVE 4.6 Client vs VirusScan 8.8 on SVM - Which takes precedence?

Jump to solution
Greetings I'm trying to understand how VirusScan settings on the SVM and MOVE client settings interact. Given VirusScan on the SVM server has various on-access scan settings configured (e.g. scan on read/write, exclusions etc) and the MOVE client on the client VM itself has similar on access scan settings settings, just wondering how these two settings interact, and which takes precedence in the event of a conflict? For instance, let's imagine: - VirusScan on SVM server is configured to scan only on write, and has a file type of .xyz excluded - The MOVE client on the virtual desktop is configured to scan only on read, and has a file type of .abc excluded. What's the behavior? Will files be scanned on read or write? Will .xyz files be scanned? Will .abc files be scanned?
1 Solution

Accepted Solutions
jsam McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 3

Re: On-Access Scan Settings for MOVE 4.6 Client vs VirusScan 8.8 on SVM - Which takes precedence?

Jump to solution

The products and policies are separate. The MOVE SVM service offloads scan activity to the underlying VSE/ENS product but will use its own policy settings such as scan archive files etc when doing so.

Best practice is to add mvserver.exe to ENS/VSE (as appropriate) low risk process list and disable scan read/write for this process group so there is no concern that the host AV will be taking an interest in Move client files being scanned under X:\McAfee\MOVE AV Server\scanfiles\* on the SVM.

 

 

View solution in original post

2 Replies
jsam McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 3

Re: On-Access Scan Settings for MOVE 4.6 Client vs VirusScan 8.8 on SVM - Which takes precedence?

Jump to solution

The products and policies are separate. The MOVE SVM service offloads scan activity to the underlying VSE/ENS product but will use its own policy settings such as scan archive files etc when doing so.

Best practice is to add mvserver.exe to ENS/VSE (as appropriate) low risk process list and disable scan read/write for this process group so there is no concern that the host AV will be taking an interest in Move client files being scanned under X:\McAfee\MOVE AV Server\scanfiles\* on the SVM.

 

 

View solution in original post

McDuff
Level 10
Report Inappropriate Content
Message 3 of 3

Re: On-Access Scan Settings for MOVE 4.6 Client vs VirusScan 8.8 on SVM - Which takes precedence?

Jump to solution

Thank you, that's helpful.  It would be nice if this information could be added to the MOVE documentation.

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