Release Notes for McAfee(R) GroupShield(TM) version 7.0.1 Patch 1 for Microsoft Exchange. Copyright (C) 2011 McAfee, Inc. All Rights Reserved CONTENTS - About this Document - About this Release - Purpose - Files included with this release - Known Issues - Important notes for this Patch - Resolved Issues - Installation Instructions - Finding product documentation - Copyright - Trademark Attributions - License Information ABOUT THIS DOCUMENT Thank you for choosing McAfee(R) GroupShield version 7.0.1 Patch 1 for Microsoft Exchange. This document contains important information about the current release. We strongly recommend that you read the entire document. ABOUT THIS RELEASE Patch Release: January 21, 2011 This release was developed and tested with: - DAT Version: 6222.0000 - Engine Version: 5400.1158 Make sure you have installed these versions before using this release. PURPOSE This release includes files for use with McAfee(R) GroupShield (TM) version 7.0.1 Patch 1 for Microsoft Exchange. It resolves the issues listed in "RESOLVED ISSUES" section. FILES INCLUDED WITH THIS RELEASE This release consists of a package called GSE701Patch1.ZIP, which contains the following files: - Patch1_without_DBMigration.ZIP = GroupShield Patch without capability of Postgres Quarantine Database Migration archive file. - Patch1_with_DBMigration.ZIP = GroupShield Patch with capability of Postgres Quarantine DataBase Migration archive file.
- GROUPSHD7000_0404.ZIP = GroupShield Product Extension file (Chinese- Traditional). - GROUPSHD7000_0407.ZIP = GroupShield Product Extension file (German). - GROUPSHD7000_0409.ZIP = GroupShield Product Extension file (English). - GROUPSHD7000_040A.ZIP = GroupShield Product Extension file (Spanish). - GROUPSHD7000_040C.ZIP = GroupShield Product Extension file (French). - GROUPSHD7000_0411.ZIP = GroupShield Product Extension file (Japanese). - GROUPSHD7000_0412.ZIP = GroupShield Product Extension file (Korean). - GROUPSHD7000_0804.ZIP = GroupShield Product Extension file (Chinese- Simplified). - GSE7REPORTS.ZIP = GroupShield Report Extension file. - README.PDF = This Readme file. - VALIDATE.TXT = Validate codes for this Patch. KNOWN ISSUES 1. ISSUE: GroupShield (TM) version 7.0.1 Patch 1 for Microsoft Exchange is incompatible with McAfee Quarantine Manager. However this will be rectified in a follow-up fix. For more information on the progress/release of the fix, refer to the McAfee Download website. This Patch release will work properly, if you are not using McAfee Quarantine Manager. GroupShield (TM) version 7.0.1 is still completely compatible with the supported versions of McAfee Quarantine Manager.
2. ISSUE: With Exchange Server 2007 SP3, on-demand scan failed to scan items. (eventid=2045 and error occurred=80004001) While installing Exchange Server 2007 Service Pack 3 on Windows 2008 R2, a warning message for CDOEx related applications appears if the hotfix mentioned in KB 982720 is not installed. Install the hotfix to resolve this issue before installing Exchange Server 2007 Service Pack 3. Reference ID: 620867 3. ISSUE: The Event Viewer shows "faulting Module SpamRouterX64.dll", and "GSH User Junk Folder Router" exception C0000005" errors intermittently. Reference ID: 625481 4. ISSUE: Configuration report, Status report, On-demand scan task and Autoupdate may not function intermittently. Workaround: Restart the GroupShield for Exchange & Framework services and retry the tasks. Reference ID: 626132 5. ISSUE: AutoUpdate, On-demand scan, Status Report and Configuration tasks may not work if VirusScan Enterprise is installed on the same computer (this error occurs intermittently). Workaround: Disable the VirusScan Enterprise protection, re-start Framework service, start the above mentioned tasks and then enable the VirusScan Enterprise protection. Reference ID: 626136 6. ISSUE: GroupShield version 7.0.1 Patch 1 for Exchange SUPERDAT installation screen displays distorted parameters and buttons for localized versions. Reference ID: 625487 7. ISSUE: Emails containing Russian characters are replaced with? when released from quarantine for both release and download operations. Reference ID: 625941 8. ISSUE: Error: Database migration failed to establish connection. WORKAROUND: Run DBMIGRATE.EXE after restarting the GroupShield services.
9. ISSUE: During database migration, Postgres errors appear in the event viewer, if Patch1_with_DBMigration.ZIP package is used for installation. Reference ID: 624014 10. ISSUE: During Installation of Patch1, the following issues may occur: a. On a standalone/silent installation, the Groupshield postgres data migration fails. b. Using EPO on Exchange Cluster (both the nodes) simultaneously, the cluster node gets interchanged and Groupshield postgres data migration fails. WORKAROUND: For (a): - Double click <install-dir>\bin\dbmigrate.exe to perform DBMigration. For (b): 1. Move the cluster resources to Original Active node. 2. Double click <install-dir>\bin\dbmigrate.exe to perform DBMigration. Reference ID: 645673 IMPORTANT NOTES FOR THIS PATCH - In a standalone Patch 1 installation with the capability of Postgres Quarantine Database Migration archive file, if Groupshield process is locked, the Client machine will display a dialog for reboot to replace the Patch 1 binaries. The Data Migration window will come up after the reboot. - In an epolicy Orchestrator based Patch 1 installation with the capability of Postgres Quarantine Database Migration archive file, if Groupshield process is locked, the client machine will reboot automatically. Data migration will happen in silent mode after the reboot. - Installing Patch 1 on clusters will stop Cluster Service and start the cluster service after rebooting in case of a file lock scenario. - Installing Patch 1 will restart IIS and Microsoft Exchange services. - Use Patch1_without_DBMigration.ZIP package to install Patch without capability of Postgres Quarantine Database Migration from epolicy Orchestrator. - Use Patch1_with_DBMigration.ZIP package to install Patch with capability of Postgres Quarantine Database Migration from epolicy Orchestrator.
- Custom deployment of Patch 1 where few systems with DBMigration and few systems without DBMigration also supported. Both the packages can be checked into epolicy Orchestrator 4.x at any point. - If Postgres HotFix 528662 or 551487 is already installed, then Postgres database migration feature is not available in patch. - If administrator wants to run DBMigration at later point of time, they can do by clicking the DBMigrate.EXE which is available in bin folder. - Patch over Patch installation is not supported. However Force installation is supported with /F switch. - After Installing patch1, by default QPCorruptionDetection is disabled and it won t detect quoted-printable mails as corrupted. If it is epolicy Orchestrator managed machine, QPCorruptionDetection can be enabled by changing the registry key from 0 to 1. This registry key can be found under: HKEY_LOCAL_MACHINE\Software\McAfee\GroupShield for Exchange\SystemState If it is a standalone machine, QPCorruptionDetection can be enabled by opening the McAfeeConfig.xml in the notepad, search for string QPCorruptionDetection, and edit the value from 0 to 1. - If the anti-spam rules update request goes through a proxy server, do the following changes: a. Click "Start Run" and type "REGEDIT". The "Registry Editor" window appears. b. Modify the registry keys "ProxyAddress" and "ProxyUserAccountDetails" in the following path: Default Path in a 32-bit OS: HKEY_LOCAL_MACHINE\Software\McAfee\GroupShield for Exchange\SystemState\ Default Path in a 64-bit OS: HKEY_LOCAL_MACHINE\Software\Wow6432Node\McAfee\GroupShield for Exchange\SystemState\ c. Set the ProxyDetailsSet DWORD value to 1, if we need to use the "ProxyAddress" and "ProxyUserAccountDetails" values from registry. d. For the "ProxyAddress" registry key, add the "Value data" in the following format: - <Proxy Server IPAddress>:<Proxy ServerPort> - Example: 192.168.215.100:8080 e. For the "ProxyUserAccountDetails" registry key, add the "Value data" in the following format: - <User name>:<password> - Example: Administrator:Password123
RESOLVED ISSUES Here is a list of issues from previous releases of the software that have been fixed in this release. 1. ISSUE: Upon successful DAT or Engine update, the DAT date is not updated in the registry. Reference ID: 447121 2. ISSUE: DAT date becomes Not Available after a DAT update from FTP. Reference ID: 445864 3. ISSUE: EventParser services stops responding while processing events. Reference ID: 433723 4. ISSUE: Disclaimer is not applied to an outbound email, if GroupShield is installed on Exchange Server 2007 with the Hub Transport role. Reference ID: 445948 5. ISSUE: The Spam Router fails to route spam mails to the user's "Junk E-mail" folder on Microsoft Exchange Server 2007. Reference ID: 449141 6. ISSUE: Anti-spam rules update fails, if the update request goes through a proxy server. Reference ID: 450161 7. ISSUE: If Digest mail is enabled in the registry for GroupShield, Microsoft Exchange Information Store stops responding once the AutoUpdate is complete. Reference ID: 452546 8. ISSUE: File filtering feature does not work, if the attachment's file name is long and contains blank spaces. Reference ID: 453512 9. ISSUE: In the "Settings & Diagnostics Diagnostics" page, changes made to the "Event Logging" settings are not saved. Reference ID: 454269
10. ISSUE: POSTGRESS fails to load, when GroupShield resource is brought online on Microsoft Exchange 2007 cluster. Reference ID: 462250 11. ISSUE: When VSAPI is enabled, the SMTP Archive Sink "Postcat" (Post-categorization) causes overhead on VSAPI and the computer stops responding due to high CPU utilization of RPCSERV.EXE. Reference ID: 470824 12. ISSUE: GroupShield for Exchange fails to quarantine infected emails, on Microsoft Windows 2008 Server. Reference ID: 474504 13. ISSUE: Unable to download infected emails from the "Detected Items" database. Reference ID: 474941 14. ISSUE: RPCSERV.EXE exception was observed, during alert replacement for TNEF (Transport Neutral Encapsulation Format) email. This is due to heap corruption in the TNEF Parser plug-in. Reference ID: 476761 15. ISSUE: The "UpdateFrequency" and "ConnectionPoolSize" registry key values are different in "Stats" and "gsstats" key of the "GroupShield for Exchange" key. Reference ID: 478550 16. ISSUE: GSCommon.dll exception occurs while fetching virtual server name. This is caused by usage of uninitialized variables. Reference ID: 480870 17. ISSUE: When a user mailbox is created under new mailbox storage group in Exchange server, the Spam Router fails to route spam email messages to the user Junk E-mail folder. Reference ID: 487997
18. ISSUE: After a successful DAT update, GroupShield logged the following error in Event Viewer: "The OnAccess (Transport) scanner failed to scan the item '' with error 8004022e." This error indicates that GroupShield configuration has not been refreshed properly with the latest DAT(s). Reference ID: 489257 19. ISSUE: High "RPC Averaged Latency" was observed, when Postgres" process takes more time to complete the I/O operations. As a result the GroupShield reporting threads wait longer, which increases the RPC latency and delays the processing of email messages. Reference ID: 491164 20. ISSUE: When a policy was enforced using epolicy Orchestrator, an Update policy scheduled on the GroupShield server was overwritten. Reference ID: 495934 21. ISSUE: Unable to change the action for File Filtering rule, when GroupShield's Web user interface is accessed using Internet Explorer 8.0. Reference ID: 497026 22. ISSUE: Email messages are not scanned when: - The email address is specified in the "CC" or "BCC" field. - The "DigestMail" DWORD value is set to "1" in the registry editor under: HKLM\Software\McAfee\GroupShield for Exchange\ADUserCache\ Reference ID: 503826 23. ISSUE: GroupShield reports extension does not update events 1750-1760 in the event table. Reference ID: 506246 24. ISSUE: Unable to optimize the "gse_store_stats" table in the GroupShield for Exchange 7.0.1 database. Reference ID: 511043 25. ISSUE: During Autoupdate, "RPC Requests" performance counter shows high resource utilization. Reference ID: 514941
26. ISSUE: Netinfo.EXE stopped responding due to an invalid pointer in the Transport scanner. Reference ID: 518820 27. ISSUE: GroupShield's POSTGRES.EXE process fails to initialize, when the server locale and the user locale do not match. Reference ID: 524622 28. ISSUE: In a Locked-Down secure environment, GroupShield's POSTGRES process failed to start. Reference ID: 528662 29. ISSUE: High "RPC Averaged Latency" was observed when "Postgres" process takes more time to complete the I/O operations. As a result the GroupShield reporting threads wait longer; this increases the RPC latency and delays the processing of email messages. Reference ID: 488686 30. ISSUE: GroupShield's Quarantine database size gradually increased, as Write Ahead Logs (each 16 MB) were getting created in the POSTGRES "PG_XLOG" folder. Reference ID: 514883 31. ISSUE: When Virus Scanning Application Interface (VSAPI) scanning was enabled in GroupShield's On-Access settings, Microsoft Exchange Information Store service failed to start. Reference ID: 530772 32. ISSUE: When a split ZIP file was scanned, the first part of the ZIP file was detected as corrupted content. Reference ID: 531415 33. ISSUE: On the HUB server, email flow stopped as emails were queued up in the submission queue. Reference ID: 538979 34. ISSUE: GroupShield's POSTGRES process failed to start in one or both of the following circumstances: - In a Locked-Down secure environment. - In a non-english locale environment. Reference ID: 551487
35. ISSUE: This Patch optimizes and enhances the memory usage during GroupShield on-demand scans. Reference ID: 562301 36. ISSUE: On-demand scan shows zero result while resuming after it is stopped. Reference ID: 569373 37. ISSUE: - On-demand scan shows zero folders scanned while using the Resumable option. - On-demand scan failed to scan mailboxes containing special characters. Reference ID: 560405 38. ISSUE: a. On-demand scan wizard is not able to add mailboxes having identical aliases. b. On-demand scan is not able to scan one of the mailboxes of child domains having identical aliases. c. On-demand scan is not able to scan when user and mailbox are in different child domains with mailboxes having identical aliases. Reference ID: 580811 39. ISSUE: Sub-policy based on SMTP addresses is not applied in Edge Transport Role thus affecting the mail flow. Reference ID: 573230 40. ISSUE: When GroupShield's Alert Message was modified using epolicy Orchestrator 4.5, the formatting in the "Warning.TXT" file was lost. Reference ID: 533910 41. ISSUE: In epolicy Orchestrator 4.0/4.5, GroupShield policies having "<<" or ">>", instead of quotation marks in the text fields were removed during policy enforcement. Reference ID: 523488 42. ISSUE: Camelus support over GroupShield for Exchange 7 Patch 1. Reference ID: 539223
43. ISSUE: When a split.zip/.rar file was scanned, a part of the split file was detected as corrupted content. When disclaimer in GroupShield for Exchange was enabled, emails were getting bounced. This was because GroupShield added extra CR or LF in the email body. Reference ID: 553694 44. ISSUE: GroupShield for Exchange 7.0.1 Patch uses epolicy Orchestrator deployable packages to install a patch. Reference ID: 573880 45. ISSUE: Scan failure occurred due to improper update of extra DAT. Reference ID: 568105 46. ISSUE: a. When quarantined emails with Russian characters are released from the quarantine database: - The released email is quarantined again. This is only applicable for emails that are quarantined due to File Filter rule. - The body of the released email contains garbled text. This is only applicable for emails in RTF and HTML formats. b. Email released from the quarantined database is in ".EML" format, instead of ".MSG" format. c. Emails sent to 'CC' and/or 'BCC' and quarantined, when released to user will go as 'TO' instead of 'CC' and/or 'BCC'. d. Downloaded emails from quarantined database are not in readable format. e. Released emails from quarantined database are not the same as original email. Reference ID: 565047 47. ISSUE: While scheduling an on-demand scan, the "Available Folders" section appeared blank. This issue occurred when "GSCOMMONx64SRV.EXE" failed to register during installation. Reference ID: 541845 48. ISSUE: The timestamp for epolicy Orchestrator events generated between 12:00 to 13:00 hours was incorrect. Reference ID: 582678 49. ISSUE: "Unknown Error has occurred" error occurred while running the query "Number of Messages and Average Processing Time Today". Reference ID: 584501
50. ISSUE: User Junk Folder Router failed to route spam emails. Due to this, spam emails were routed to the user's "Inbox" instead of "Junk E-mail" folder. Reference ID: 582977 51. ISSUE: GroupShield reports in epolicy Orchestrator displayed the action for a cleaned infection as "Replaced" instead of "Cleaned". Reference ID: 579340 52. ISSUE: Emails with multiple layers of multipart MIME with their own "Content-Transfer-Encoding" headers are detected as corrupt. Reference ID: 577607 53. ISSUE: GroupShield logged the following error in the Event Viewer: - The On Access (Transport) scanner failed to scan the item with error 8004020a/b. Reference ID: 572750 54. ISSUE: Email quarantined due to mail size filtering when released from MQM is not getting delivered. Reference ID: 582421 55. ISSUE: Scan failure occurred due to improper update of extra DAT. Reference ID: 590846 56. ISSUE: Sometimes McAfee GroupShield for Exchange fails to use the latest DATs after an auto-update. Reference ID: 623484 57. ISSUE: GroupShield causes RPC latency, due to which emails are getting queued up in the Exchange server. Reference ID: 620960 58. ISSUE: When the GroupShield's disclaimer option is enabled, outbound emails start queuing up instead of being delivered. Reference ID: 637177
INSTALLATION INSTRUCTIONS REQUIREMENTS: To use this Patch, you must have McAfee GroupShield version 7.0.1 for Microsoft Exchange software installed on the computer you intend to update. This Patch will not work with any earlier versions of the software. IMPORTANT: Before applying this patch, ensure that Auto-Update and On-demand task are not running. STANDALONE INSTALLATION 1. Close all GroupShield administration consoles, StandaloneUI, EditSiteList, any MMC console that is running on the server. 2. Extract Patch1_without_DBMigration.EXE or Patch1_with_DBMigration.EXE from the package GSE701Patch1.ZIP to a temporary location. If HF551478 or HF528662 is already installed, then select Patch1_without_DBMigration.EXE to install Patch1. 3. Double-click Patch1_without_DBMigration.EXE or Patch1_with_DBMigration.EXE The Patch displays a wizard and produces a SUPERDAT.LOG file (located in the folder where the Patch has been executed from) where it lists all actions taken. - After completing Patch1_with_DBMigration.EXE, DBMigration window will open. The administrator has to click "Start" for the DBMigration process to get initiated. - If Patch1 installation is aborted with the error message "Error: Product reject the update request", check the superdat.log file for the service which is still running. Then manually stop the service and re-install the patch. The Superdat.log file can be found in the same folder from where the Patch installation was started. INSTALLATION THROUGH EPOLICY ORCHESTRATOR VERSION 4.0 1. Extract PATCH1_with_DBMigration.ZIP, PATCH1_without_DBMigration.ZIP, GROUPSHD7000_0409.ZIP (for English)and GSE7REPORTS.ZIP from the Patch package GSE701Patch1.ZIP to a temporary location of your epolicy Orchestrator computer. If HF551478 or HF528662 is already installed, then select Patch1_without_DBMigration.EXE to install Patch1.
2. Log on to epolicy Orchestrator as an administrator. 3. Click Software Check In Package, then add the Patch package. 4. Click "Configuration" "Extensions", then click "Install Extension". 5. Browse for the file GROUPSHD7000_0409.ZIP (for English) from the extracted package and click OK to install the product extension. 6. Browse for the file GSE7REPORTS.ZIP from the extracted package and click OK to install the report extension. 7. Create a new task to schedule an immediate update using epolicy Orchestrator "Product Update" option given under the "Client Tasks" tab. Under "Patches and Service Packs"; Select "GroupShield for Exchange Patch1 With Database Migration 7.0.0" or Select "GroupShield for Exchange Patch1 without Database Migration 7.0.0" and then run an agent wake-up call to deploy the Patch. If Patch1 install is aborted, check the Superdat.log file for the service which is still running, then manually stop the service and deploy the patch again. - If Patch1_with_DBMigration.ZIP is used for deployment: For Windows 2003 R2/SP2 the Superdat.log can be found in: C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\GROUSHD7000_DB\HotFix\PATCH1\0000\SuperDAT.log. For Windows 2008 R2/SP2, the Superdat.log can be found in: C:\Programdata\McAfee\Common Framework\Current\GROUSHD7000_DB\HotFix\PATCH1\0000\SuperDAT.log - If Patch1_without_DBMigration.ZIP is used for deployment: For Windows 2003 R2/SP2 the Superdat.log can be found in: C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\GROUSHD7000_NoDB\HotFix\PATCH1\0000\SuperDAT.log For Windows 2008 R2/SP2, the Superdat.log can be found in: C:\Programdata\McAfee\Common Framework\Current\GROUSHD7000_NoDB\HotFix\PATCH1\0000\SuperDAT.log INSTALLATION THROUGH EPOLICY ORCHESTRATOR VERSION 4.5 1. Extract PATCH1_with_DBMigration.ZIP, PATCH1_without_DBMigration.ZIP, GROUPSHD7000_0409.ZIP (for English)and GSE7REPORTS.ZIP from the Patch package GSE701Patch1.ZIP to a temporary location of your
epolicy Orchestrator computer. If HF551478 or HF528662 is already installed, then select Patch1_without_DBMigration.EXE to install Patch1. 2. Log on to epolicy Orchestrator as an administrator. 3. Click Menu Software Master Repository Actions Check In Package, then add the Patch package. 4. Click "Menu" "Software" "Extensions" then click "Install Extension". 5. Browse for the file GROUPSHD7000_0409.ZIP (for English) from the extracted package and click OK to install the product extension. 6. Browse for the file GSE7REPORTS.ZIP from the extracted package and click OK to install the report extension. 7. Create a new task to schedule an immediate update using epolicy Orchestrator "Product Update" option from the "Client Tasks" tab. Under "Patches and Service packs". Select "GroupShield for Exchange Patch1 With Database Migration 7.0.0" or select "GroupShield for Exchange Patch1 without Database Migration 7.0.0" and then run an agent wake-up call to deploy the Patch. If Patch1 install is aborted, check the Superdat.log file for the service which is still running, then manually stop the service and deploy the patch again. - If PATCH1_with_DBMigration.ZIP is used for deployment: For Windows 2003 R2/SP2 the Superdat.log can be found in C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\GROUSHD7000_DB\HotFix\PATCH 1\0000\SuperDAT.log. For Windows 2008 R2/SP2, the Superdat.log can be found in C:\programdata\McAfee\Common Framework\Current\GROUSHD7000_DB\HotFix\PATCH 1\0000\SuperDAT.log - If Patch1_without_DBMigration.ZIP is used for deployment: For Windows 2003 R2/SP2 the Superdat.log can be found in C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\GROUSHD7000_NoDB\HotFix\PAT CH1\0000\SuperDAT.log. For Windows 2008 R2/SP2, the Superdat.log can be found in C:\programdata\McAfee\Common Framework\Current\GROUSHD7000_NoDB\HotFix\PAT CH1\0000\SuperDAT.log.
CLUSTER INSTALLATION CLUSTER CONTINUOUS REPLICATION (CCR) ON EXCHANGE 2007 Install GroupShield for Exchange 7.0.1 Patch 1 on all the nodes of the cluster following the steps under the STANDARD INSTALLATION section. SINGLE COPY CLUSTER (SCC) ON EXCHANGE SERVER 2003 AND 2007 Install GroupShield for Exchange 7.0.1 Patch 1 on all the nodes of the cluster following the steps under the STANDARD INSTALLATION section. No extra steps are required to install Patch in Cluster setup". Patch 1 can be installed from epolicy Orchestrator onto cluster installations as well. SILENT INSTALLATION 1. Extract Patch1_without_DBMigration.EXE or Patch1_with_DBMigration.EXE from the package GSE701Patch1.ZIP and save it to the local drive. If HF551478 or HF528662 is already installed, then select Patch1_without_DBMigration.EXE to install Patch1. 2. From the command prompt, run Patch1_without_DBMigration.EXE or Patch1_with_DBMigration.EXE /s. If Patch1 install is aborted, check the Superdat.log file for the service which is still running, then manually stop the service and deploy the patch again. The Superdat.log file can be found in the same folder from where the Patch installation was started. TESTING YOUR INSTALLATION You can verify the Patch installation by clicking Dashboard Versions & Updates and verifying the Product Information from the user interface: Hotfixes PATCH 1
FINDING PRODUCT DOCUMENTATION 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. 2. Under Self Service, access the type of information you need: For user documentation: 1. Click "Product Documentation." 2. Select a "Product," then select a "Version." 3. Select a product document. For the KnowledgeBase: 1. Click "Search the KnowledgeBase" for answers to your product questions. 2. Click "Browse the KnowledgeBase" for articles listed by product and version. COPYRIGHT Copyright (C) 2011 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. V3.1.9