Release Notes for McAfee Agent 4.0.0 Patch 2 (Windows)
8.
Issue:
When an error occurred during Host Intrusion Prevention policy enforcement, the system
could be “locked out of the network”. (Reference: 406896)
Resolution:
Now the ePolicy Orchestrator server connection information (server IP, name and
port, and incoming agent wake-up port) is recorded. This allows Host Intrusion Prevention to
create specific rules that allow communication to and from the ePolicy Orchestrator server, even
in the absence of Host IPS policies.
9.
Issue:
The name of the ePO server the system last communicated with appears in the XML log
file. The value is initially blank and remained blank for a period of time after the first
communication. (Reference: 407154)
Resolution:
The name of the ePO server the system last communicated with now appears
immediately after the last server communication.
10.
Issue:
The McAfee Agent deployed managed products to Microsoft Vista or Windows Server 2008
that were not supported on these platforms. (Reference: 408989)
Resolution:
Managed products are now deployed only to their supported platforms.
11.
Issue:
The Mirror task created a duplicate repository, but it failed to copy the sitestat.xml file.
This caused the duplicate repository to remain disabled. (Reference: 409637)
Resolution:
The Mirror task now copies the sitestat.xml file to the duplicated repository.
12.
Issue:
During a managed product update, a dialog box could be presented requesting a system
reboot. The dialog box asked the user if they wanted to reboot now and rebooted the system even
when the user selected “No”. (Reference: 410573)
Resolution:
The managed product update process now honors the user's selected reboot
response.
13.
Issue:
Certain dates, such as leap years, were recorded incorrectly in the Agent_<system name>.
xml log file. (Reference: 413415)
Resolution:
All dates are now recorded correctly in the Agent_<system name>.xml log file.
14.
Issue:
The McAfee Agent only updated the VirusScan engine if the minor version was newer than
what was installed. This prevented the VirusScan engine from updating to a newer build of the
same version. (Reference: 414065)
Resolution:
The McAfee Agent now supports build-to-build VirusScan engine updates.
15.
Issue:
The installation and upgrade processes failed if the data folder was located in the
“Windows” or “WinNT” folders. (Reference: 415578)
Resolution:
Now the installation and upgrade processes allow the data folder to be located in the
“Windows” or “WinNT” folders with the exception of the system32 folder. The installation and
upgrade processes prohibit the data folder from including the system32 folder.
16.
Issue:
Some non-McAfee product installation routines removed critical registry entries, such as
the Windows IStream COM registration, causing the McAfee Agent to fail. (Reference: 416298)
