Release Notes for McAfee Agent 4.0.0 Patch 2 (Windows)
Resolution:
The upgrade process now re-registers the ole32.dll file when it detects it is missing.
17.
Issue:
The installation and upgrade processes failed if the installation or data folders contained
double-byte characters. (Reference: 416559)
Resolution:
The installation and upgrade processes now allow the installation and data folders to
contain double-byte characters.
18.
Issue:
Several install and uninstall error messages made no sense when displayed on a Japanese
language system. (Reference: 418729)
Resolution:
The upgrade process now displays meaningful install and uninstall error messages on
a Japanese language system.
19.
Issue:
On systems running VirusScan Enterprise version 8.0 the McAfee Agent did not remove
the Temp files created during the execution of an “Agent Update Task”. (Reference: 419066)
Resolution:
The McAfee Agent now removes the Temp files created during the execution of an
“Agent Update Task”.
Note:
This change does not remove the Temp files created during the execution of an “Agent
Update Task” prior to implementing this patch.
20.
Issue:
During Policy Enforcement, when the McAfee Agent failed to compile the policy file, the
policy enforcement failed and the agent crashed on the next Policy Enforcement. (Reference:
423070)
Resolution:
The McAfee Agent now detects failed Policy Enforcements and retries the policy
compilation until it completes successfully.
21.
Issue:
DAT updates were postponed indefinitely and the message “Update will be retried after 3
mins because update is already in progress” appeared repeatedly in the agent log file. (Reference:
424203)
Resolution:
The DAT update process now terminates properly when it detects an error in an FTP
transaction.
22.
Issue:
In environments running the Early Adopter Release (November 11, 2008) the “/
forceinstall” switch did not work when applied against the MA 4.0 Patch 1 package generally
available for download. (Reference: 454619)
Resolution:
The MA 4.0 Patch 1 package has been updated allowing the “/forceinstall” switch to
work as expected.
Issues previously resolved in the policy (Extension) pages are listed below.
1.
Issue:
When a repository was added for one site, the user had to go to every other site and turn
off the repository in the agent policies. In environments with a large number of repositories, this
was very labor intensive. (Reference: 239994)
Resolution:
A checkbox has been added to “Agent Policy on Repository Page” that allows new
repositories to be excluded by default. Now when a repository is added and the new checkbox is
checked, the new repository is added to the disable list for each of the existing repositories.
