NOTE: In some scenarios, the runtime DATs are not available. See item #1 under Known Issues. Refer to
McAfee Support KnowledgeBase article KB65459 for further information on runtime DATs.
13. VirusScan Enterprise functions that request the current version of DATs no longer need to initialize the scan
engine to do so. This prevents excessive CPU spikes during ePolicy Orchestrator properties collection, as well
as other areas that poll the DATs.
14. The on-access scanner memory scan function (Processes on enable) has been modified significantly to make
it more comprehensive.
NOTE: The improved functionality can cause a performance impact to the system. See item #2 under
Known Issues.
15. When a web browser opens a site that is script-intensive, scanning the scripts adds to the delay of loading
the page. This Patch contains new functionality for ScriptScan whitelisting. If the web site is a trusted
Intranet and/or frequently visited, the new implementation now allows for the exclusion of that the site from
script scanning.
NOTE: Refer to McAfee Support KnowledgeBase article KB65382 for further information.
16. The installation packages for patches and reposts have been upgraded so that the installation log name,
created in the McAfeeLogs folder, has a dynamically generated name based on the current date and time of
the installation. This helps save logs that might have been overwritten with the previous “backup previous
log only” method.
Known issues
Here is a list of known issues that we were aware of at production time.
1. Issue: In some situations, the product switches over to using the normal copy of the DAT files, instead of
the runtime DATs:
If the McAfee AntiSpyware Enterprise module is installed after VirusScan Enterprise 8.7i Patch 3 is on
the system, some of the new registry settings, which are new for the runtime functionality, were
changed back. This resolves itself with a restart of the McTaskManager service or with a reboot.
If one of the scanners is busy on a large file when the AutoUpdate process posts the revised copy of
the DATs, the process of refreshing the runtime copy of the DATs times out. All scanners use the
normal DATs until the next successful update.
The VirusScan Modules* will not use the runtime DAT functionality until they received their next
Patch.
2. Issue: With the improved functionality of the on-access scanner memory scan, lower and middle ranged
systems may see a performance impact at startup and after a successful AutoUpdate of the engine or DATs.
Currently the Process on enable option is enabled by default on the shipping version of VirusScan Enterprise
8.7i. McAfee recommends that in a managed environment, disable this option prior to deployment of the
Patch, until the impact of memory scanning can be determined for your environment. It is not possible to
maintain both the more comprehensive scanning that comes with Patch 1 and later, and the former level of
scanning. Therefore, only the more comprehensive scan is used.
NOTE FOR CURRENT AND NEW USERS:
The Patch installation does not modify current settings to disable the Process on enable option.
The VirusScan 8.7i NAP and extension that are included with the Patch do change the McAfee Default
policy, but do not modify the My Default policy, or any custom policy settings that were made prior to
the check-in of the new NAP/extension.
The VirusScan Enterprise 8.7i Repost with Patch now installs with the Process on enable option
disabled, unless the Maximum Security option is selected during the installation.
3. Issue: With the introduction of support for Russian, you might need to remove the previous version of the
extension from ePolicy Orchestrator before adding the new extension. If you do not, some of the interface
might be displayed in the original language.
4. Issue: McAfee Agent 4.0 Patch 2 and later include support for displaying status and logs in Russian. Older
versions display this information in English by default.
