Known Issues - McAfee VIRUSSCAN ENTERPRISE 8.7I PATCH 4 - RELEASE NOTES Release Note

NOTE: Refer to McAfee Support KnowledgeBase article KB65382 for further information.
17. The installation packages for patches and reposts were 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 Run-Time 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 Run-Time DAT functionality until they receive their next Patch.
2. Issue: With the improved functionality of the on-access scanner memory scan, lower and middle ranged systems might 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 includes support for displaying status and logs in Russian. Older versions display this
information in English by default.
5. Issue: Since VirusScan Enterprise 8.7i Patch 2 and later include the new interface for reporting status to Windows Security
Center, uninstalling the Patch removes this function -- without reintroducing the older expired function. This means that Windows
Security Center does not report VirusScan Enterprise 8.7i being installed until Patch 2 or later is implemented.
6. Issue: When you remove the McAfee AntiSpyware Module, the status in Windows Security Center is not updated.
7. Issue: In deployments of VirusScan Enterprise 8.7i Patch 2 and later with McAfee Agent 4.5, the VirusScan tray plug-in does not
appear until after a restart of the McAfee system tray icon. If VirusScan is uninstalled, the VirusScan tray plug-in is still visible
until a similar restart.
8. Issue: This Patch adds needed support for McAfee VirusScan Enterprise for Offline Virtual Images 2.0, and should not be
removed unless the VirusScan Module is removed first.
9. Issue: The Patch installer included an MSI deferred action to resolve an issue that occurred when attempting to uninstall the
Patch on some newer operating systems. The deferred.mfe file updated the cached MSI of the currently installed VirusScan
Enterprise 8.7i product. If the Patch is included in a McAfee Installation Designer customized package, the deferred.mfe file was
not included, and therefore the Patch might not be able to be uninstalled in some newer operating systems.
10. Issue: If you installed this release interactively and cancelled the installation on a system where a previous Patch was installed,
after the rollback was complete, the previous Patch might no longer report to ePolicy Orchestrator or appear in the About
VirusScan Enterprise window.
11. Issue: Installing the Patch and specifying a log file path using the Microsoft Installer (MSI) switch "/L" did not log to the
specified path. A log file capturing full data was logged to the folder "McAfeeLogs" under the Temp folder.
12. Issue: If Host Intrusion Prevention 6.x or later was installed and disabled prior to installing VirusScan Enterprise, it was
necessary to re-enable Host Intrusion Prevention and disable it again, in order for VirusScan Buffer Overflow Protection to be
properly enabled.
13. Issue: Uninstalling VirusScan Enterprise Patches is possible for computers running Windows Installer v3.x or later. This
technology is not fully integrated for Windows 2000 operating systems, so there is no option to remove the Patch in Add/Remove
programs. See Removing the Patch for instructions on removal via command-line options.
14. Issue: Patches for VirusScan Enterprise 8.7i can only be uninstalled via Add/Remove programs, not via ePolicy Orchestrator.