During the migration process to Trellix ENS, the Endpoint Migration Assistant adjusts the migrated settings in your target policies to address differences between the legacy product and the new product. Therefore, some of the target policy settings don't match your legacy settings.
Client tasks that are migrated
Custom scheduled On-Demand Scan and Restore From Quarantine client tasks are migrated to the Client Task Catalog.
These are multiple-instance tasks. Each instance of the source task migrates to a separate instance of the client task in Threat Prevention.
Workstation and server settings
In VirusScan Enterprise, policies include settings for servers and workstations. For Threat Prevention policies, you must specify which type of settings to migrate: Workstation, Server, or Workstation and Server. The default is Workstation.
If you migrate only workstation or server policies, you can migrate the other policies manually at a later time.
If you migrate both types of policies, the number of target assignments might increase, depending on your System Tree structure. If a group contains both workstations and servers, the policy assigned to the greatest number of systems is assigned to the group, and the policy assigned to fewer systems is assigned to individual systems within the group as needed.
Note
Best practice: To minimize the number of assignments, place workstations and servers in separate groups.
Quarantine folder
The path for the quarantine folder is limited to 190 characters, but VirusScan Enterprise allowed 256 characters. During client migration, if the migrated quarantine folder path contains more than 190 characters, the path automatically reverts to the default location, <SYSTEM_DRIVE>\Quarantine.
Access Protection port-blocking rules
Endpoint Security Firewall provides more advanced port-blocking capabilities than the predefined Access Protection rules for VirusScan Enterprise 8.8.
Important
Access Protection port-blocking rules, either predefined or user-defined, are not migrated. User-added inclusions and exclusions for predefined rules are also not migrated.
If you want to continue using legacy rules that don't migrate from VirusScan Enterprise, you can create firewall rules in Endpoint Security Firewall to replicate their behavior. You can create firewall rules to:
- Define the same behavior as one or more of the predefined Access Protection port-blocking rules.
- Block the same ports as one or more custom Access Protection port-blocking rules.
Self Protection settings
When you migrate Access Protection rules (except port-blocking rules):
- Self Protection settings move from the Access Protection policies to the Common Options policy.
- Self Protection is enabled by default, regardless of the legacy setting.
- User-defined exclusions configured for each legacy product module are migrated as global exclusions for Trellix ENS.
- User-defined exclusions for three predefined rules in the
Common Standard Protection category are migrated as global Self Protection exclusions in the
Common
Options policy:
User-defined exclusions for this legacy rule Migrate to the Self Protection exclusions for Prevent modification of McAfee files and settings Processes Prevent termination of McAfee processes Processes Prevent hooking of McAfee processes Processes Tip
Best practice: Review your exclusions after migration, then revise or remove them as needed. Also review exclusions configured for any third-party applications to access VirusScan Enterprise registry or file locations, because these locations have changed in Trellix ENS.
Exploit Prevention (Buffer Overflow Protection)
In Trellix ENS, Buffer Overflow Protection settings are renamed Exploit Prevention.
After migration, the protection level for Exploit Prevention is set to the default Standard Protection, which detects and blocks only high-severity buffer overflow exploits identified in the Exploit Prevention content file and stops the detected threat.
Tip
Best practice: Use this setting for a limited time only, then review the log file during that time to determine whether to change to Maximum Protection.
Scan exclusions for root-level folders
Threat Prevention supports the exclusion of root-level folders from on-access scan and on-demand scans if the path starts with wildcard characters such as "?" or '"/".
Threat Prevention supports the following exclusion patterns, and the Migration Assistant does not change them during migration:
- Environmental variables — Patterns that begin with % (for example, %systemroot%\Test\ )
- UNC paths — Patterns that begin with \\ (for example, \\Test )
- Full paths — Patterns that include an absolute drive designator (for example, C:\Test\ )
- Patterns that begin with **\
- Patterns that begin with a single wildcard character (for example, use ?:\test, *:\test, *\test, or \test to exclude C:\test, D:\test, and E:\test.
Migrating unsupported characters in exclusions
The Migration Assistant migrates exclusion rules in VirusScan Enterprise to Access Protection rules in Threat Prevention.
In exclusion rules, VirusScan Enterprise allows the semi-colon ( ; ) character to separate include and exclude processes. The Migration Assistant recognizes only the comma ( , ) character to separate include and exclude processes.
When you migrate an exclusion rule that uses ; to separate multiple include and exclude processes, the Migration Assistant migrates them as a single process. The result is that migrated policies do not contain all the exclusions that were in the original policy.
Example
In the source policy, two executable files are excluded. They are separated by a ; instead of a , character.
\users\*\AppData\Roaming\*.exe ; *\Documents and Settings\*Application Data\*.exe*The Migration Assistant does not recognize the ; character. It migrates both files as a single exclusion. As a result, the migrated policy does not exclude either file.
You can correct this issue in any of these ways:
- Before migration — Review source VirusScan Enterprise policies. Locate unsupported ; characters and change them to , before migrating.
- During manual migration — The Migration Assistant notifies you that one or more policies have unsupported characters. You have the opportunity to cancel the migration, revise the policies in VirusScan Enterprise, then begin manual migration again.
- After migration — Edit your migrated policies to replace each ; character with a , character.