user level scanners are enabled on a system, the Run-Time DATs are not updated on the system and can impact the memory
usage improvements provided by the Run-Time DATs.
Previous improvements
Previous releases of the software include the following improvements.
1. Changes were made to the service startup sequence to have less impact on the system during startup.
2. Improvements were made to the way that the CommonShell scanner interacts with file I/O. This improves performance with on-
access scanners within the product.
3. VirusScan Enterprise 8.7i Patch 2 and later now has the ability to report compliance to the newer versions of Windows Security
Center.
4. The VirusScan Enterprise 8.7i extension has improved support for ePolicy Orchestrator 4.5 with Firefox 3.0 and Internet Explorer
8.0.
5. Several modifications were made to the way that the VirusScan Enterprise system tray icon interacts with the new functionality
of McAfee Agent 4.5.
6. The file extension .txt was added to the SmoothWritesExtension registry value to increase performance in handling text files.
7. Russian language support was added to the VirusScan Enterprise user interface, NAP file, and extension.
NOTE: See items #3 and #4 under Known issues for further information about this topic.
8. The VirusScan Reports extension now has updated queries to show the status of Artemis settings for the on-access, on-demand,
and email scanners.
NOTE: The Artemis status requires VirusScan Enterprise 8.5i Patch 8 or VirusScan Enterprise 8.7i Patch 1 and later to be
installed on the client systems, in order to correctly populate the reports. Refer to McAfee Support KnowledgeBase article
KB53732 for further information on Artemis functionality.
9. The Artemis level settings of the On-Access Scanner is now modifiable via the properties UI, and the equivalent VirusScan 8.7i
NAP and extension included in the Patch package.
NOTE: Because this setting is new with this release of the VirusScan 8.7i NAP and extension, there is no preserved setting upon
check-in of the management package. The ePolicy Orchestrator administrator must update that setting in the policies to match
the current Artemis policy.
10. Several modifications were made to the way VirusScan Enterprise interacts with the operating system on startup, suspend, and
shutdown. These modifications resolve and improve performance issues.
11. Current DAT files are compressed to conserve network bandwidth. Now, changes were made to decompress the DATs during the
AutoUpdate process and leave them in that state, so that scanners do not have to decompress them during initialization of the
scan.
12. The on-demand scanner now uses Windows Priority Control setting for the scan process. This lets the operating system set the
amount of CPU time that the on-demand scanner receives at any point in the scan process. The System Utilization setting in the
On-Demand Scan Properties maps to Windows Priority Control as:
Utilization
Priority
10%
Low
20%-50%
Below Normal
60%-100% Normal
13. The on-access, on-demand, email, and script scanners now use a runtime copy of the DATs. This change has reduced the
memory consumption of affected scanners by having the DATs in a readily available state for the scan engine to load.
NOTE: In some scenarios, the Run-Time DATs are not available. See item #1 under Known issues. Refer to McAfee Support
KnowledgeBase article KB65459 for further information on Run-Time DATs.
14. 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 functions that poll the DATs.
15. 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.
16. 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 website is a trusted Intranet and/or frequently visited, the new
implementation now allows for the exclusion of that site from script scanning.
Need help?
Do you have a question about the VIRUSSCAN ENTERPRISE 8.7I PATCH 4 - RELEASE NOTES and is the answer not in the manual?
Questions and answers