Migrating VirusScan Policies to ENS

[Sohel]

I'm trying to move my VSE policies to ENS, I noticed all my policies are not migrating.

below is an example of some of  my low-risk processes in VSE

many of them are missing or didn't migrate after policy migration (Endpoint Security Threat Prevention \On-Access Scan\Low Risk:

 

any thoughts?

[AdithyanT]

Hi @Sohel 

Thank you for your post. I am afraid this one really requires a Service Request to investigate setting by setting to understand what is missed and what is not.

Nevertheless, I would like to give a try. To begin with, I am unable to correlate the 2 pages you have given. One seems to correspond to Low risk processes from VSE policy and the other screenshot seems to be from Exclusions under Endpoint Security.

If you are looking for the list of High risk and Low Risk processes under ENS On Access Scanning Policy, I would suggest looking under Process settings where each process is listed down along with the process type (High Risk/Low Risk) on the side.

Can you compare them and confirm the same? I have personally not used the migration assistant tool, but I am happy to try it out for you if you are not able get the relevant processes listed as stated above.

Of course, form a very general perspective, I would also request you to have this document handy.

I sincerely hope this is helpful atleast to begin with!

[Thussain]

Endpoint Security optimizes and consolidates legacy products into an integrated, eɝcient new platform. In addition to new and enhanced features that leverage the latest developments in security technology, a new McAfee Endpoint Security Platform (also known as McAfee Endpoint Security Common) module centralizes the shared protection features so they are easily accessible by all product modules. As a result, some of the policy
settings you are familiar with in legacy products have changed.

The Endpoint Migration Assistant ensures that the settings in your legacy policies are moved to the correct policies in Endpoint Security. In some cases, they are merged with other Endpoint Security settings, and in others, new default settings are applied to support updated technologies.

• New and revised categories reflect new and shared features.
• New settings represent new functionality.
• Some settings are removed, moved to a di΍erent category or policy, or merged with settings for other
features.
• Some settings for multiple operating system platforms can be migrated to separate single-platform policies
or one multi-platform policy.
• Settings shared by multiple product modules and features are moved to the Options policy in the Common
module.
• In some cases, settings are duplicated in multiple policies for use by functionality that is split across
modules.

You may also refer to page 7,8 and 9 from the below link 

https://kc.mcafee.com/resources/sites/MCAFEE/content/live/PRODUCT_DOCUMENTATION/27000/PD27567/en_US/...

[Sohel]

I noticed policy migration only copies what is listed under 'workstation' (in 'low-risk' VSE policy), it doesn't move anything under the "server" list - not sure why?

(below is what is listed under workstation)

and here is what I have under server (under same policy):

[Thussain · Accepted solution]

Under Available Policies in the left pane, select policy categories for your products.
The legacy policies within those categories are listed on the right side of the screen

a If you select VirusScan Enterprise policies, the Workstation settings are listed by default. To display Server policy settings instead, click Edit, then select an option:
• Workstation settings
• Server settings
• Both Workstation and Server settings

b If a category contains multiple policies, select the name of the policy to migrate from the drop-down list that appears next to the category name.

c If settings in a selected policy are merging with policies from other categories, the Migration Assistant displays the other categories. For each of these categories:
• Select the name of the policy to migrate.
• If you don't want to migrate settings in that category now, select None. If you select None for all the merging categories, no new policy is created for these categories.