Release Notes for McAfee® AntiSpyware Enterprise Module 8.0 and 8.5 for ePolicy Orchestrator® 4.0

Thank you for using AntiSpyware Enterprise Module software. This file contains important information regarding installing and managing AntiSpyware Enterprise Module 8.0 and 8.5 with ePolicy Orchestrator 4.0. We strongly recommend that you read the entire document.

CAUTION: We do not support automatic upgrading of a pre-release version of the software. To upgrade to a production release of the software, you must first uninstall the existing version of the software.

This release and what’s new

The McAfee AntiSpyware Enterprise Module works with VirusScan Enterprise to protect your desktop and file servers from potentially unwanted spyware and cookies.

This release provides the AntiSpyware Enterprise Module 8.0 and 8.5 files you need to manage these products with ePolicy Orchestrator 4.0.

Product license

The Beta license for this product expires on September 25, 2007. This license term varies from the standard 30 days as described in the End User License Agreement.

Installation

When you install or upgrade to ePolicy Orchestrator 4.0, the AntiSpyware Enterprise Module extension is not automatically installed in the repository unless you previously had the module installed in ePolicy Orchestrator 3.6.1.

  • If you were using the AntiSpyware Enterprise Module with ePolicy Orchestrator 3.6.1, the new AntiSpyware Enterprise Module extension will be automatically installed in the ePolicy Orchestrator repository when you upgrade to ePolicy Orchestrator 4.0.
  • If you were not using the AntiSpyware Enterprise Module with ePolicy Orchestrator 3.6.1 and upgrade to ePolicy Orchestrator 4.0, you must manually install the ePolicy Orchestrator extension. The extension can be found in the “Extensions-After” folder in the installation directory. See the ePolicy Orchestrator online Help for information about installing extensions.

Known issues

Known issues in this release of the software are described below:

Product deployment

  • Issue

    VirusScan Enterprise must be installed on the client system before the AntiSpyware Enterprise Module can be installed. When creating deployment tasks to deploy both VirusScan Enterprise and the AntiSpyware Enterprise Module to the same system, the products may not deploy in the correct order. If the deploys and attempts to install before VirusScan Enterprise is installed, the AntiSpyware Enterprise Module installation fails.

    Resolution

    The order in which you create the deployment tasks determines the order in which the product deploys and is installed. Create the VirusScan Enterprise deployment task before creating the AntiSpyware Enterprise Module deployment task to ensure they are deployed and installed in the correct order.

Compatibility with other products

  • Issue

    The AntiSpyware Enterprise Module 8.0 and 8.5 versions included in this release are not compatible with previous versions of ePolicy Orchestrator or any versions of ProtectionPilot.

    Resolution

    The AntiSpyware Enterprise Module 8.0 and 8.5 versions included in this release were created specifically for ePolicy Orchestrator 4.0. They cannot be used with previous versions of ePolicy Orchestrator or any versions of ProtectionPilot.

On-demand scan tasks

  • Issue

    When the AntiSpyware Enterprise Module product extension is added to the ePolicy Orchestrator 4.0 repository, the "Cookies" and "Registry" scan items are automatically added to the default on-demand scan task as expected. However these scan items are not automatically added to previously existing on-demand scan tasks.

    Resolution

    Users must manually edit previously existing on-demand scan tasks to add the "Cookies" and "Registry" scan items.
    Note: Any new on-demand scan tasks that are created using the default task, will automatically include the "Cookies" and "Registry" scan items.

Where to find McAfee enterprise product information

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.

Installation Phase

Setup Phase

Maintenance Phase

Before, during, and after installation.

Release Notes

  • Known issues in the current release.
  • Issues resolved since the last release.
  • Last-minute changes to the product or its documentation.

Getting up-and-running with the product.

Configuration Guide and Online Help

  • Setting up and customizing the software for your environment.

Online Help

  • Managing and deploying products through ePolicy Orchestrator.
  • Detailed information about options in the product.

Maintaining the software.

Online Help

  • Maintaining the software.
  • Reference information.
  • All information found in the product guide.

Knowledgebase (knowledge.mcafee.com)

  • Release notes and documentation.
  • Supplemental product information.
  • Workarounds to known issues.

Finding release notes and documentation for McAfee enterprise products

  1. Go to knowledge.mcafee.com and select Product Documentation under Useful links.
  2. Select <Product Name> | <Product Version> and select the required document from the list of documents.

Supporting documentation for this product

In addition to the release notes, refer to the AntiSpyware Enterprise Module 8.0 and 8.5 Product Guides for more information about tasks, procedures, and configuring policies in ePolicy Orchestrator.

License attributions

This product includes or may include:

Software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). | Cryptographic software written by Eric A. Young and software written by Tim J. Hudson | Some software programs that are licensed (or sublicensed) to the user under the GNU General Public License (GPL) or other similar Free Software licenses which, among other rights, permit the user to copy, modify and redistribute certain programs, or portions thereof, and have access to the source code. The GPL requires that for any software covered under the GPL, which is distributed to someone in an executable binary format, that the source code also be made available to those users. For any such software covered under the GPL, the source code is made available on this CD. If any Free Software licenses require that McAfee provide rights to use, copy or modify a software program that are broader than the rights granted in this agreement, then such rights shall take precedence over the rights and restrictions herein. * Software originally written by Henry Spencer, Copyright 1992, 1993, 1994, 1997 Henry Spencer. | Software originally written by Robert Nordier, Copyright © 1996-7 Robert Nordier. | Software written by Douglas W. Sauder. | Software developed by the Apache Software Foundation (http://www.apache.org/). A copy of the license agreement for this software can be found at www.apache.org/licenses/LICENSE-2.0.txt. | International Components for Unicode ("ICU") Copyright © 1995-2002 International Business Machines Corporation and others. | Software developed by CrystalClear Software, Inc., Copyright © 2000 CrystalClear Software, Inc. | FEAD® Optimizer® technology, Copyright Netopsystems AG, Berlin, Germany. | Outside In® Viewer Technology © 1992-2001 Stellent Chicago, Inc. and/or Outside In® HTML Export, © 2001 Stellent Chicago, Inc. | Software copyrighted by Thai Open Source Software Center Ltd. and Clark Cooper, © 1998, 1999, 2000. | Software copyrighted by Expat maintainers. | Software copyrighted by The Regents of the University of California, © 1996, 1989, 1998-2000. | Software copyrighted by Gunnar Ritter. | Software copyrighted by Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A., © 2003. | Software copyrighted by Gisle Aas. © 1995-2003. | Software copyrighted by Michael A. Chase, © 1999-2000. * Software copyrighted by Neil Winton, © 1995-1996. | Software copyrighted by RSA Data Security, Inc., © 1990-1992. | Software copyrighted by Sean M. Burke, © 1999, 2000. | Software copyrighted by Martijn Koster, © 1995. | Software copyrighted by Brad Appleton, © 1996-1999. | Software copyrighted by Michael G. Schwern, © 2001. | Software copyrighted by Graham Barr, © 1998. | Software copyrighted by Larry Wall and Clark Cooper, © 1998-2000. | Software copyrighted by Frodo Looijaard, © 1997. | Software copyrighted by the Python Software Foundation, Copyright © 2001, 2002, 2003. A copy of the license agreement for this software can be found at www.python.org. | Software copyrighted by Beman Dawes, © 1994-1999, 2002. | Software written by Andrew Lumsdaine, Lie-Quan Lee, Jeremy G. Siek © 1997-2000 University of Notre Dame. | Software copyrighted by Simone Bordet & Marco Cravero, © 2002. | Software copyrighted by Stephen Purcell, © 2001. | Software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/). | Software copyrighted by International Business Machines Corporation and others, © 1995-2003. | Software developed by the University of California, Berkeley and its contributors. | Software developed by Ralf S. Engelschall <rse@engelschall.com> for use in the mod_ssl project (http:// www.modssl.org/). | Software copyrighted by Kevlin Henney, © 2000-2002. | Software copyrighted by Peter Dimov and Multi Media Ltd. © 2001, 2002. | Software copyrighted by David Abrahams, © 2001, 2002. See http://www.boost.org/libs/bind/bind.html for documentation. | Software copyrighted by Steve Cleary, Beman Dawes, Howard Hinnant & John Maddock, © 2000. | Software copyrighted by Boost.org, © 1999-2002. | Software copyrighted by Nicolai M. Josuttis, ©1999. | Software copyrighted by Jeremy Siek, © 1999-2001. | Software copyrighted by Daryle Walker, © 2001. | Software copyrighted by Chuck Allison and Jeremy Siek, © 2001, 2002. | Software copyrighted by Samuel Krempp, © 2001. See http://www.boost.org for updates, documentation, and revision history. | Software copyrighted by Doug Gregor (gregod@cs.rpi.edu), © 2001, 2002. | Software copyrighted by Cadenza New Zealand Ltd., © 2000. | Software copyrighted by Jens Maurer, © 2000, 2001. | Software copyrighted by Jaakko Järvi (jaakko.jarvi@cs.utu.fi), © 1999, 2000. | Software copyrighted by Ronald Garcia, © 2002. | Software copyrighted by David Abrahams, Jeremy Siek, and Daryle Walker, © 1999-2001. | Software copyrighted by Stephen Cleary (shammah@voyager.net), © 2000. | Software copyrighted by Housemarque Oy <http://www.housemarque.com>, © 2001. | Software copyrighted by Paul Moore, © 1999. | Software copyrighted by Dr. John Maddock, © 1998-2002. | Software copyrighted by Greg Colvin and Beman Dawes, © 1998, 1999. | Software copyrighted by Peter Dimov, © 2001, 2002. | Software copyrighted by Jeremy Siek and John R. Bandela, © 2001. | Software copyrighted by Joerg Walter and Mathias Koch, © 2000-2002. | Software copyrighted by Carnegie Mellon University © 1989, 1991, 1992. | Software copyrighted by Cambridge Broadband Ltd., © 2001-2003. | Software copyrighted by Sparta, Inc., © 2003-2004. | Software copyrighted by Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications, © 2004. | Software copyrighted by Simon Josefsson, © 2003. | Software copyrighted by Thomas Jacob, © 2003-2004. | Software copyrighted by Advanced Software Engineering Limited, © 2004. | Software copyrighted by Todd C. Miller, © 1998. | Software copyrighted by The Regents of the University of California, © 1990, 1993, with code derived from software contributed to Berkeley by Chris Torek.


COPYRIGHT

COPYRIGHT

Copyright © 2007 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

TRADEMARK ATTRIBUTIONS

AVERT, EPO, EPOLICY ORCHESTRATOR, FLASHBOX, FOUNDSTONE, GROUPSHIELD, HERCULES, INTRUSHIELD, INTRUSION INTELLIGENCE, LINUXSHIELD, MANAGED MAIL PROTECTION, MAX (MCAFEE SECURITYALLIANCE EXCHANGE), MCAFEE, MCAFEE.COM, NETSHIELD, PORTALSHIELD, PREVENTSYS, PROTECTION-IN-DEPTH STRATEGY, PROTECTIONPILOT, SECURE MESSAGING SERVICE, SECURITYALLIANCE, SITEADVISOR, THREATSCAN, TOTAL PROTECTION, VIREX, 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 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 ACCOMPANIES 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 WEB SITE 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.