Thank you for choosing this McAfee product. This document contains important information about the current release. We strongly recommend that you read the entire document.
|The option to exclude subdirectories is also supported.|
|•||Valid wildcards are question mark (?) for excluding single characters, and asterisk (*) for excluding multiple characters|
|•||Wildcards can appear in front of backslashes (\) in a path. For example, C:\ABC\*\XYZ matches C:\ABC\DEF\XYZ|
|•||An exclusion containing question mark (?) applies if the number of characters matches the length of the file or folder name. For example, the exclusion W?? excludes WWW, but does not exclude WW or WWWW|
|•||The syntax is extended to include a double asterisk (**), which means zero or more of any characters including backslash (\). This allows multiple-depth exclusions. For example, C:\ABC\**\XYZ matches C:\ABC\DEF\XYZ and C:\ABC\DEF\DEF\XYZ|
|•||Environment variables can be inserted into exclusion strings in order to reference system-dependent values at runtime, such as the “Program Files” folder|
|•|| Variables are indicated by enclosing the variable name in percent signs (“%”). For example, the folder name is %ProgramFiles%\MyData\ |
|•||An ePolicy Orchestrator administrator can import existing path exclusion policies from VirusScan Enterprise|
|•||The ePolicy Orchestrator administrator must export the path exclusion policies for the On-Access Default/High-Risk/ Low-Risk Processes Policy as an XML file, then import the XML files to the MOVE Multi-Platform client policy|
|•||While importing the XML files, there is an option to clear the existing exclusions|
|Existing duplicate entries are fixed so that data is not replicated.|
|McAfee Agent 4.8 is also supported.|
|•||Creating a new agent identifier each time a non persistent virtual image is started results in a duplicate Agent GUID. To avoid duplicate GUIDs, the agent can be installed in VDI mode on the virtual images.|
|•||Installing the agent in VDI mode de-provisions the virtual image every time it’s shut down and enables the McAfee ePO server to save the de-provisioned agents to its database.|
|•||2.6.0 to 2.6.2|
|•||2.6.1 to 2.6.2|
For known issues in this product release, refer to KnowledgeBase article KB77353.
|1||Issue — A blue screen occurs on some systems after the MOVE client is installed. (Reference: 837706 ) |
Resolution — Corrected a defect that was causing intermittent stack overflows.
|2||Issue — "ERROR: svc_socket.c: Failed to read ODS state" occurs in the MVServer Log. (Reference: 838600 ) |
Resolution — Reliance on the client MAC address for On-Demand Scan tracking resulted in an error when the client and server were in different subnets. As part of the initial heartbeat request, the client now passes a unique ID to the server that is used for On-Demand Scan tracking.
|3||Issue — Repeated On-Demand Scan starts are issued from the Offload Scan Server. (Reference: 835592 ) |
Resolution — If the entire On-Demand Scan occurred within the heartbeat interval, the scan complete event wasn't sent to the Offload Scan Server. This issue is now resolved.
McAfee provides the information you need during each phase of product implementation, from installation to daily use and troubleshooting. After a product is released, information about the product is entered into the McAfee online KnowledgeBase.
|1||Go to the McAfee Technical Support ServicePortal at http://mysupport.mcafee.com.|
Under Self Service, access the type of information you need:
Copyright © 2013 McAfee, Inc. Do not copy without permission.
McAfee and the McAfee logo are trademarks or registered trademarks of McAfee, Inc. or its subsidiaries in the United States and other countries. Other names and brands may be claimed as the property of others.