Patch
1 Issue — Third-party products that inject DLLs into processes could cause the VirusScan Enterprise service
(VsTskMgr.exe) to periodically poll data and frequently log event 516 entries. (Reference: 625756)
Resolution — The VirusScan Enterprise Task Manager service no longer causes prolific generation of the event 516.
2 Issue — When a VirusScan Enterprise patch update is applied, the update would "succeed" and appear to be at the
correct patch level even if a file was missing or corrupted in the repository. (Reference: 629564)
Resolution — A missing or corrupt patch file in the repository now causes VirusScan Enterprise updates to fail.
Note
You must still manually fix the issue with the repository before the update can be
successful.
3 Issue — A flaw in the Windows registry filtering model caused the McAfee Access Protection driver to incorrectly block
remote registry accesses. (Reference: 668312)
Resolution — Microsoft identified a workaround and McAfee implemented the fix.
4 Issue — The Reports Extension might fail to check into the repository if the default group for the queries already exist.
(Reference: 670759)
Resolution — All queries now include a group reference so they do not try to recreate the default group.
5 Issue — A STOP error (Bugcheck 7f) could occur with the McAfee filter driver due to lost content header information
when transmitting through a raw socket on Windows 7. This issue was seen with some third-party VPN clients.
(Reference: 682177)
Resolution — The McAfee filter driver now ensures header information is preserved and forwarded through a raw socket.
6 Issue — McShield might fail to start due to an API not properly calling processor group affinity for Non-Uniform Memory
Access systems. (Reference: 685950)
Resolution — The API to set processor group affinity is now called correctly.
7 Issue — When a McAfee driver queried for the engine version, the return value was a non-empty string if a version was
not found in the registry. (Reference: 689986)
Resolution — The return value has been updated to send an empty string if no engine version is found.
8 Issue — During an On-Demand Scan, the user was able to stop or cancel the scan, regardless of configured settings, by
clicking the scan task in the console and selecting Show Progress. (Reference: 694042)
Resolution — Managed ePolicy Orchestrator On-Demand Scan tasks now properly enforce the password protection
settings for the user if managed tasks are displayed in the user console.
9 Issue — Access Protection rules that begin with the special wildcard character "?", even with no rules set to block, would
cause the CPU to spike to 100% usage. (Reference: 696654)
Resolution — The Access Protection driver now properly addresses the issue when evaluating rules beginning with "?".
10 Issue — A STOP error (Bugcheck 8E) could occur with VirusScan Enterprise if a locked file was being scanned under some
circumstances. (Reference: 702469)
Resolution — VirusScan Enterprise now prevents the STOP error when scanning locked files.
11 Issue — When adding or removing a storage media device, the CPU usage could spike due to repeated attempts to
acquire a resource that might be in an unguarded dead-lock state. (Reference: 703065)
(27 strony)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji