Solved! Go to Solution.
Hello @wimme ,
Thank you for writing, I would like to add that the Exclusion arguments of specific files/folder or process would remain the same and should work as seen on both VSE and ENS. However, there are certain changes that we would need to look at the comparison of the policy itself when we migrate from VSE to ENS
I am adding the following documents which would shine more information regarding the Merging of the policies and also comparison
• How policies are merged during migration
https://docs.mcafee.com/bundle/endpoint-security-migration-guide-windows/page/GUID-F928CE48-0D0B-4A9...
• Merging specific to OAS scan settings
https://docs.mcafee.com/bundle/endpoint-security-migration-guide-windows/page/GUID-93FDE92A-B2B2-486...
That being said, We do not have a specific article that could validate whether the exclusion placed is working as expected, however, I can think of using McAfee Profiler which would show us the list of process and files that the ENS would scan and the expectation is to not see the files/folders or process for MSME is excluded from scanning
About McAfee Profiler:
What is Profiler?
Profiler gathers statistics from systems that show how on-access scan is affecting the CPU. Profiler captures top files and processes that on-access scan accesses. Based on the data collected, administrators can decide if they want to exclude a file or a process from scanning to reduce the impact on the system.
How do I obtain the latest Profiler version?
Log on to the ServicePortal (https://support.mcafee.com), click the Tools tab, and scroll down to find the McAfee Profiler tool.
Please refer to the article: KB69683 which show more details about the usage. I guess this would help you achieve the concern
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!
Hitesh
Hello @wimme ,
Thank you for writing, I would like to add that the Exclusion arguments of specific files/folder or process would remain the same and should work as seen on both VSE and ENS. However, there are certain changes that we would need to look at the comparison of the policy itself when we migrate from VSE to ENS
I am adding the following documents which would shine more information regarding the Merging of the policies and also comparison
• How policies are merged during migration
https://docs.mcafee.com/bundle/endpoint-security-migration-guide-windows/page/GUID-F928CE48-0D0B-4A9...
• Merging specific to OAS scan settings
https://docs.mcafee.com/bundle/endpoint-security-migration-guide-windows/page/GUID-93FDE92A-B2B2-486...
That being said, We do not have a specific article that could validate whether the exclusion placed is working as expected, however, I can think of using McAfee Profiler which would show us the list of process and files that the ENS would scan and the expectation is to not see the files/folders or process for MSME is excluded from scanning
About McAfee Profiler:
What is Profiler?
Profiler gathers statistics from systems that show how on-access scan is affecting the CPU. Profiler captures top files and processes that on-access scan accesses. Based on the data collected, administrators can decide if they want to exclude a file or a process from scanning to reduce the impact on the system.
How do I obtain the latest Profiler version?
Log on to the ServicePortal (https://support.mcafee.com), click the Tools tab, and scroll down to find the McAfee Profiler tool.
Please refer to the article: KB69683 which show more details about the usage. I guess this would help you achieve the concern
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!
Hitesh
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA