Thank you for using VirusScan Enterprise software. This document contains important information about this release. We strongly recommend that you read the entire document.
The VirusScan Enterprise 8.8 release uses the following:
New and updated features in the VirusScan Enterprise 8.8 software release.
Caches previously scanned files in a common location to reduce duplicate file scanning and improve performance.
This release supports all Windows Office 2010 applications, specifically adding on-access scanning of Microsoft Outlook 2010 email and attachment files.
ScriptScan exclusions, URLs of trusted scripts from known safe websites, can be easily added to reduce scanning and improve performance. This feature is available in ePolicy Orchestrator 4.0 or later, and in the VirusScan Console. Previously these excluded URLs required manual registry editing.
Known issues in this release of the software are described below.
The ePolicy Orchestrator Migration tool might fail to migrate the existing policies and tasks from an ePolicy Orchestrator Server that uses Windows NT authentication for ePolicy Orchestrator access. In some cases the ePolicy Orchestrator Migration tool needs to pass the SQL administrator password as a parameter for the ePolicy Orchestrator Migration tool.
Workaround: Run the ePOPolicyMigration.exe command from the command line, and add the /PASSWORD switch and the SQL administrator password. For example, type: [path]\epopolicymigration.exe /password=sql_admin_password
For information about using the ePolicy Orchestrator /PASSWORD switch at the command line see the McAfee VirusScan Enterprise 8.8.0 Installation Guide. (611047)
After successfully upgrading from VirusScan Enterprise 8.7 to VirusScan Enterprise 8.8 the ePolicy Orchestrator 4.5 System Details dialog box does not list VirusScan Enterprise 8.8 in the Installed Products row. (620509)
Workaround: Uninstall the failed product, restart the system, then reinstall the product.
NVIDIA® drivers might cause performance issues or system failure. VirusScan Enterprise 8.8 might run at 100% CPU utilization or cause the system to fail. See KnowledgeBase articles KB51688 and KB52367 for more information about this issue. (388060)
Running the VirusScan Enterprise 8.8 installer fails to completely remove all the CA Anti-Virus version 7.0 and 7.1 program directory structure and registry key entries.
Workaround: None. This is an issue with the CA Anti-Virus uninstall program. (625703)
On standalone client systems, VirusScan Enterprise 8.8 fails to complete the initial product update with Panda Anti-Virus 2008 also installed.
When you run VSESetup.exe and selected the option No, to not remove the Panda Anti-Virus 2008 software, at the last stage where VirusScan Enterprise 8.8 would perform the product update, the update dialog box might hang for 20 minutes or more.
Workaround: When you run VSESetup.exe, selected the option Yes to remove the Panda Anti-Virus 2008 software. (626009)
On an ePolicy Orchestrator managed client, if you run VSESetup.exe and select the option to remove detected anti-virus software, some Symantec anti-virus files, directories, and registry keys are left on the system.
Workaround: None. (629265)
Upgrading from VirusScan Enterprise 8.7i to VirusScan Enterprise 8.8 via ePolicy Orchestrator might cause the MSI installer (msiexec.exe) to trigger the Access Protection rule Common Standard Protection: Prevent termination of McAfee processes.
Workaround: None. This does not affect the installation and can be ignored. (635226)
This hard disk and memory requirement is particularly important for embedded and virtual systems where running the minimum system requirements is often the case. (625749)
Failure to access the repository is not logged in the VirusScan Enterprise 8.8 update log, but is logged in the McAfee Agent log. The default location of the McAfee Agent log is: <drive>:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\mcscript.log. (384749)
Silent update tasks performed from the command line still display the progress dialog box. The installation completes successfully, but the Update in progress dialog box appears when you run setup.exe /q RUNAUTOUPDATESILENTLY=TRUE from the command line. (399265)
When you run the command setup.exe CMASOURCEDIR="<drive>:\Documents and Settings\<username>\Desktop\" from the command line to install the product and import the Sitelist.xml file from the Desktop, the installation successfully completes, but fails to import the Sitelist.xml file.
Workaround: Use a Sitelist.xml file that was created by ePolicy Orchestrator agent 4.0. If the McAfee Agent 4.0 installation upgraded a previous installation of ePolicy Orchestrator agent 3.6.1, it produces a correct Sitelist.xml file that can be imported. (419467)
When using the Remote Console feature to connect to Windows Vista systems or later, you are unable to open Access Protection, Buffer Overflow, and Quarantine Manager dialog boxes for the remote systems and no error appears. This is because the Windows Vista and later systems do not automatically start the Remote Registry service required by the Remote Console feature.
Workaround: Before starting the Remote Console feature, manually start the Remote Registry service on the remote system using the following: (581439)When using the Remote Console feature to open Access Protection properties on a system with Windows Server 2008, it might take several minute to open the connection. (392825)
Workaround: Use these steps to restart the McAfee Task Manager service and reset the appearance of the Buffer Overflow Protection task status:
When you reopen the VirusScan Enterprise 8.8 console, the Buffer Overflow Protection status appears enabled. (638390)
When you try to move an infected file from one folder to another, within the same volume, the configured actions for "When a threat is found" are not performed on the source file, but the move is prevented. This is expected behavior for VirusScan Enterprise 8.8. For detailed information, see KnowledgeBase article KB70468. (633871)
If you run an on-demand scan from Microsoft Outlook 2010 and an email with malware is detected in the body of a message, the Junk E-mail Filter moves the message to the Junk E-mail folder. This is not expected behavior. The infected message should have been moved to the Quarantine folder.
Workaround: None. This is caused by the Junk E-mail Filter in Microsoft Outlook 2010. (631700)
When you run the CheckPoint pireg.exe utility the following error message appears:
mcavscv.dll does not exist
Workaround: To stop this error from appearing, install the Microsoft Visual C++ 2008 Redistributable Package. (629324)
In the User Account Control (UAC) window prompt if you make certain setting changes and click No the changes are still made. This issue only affects the following systems using Microsoft Outlook 2010:
Specifically, in these environments:
Workaround: None. This is a problem with the Windows UAC and there is no workaround. (627058)
Disabling on-access scanning does not disable ScriptScan. With VirusScan Enterprise 8.7 and earlier, if you disabled on-access scanning it would also disable the ScriptScan feature. With VirusScan Enterprise 8.8 if you disable on-access scanning ScriptScan continues to run.
Using Microsoft Outlook 2010, if you want to perform an on-demand scan on a selected folder only one item in the folder is scanned.
Workaround: To perform an on-demand scan on an entire Microsoft Outlook 2010 folder:
(624659)
With Microsoft Windows 2000 SP4, if you try to edit the AutoUpdate Repository list using the Tools | Edit AutoUpdate Repository List command in the VirusScan Console, the following error might appear:
Failed to read the repository list, Error = fffffffc
If the error appears it is because the SiteList.xml file is missing from the following path:
C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework
Workaround: Copy a SiteList.xml file from the McAfee Agent 4.0 installation package, or another location, to the path. (568699)
When you configure a drive to exclude from on-access scanning, use a UNC path, not a mapped network drive. For example, if you type Z:, for the mapped network drive in the Set Exclusions dialog box, the files in the mapped drive are not excluded from on-access scanning.
Workaround: To exclude a network drive from on-access scanning use a UNC path, not a mapped network drive. (546966)
To scan only the file type ÃbÃ, configure an exclusion using the wildcard characters ? or *. For example, configure an exclusion using Ãb? or Ã*.
(586207)
The McAfee email scanner for Lotus Notes does not use the Quarantine Manager to quarantine detected threats. Consequently, if you configure the email scanner's first action as Clean attachments or Delete attachments, the original version of the detected threat is no longer available for recovery or restoration. If you want the original version of the detected threat to be available after the action is taken on the detection, McAfee recommends setting the first action as Move attachments to a folder and to specify a quarantine folder. When this move action is enabled, the original detected threat is moved to the specified quarantine folder with the .MCM extension appended to the detection.
If you enable the Move attachments to a folder option on client systems you should always have the on-access scanner enabled so those files can not inadvertently be accessed by a user. (430862)
When running VirusScan Enterprise 8.8 on a system with Microsoft Windows Server 2008, the on-access scanner might fail to delete a detected file from a network shared folder. The on-access scanner’s ability to delete a detected file is not guaranteed on network file systems. In this case, if the detected file is not deleted, the file content is removed and the remaining file size is zero. (431158)
After localization of the McAfee VirusScan Enterprise 8.8 software Installation Guide, the information in the System requirements section was changed. The English language files include this change.
In Table 1: Minimum workstation requirements, the minimum RAM and processor requirements were changed in the following rows (changes shown as Bold text):
| |||||||||||||||||||||
After localization of the McAfee VirusScan Enterprise 8.8 software Product Guide and Help, the information in the Configuring general settings section was changed. The English language files include this change.
In each of the user interface consoles the following step has been modified to include a Note:
After localization of the McAfee VirusScan Enterprise 8.8 software Product Guide and Help, the information in the On-Access Scan Policies Help for the General tab was changed. The English language files include this change.
The following information was added to the Scan option:
The McAfee documentation is designed to provide you with the information you need during each phase of product implementation, from evaluating a new product to maintaining existing ones. Depending on the product, additional documents might be available. After a product is released additional information regarding the product is entered into the online Knowledgebase available on McAfee ServicePortal.
|
Use this task to go to the release notes and other product documentation for McAfee enterprise products.
COPYRIGHT
Copyright © 2010 McAfee, Inc. All Rights Reserved.
No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form or by any means without the written permission of McAfee, Inc., or its suppliers or affiliate companies.
TRADEMARK ATTRIBUTIONS
AVERT, EPO, EPOLICY ORCHESTRATOR, FOUNDSTONE, GROUPSHIELD, INTRUSHIELD, LINUXSHIELD, MAX (MCAFEE SECURITYALLIANCE EXCHANGE), MCAFEE, NETSHIELD, PORTALSHIELD, PREVENTSYS, SECURITYALLIANCE, SITEADVISOR, TOTAL PROTECTION, VIRUSSCAN, WEBSHIELD are registered trademarks or trademarks of McAfee, Inc. and/or its affiliates in the US and/or other countries. McAfee Red in connection with security is distinctive of McAfee brand products. All other registered and unregistered trademarks herein are the sole property of their respective owners.
LICENSE INFORMATION
License Agreement
NOTICE TO ALL USERS: CAREFULLY READ THE APPROPRIATE LEGAL AGREEMENT CORRESPONDING TO THE LICENSE YOU PURCHASED, WHICH SETS FORTH THE GENERAL TERMS AND CONDITIONS FOR THE USE OF THE LICENSED SOFTWARE. IF YOU DO NOT KNOW WHICH TYPE OF LICENSE YOU HAVE ACQUIRED, PLEASE CONSULT THE SALES AND OTHER RELATED LICENSE GRANT OR PURCHASE ORDER DOCUMENTS THAT ACCOMPANY YOUR SOFTWARE PACKAGING OR THAT YOU HAVE RECEIVED SEPARATELY AS PART OF THE PURCHASE (AS A BOOKLET, A FILE ON THE PRODUCT CD, OR A FILE AVAILABLE ON THE WEBSITE FROM WHICH YOU DOWNLOADED THE SOFTWARE PACKAGE). IF YOU DO NOT AGREE TO ALL OF THE TERMS SET FORTH IN THE AGREEMENT, DO NOT INSTALL THE SOFTWARE. IF APPLICABLE, YOU MAY RETURN THE PRODUCT TO MCAFEE OR THE PLACE OF PURCHASE FOR A FULL REFUND.