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:
The beta version of this product is available for use until the beta product license expires on December 31, 2010.
New and updated features in the VirusScan Enterprise 8.8 software release.
The VirusScan Enterprise 8.8 software release caches previously scanned files in a common location where the software always checks before scanning files. This cache reduces duplicate file scanning and improves performance.
This release provides support for all Windows Office 2010 applications. Specifically adding on-access scanning of Microsoft Outlook 2010 email and attachment files.
ScriptScan exclusion allows you to add the URLs of trusted scripts from known safe websites as white lists for VirusScan Enterprise 8.8. These ScriptScan exclusions reduce scanning and improve performance. This user interface feature is available in ePolicy Orchestrator 4.0, and greater, plus the VirusScan Console. Previously these excluded URLs required manual registry editing.
Known issues in this release of the software are described below.
McAfee VirusScan Enterprise services will not start if UNC shares are included in the environment PATH.
There is a know issue when upgrading from VirusScan Enterprise 8.7i to VirusScan Enterprise 8.8 when Microsoft Outlook is open during the upgrade. McAfee recommends you close Microsoft Outlook before installation of VirusScan Enterprise 8.8. (611045)
The Policy Migration tool (ePOPolicyMigration.exe) upgrades VirusScan Enterprise polices and tasks from an earlier version of VirusScan Enterprise. This tool runs only one time per server. If you have both the VirusScan Enterprise 8.5 extension and the 8.7 extension installed on the same server, you must choose whether to upgrade policies and tasks from VirusScan Enterprise 8.5 or 8.7. You cannot upgrade both.
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: When you run the ePOPolicyMigration.exe command from the command line, add the /PASSWORD switch and the SQL administrator password. For example, type: [path]\epopolicymigration.exe /password=sql_admin_password
See the Migrating the ePolicy Orchestrator policies section of the McAfee VirusScan Enterprise 8.8.0 Installation Guide. It describes how to use the ePolicy Orchestrator /PASSWORD switch in the command line. (611047)
If the VirusScan Enterprise 8.8 extension is already checked in then this error is actually caused by bad password access to ePolicy Orchestrator. See the Migrating the ePolicy Orchestrator policies section of the McAfee VirusScan Enterprise 8.8.0 Installation Guide. It describes how to use the ePolicy Orchestrator /PASSWORD switch in the command line. (611046)
Workaround: Uninstall the failed product, restart the system, then reinstall the product.
NVIDIA® drivers might cause performance issues or system response failure. VirusScan Enterprise 8.8 might run at 100% CPU or cause the system to fail to respond when running on specified NVIDIA drivers. See KnowledgeBase articles KB614212 and KB65066 for more information about this issue. (388060)
Failure to access the repository is not logged in the VirusScan Enterprise 8.8 update log, but the failure 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 successfully completes, but the Update in progress dialog box appears when you run setup.exe /q RUNAUTOUPDATESILENTLY=TRUE from the command line. (399265)
Importing the Sitelist.xml file from the command line might fail. When you run 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.
To resolve this issue, 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, then it will produce a correct Sitelist.xml that can be imported by VirusScan Enterprise 8.8. (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 and the Remote Console feature uses the Remote Registry service.Workaround: Before starting the Remote Console feature, you must manually start the Remote Registry service on the remote system using the following:
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: Modify the registry values using the following process:
HKLM\SOFTWARE\McAfee\DesktopProtection, value to the following:
Name: bUseWscAVExe, Type: REG_DWORD, Data: 1
HKLM\SOFTWARE\Wow6432Node\McAfee\DesktopProtection, value to the following:
Name: bUseWscAVExe, Type: REG_DWORD, Data: 1
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. (546966)
To scan only the file type ÃbÃ, configure an exclusion using the wildcard characters ? or *. For example, configure an exclusion using Ãb? or Ã*.
Windows Action Center shows VirusScan Enterprise and the AntiSpyware Enterprise Module are turned off even when they are actually turned on. This will be addressed prior to release of VirusScan Enterprise 8.8. (592672)
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)
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 © 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.
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.
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.