McAfee ePolicy Orchestrator 4.0 Release note

McAfee
Brand
McAfee
Model
ePolicy Orchestrator 4.0
Category
Networking
Type
Release note

This manual is also suitable for

Release Notes for McAfee ePolicy Orchestrator 4.0 Patch 5
Thank you for using McAfee
®
ePolicy Orchestrator
®
software version 4.0 Patch 5. This document contains important information
about this release. We strongly recommend that you read the entire document.
Contents
z About this release
z Rating
z Purpose
z Known issues
z Resolved issues
z Installation Instructions
z Finding documentation for McAfee enterprise products
z License attributions
About this release
Patch Release: May 12, 2009
Patch Package: 4.0.0.1293
This release was developed for use with:
z
McAfee ePolicy Orchestrator 4.0
z
McAfee ePolicy Orchestrator 4.0 Patch 1
z
McAfee ePolicy Orchestrator 4.0 Patch 2
z
McAfee ePolicy Orchestrator 4.0 Patch 3
z
McAfee ePolicy Orchestrator 4.0 Patch 4
z
McAfee Total Protection for Endpoint
Make sure you have installed the correct version(s) before using this release.
Rating
McAfee recommends this release for all environments. This update should be applied at the earliest convenience. For more
information, see KB article KB51560
.
Purpose
This document supplements the McAfee ePolicy Orchestrator 4.0 Readme file in the release package, and details fixes included
in ePolicy Orchestrator 4.0 Patch 1, Patch 2, Patch 3, Patch 4, and Patch 5.
Refer to online KnowledgeBase article KB65506
at https://mysupport.mcafee.com/ for the most current information regarding
this release.
Known issues
Known issues in this release of the software are described below.
1. Issue: Not all characters are allowed with ePolicy Orchestrator or SQL usernames and passwords, specifically regarding
use with the ePolicy Orchestrator installer. (Reference: 387883, 395890)
Workaround: Here is a list of the allowed and disallowed characters for the usernames and passwords used by the
ePolicy Orchestrator 4.0 Patch 5 installer. This list is known to be valid only for the ePolicy Orchestrator Patch 5 installer
and might not represent the character sets allowed for previous patch installers.
{
ePO username and password official character set for the Patch 5 installer
Allowed
All printable characters with a hex value of 0x20 – 0x7E (ASCII 32 through 126), with exceptions
listed below.
Exceptions (for both user names and passwords, except as noted)
No leading space, trailing spaces, or passwords made up of solely spaces
No double quotes (")
No leading backslashes, trailing backslashes, or passwords made up of solely backslashes (\)
No dollar signs ($)
No percent signs (%)
Usernames cannot contain a colon (:)
Usernames cannot contain a semi-colon (;)
{ SQL user name and password official character set for the patch 5 installer
Allowed
All printable characters with a hex value of 0x20 – 0x7E (ASCII 32 through 126), with exceptions
listed below.
Exceptions (for both usernames and passwords, except as noted)
No leading space, trailing spaces, or passwords made up of solely spaces
No double quotes (")
No single quotes (')
No backslashes (\)
No percent signs (%)
Usernames cannot contain a dollar sign ($)
Usernames cannot contain a colon (:)
Usernames cannot contain a semi-colon (;)
Password size restriction
Passwords must not exceed 40 bytes in length. For multi-byte characters, this limits the
password to a maximum of 20 characters.
2. Issue: Cluster installation on Windows 2008 server is not supported.
Workaround: Cluster users should not migrate to Windows 2008 at this time.
3. Issue: If the master repository is locked, package check-in fails, causing the installation to fail and roll back.
Workaround: Ensure that there are no repository actions that conflict with the installer. These actions can be currently
running or regularly scheduled repository pulls or replications.
4. Issue: If a previous Patch installation is successfully completed with a database user configured to use a non-default
database schema, the following tables are created:
{
<schema used>.OrionExtensionsBackup
{
<schema used>.OrionConfigurationBackup.
The existence of these files causes the Patch 5 installation to fail. (Reference: 461433)
Workaround: Delete these tables and try the installation again.
5. Issue: When using Windows 2008 ePolicy Orchestrator servers, a blank “Domain” selection drop-down list appears when
the user tries to browse for systems while adding new systems to the System Tree in the ePolicy Orchestrator console.
(Reference: 391040)
Workaround: On Windows 2008 servers, the McAfee ePolicy Orchestrator 4.0.0 Application Server service must have
sufficient permissions to complete the request. For more information, see KB article KB53861
.
6. Issue: On Windows 2008 ePolicy Orchestrator servers, external commands are not executed. (Reference: 433570)
Workaround: On Windows 2008 servers, the McAfee ePolicy Orchestrator 4.0.0 Application Server service must have
sufficient permissions to complete the request. For more information, see KB article KB53862
.
7. Issue: During a cluster installation, the IP address for a client system appears as 128.0.0.0 after an agent push.
(Reference: 435257)
Workaround: After the first successful communication, the IP address reflects the correct address.
8. Issue: When the SQL Server “Nested Triggers” option is disabled, policy assignment timestamps are not updated. This
causes ePolicy Orchestrator to fail to deliver full policies to client systems. (Reference: 406765)
Workaround: Verify that the “Nested Triggers” SQL Server option is enabled for the ePolicy Orchestrator database. For
more information, see KB article KB52512
.
9. Issue: Modifications to policies are not written to the audit log unless they are from Host Intrusion Prevention policies.
(Reference: 470204)
Workaround: None.
Resolved issues
Issues that are resolved in this release are listed below.
1. Issue: If an administrator changes the "Agent-server secure communication keys," non-Windows agents will not use the
new key(s). (Reference: 366792)
Resolution: The agent key updater package now allows non-Windows agents to use new agent-server secure
communication keys.
2. Issue: Distributed repositories are not used for global
updating if the master repository has been updated with packages
other than DATs and Engines. (Reference: 419665)
Resolution: Global updating will use distributed repositories even if the master repository has been updated with
packages other than DATs and Engines.
3. Issue: When the ePO server receives an invalid package from an agent, it logs extraneous data about the invalid
package contents that does not contain information to aid administrators in determining which agent is sending the
invalid package. (Reference: 475017)
Resolution: The server log now contains information about the machines sending malformed SPIPE packages and no
longer contains the contents of invalid packages.
4. Issue: The product summary version information might not match the detailed product properties version information.
In particular, the detailed product properties might include a build number that is missing in the product summary
version information. (Reference: 467030)
Resolution: Product summary version information and the detailed product properties now has the correct values for
products deployed after this Patch has been installed.
Note: This patch does not correct version mismatches from prior deployments, only from deployments after the patch
has been put into place. Mismatches from prior deployments can be corrected by performing an agent wake up with full
properties on those machines reporting a version mismatch.
5. Issue: When 4.0 agents call in to the ePolicy Orchestrator server with a lower sequence number than the ePolicy
Orchestrator server expects, communication is rejected by the ePolicy Orchestrator server. (Reference: 467325, 464319)
Resolution: This Patch introduces several new ways to aid ePolicy Orchestrator administrators in finding sequence error
problems in their network. For more information, see KB article KB65611
.
6. Issue: Active Directory synchronization with the option to move systems causes the AgentGUID to become Null in the
database. (Reference: 461112)
Note: Systems with a Null AgentGUID receive new AgentGUIDs on the next agent-to-server-communication.
Resolution: The AgentGUID are now retained after a system is moved via Active Directory synchronization.
7. Issue: ePolicy Orchestrator servers running on Windows 2000 show the property of "Free Memory" as 0 for all systems
in the System Tree. (Reference: 450048)
Resolution: ePolicy Orchestrator servers running on Windows 2000 now show the correct "Free Memory" for systems in
the System Tree, after each system's next agent-to-server-communication.
8. Issue: When viewing or exporting a report, the Close button in the console does not work properly. Instead of closing,
the Export page then the Result page are displayed in an endless loop. (Reference: 451729)
Resolution: The Close button on the export page now returns the user to a page where they can continue to navigate,
without having to log out or use the browser Back button.
9. Issue: When creating an FTP Distributed Repository in a non-English environment with the Anonymous option selected,
the FTP Distributed Repository "Anonymous" credential is translated to the localized language and stored in the
sitelist.xml instead of "Anonymous". This might cause errors authenticating anonymously to FTP servers on non-English
ePolicy Orchestrator environments. (Reference: 449159)
Resolution: "Anonymous" is now correctly used for all languages in the FTP Distributed Repository credential setup.
10. Issue: ePolicy Orchestrator 4.0 does not support port IDs greater than 32767 for the target port referenced in a client
event, whereas IANA allows for port numbers up to 65535. (Reference: 462087)
Resolution: All valid port values are now supported as the target port in a client event.
11. Issue: The download credentials for a source repository
site cannot be modified in ePolicy Orchestrator after the site has
been created. (Reference: 450163, 480057)
Resolution: The download credentials for source repository sites can now be edited.
12. Issue: Checking a new agent package into the ePolicy Orchestrator repository does not always update the ePolicy
Orchestrator list of supported platforms correctly. (Reference: 467664)
Resolution: Checking a new agent package into the ePolicy Orchestrator repository correctly updates the ePolicy
Orchestrator list of supported platforms.
13. Issue: In some environments, repository pulls from HTTP source repositories might never finish. (Reference: 453274)
Resolution: A new registry setting has been created to work around this issue. The new registry DWORD value is called
"RawHTTPDownloadSocketsOnly" and exists in the HLM\SOFTWARE\Network Associates\ePolicy Orchestrator key.
{
A value of 1 changes the HTTP pull functionality to use Windows Sockets (Winsock).
{
A value of 0, absence of a value, or absence of this key provides the pre-existing pull functionality using Windows
Internet (WinINet).
14. Issue: Replication of specific, selected packages to a distributed repository can intermittently fail if multiple replication
tasks are running simultaneously. (Reference: 462653)
Resolution: A concurrency problem with multiple running replication tasks has been resolved.
15. Issue: The Extra DAT package cannot be deployed to additional platforms without a patch to ePolicy Orchestrator each
time additional platform support is required. (Reference: 397874)
Resolution: The supported platform list for Extra DAT
packages can now be updated without requiring a patch to ePolicy
Orchestrator.
16. Issue: The failure to push an agent can result in the ePO server not being able to create new network mappings, which
can cause pushagent commands and replication to UNC repositories to fail. (Reference: 449780)
Resolution: UNC network resource handles are now returned to the operating system after an agent push failure.
17. Issue: The removal of non-Windows agent packages from the ePolicy Orchestrator master repository prevents agent
update tasks from detecting that a new master server key has been assigned. (Reference: 463964)
Resolution: The removal of non-Windows agent packages no longer prevents agent update tasks from detecting new
master server keys.
18. Issue: The Roll Up server task can intermittently process the same computer twice, causing failure of the task and
computers not to be imported. (Reference: 446354)
Resolution: Computers are now processed only once each, and the server task completes successfully.
19. Issue: Threat-based notification rules can be triggered for non-threat events if the product and category filters of the
rules are satisfied. (Reference: 461917)
Resolution: Threat-based notification rules now are triggered only for threat events.
20. Issue: During an Active Directory synchronization, disabled computer accounts were being imported into ePolicy
Orchestrator. (Reference: 439191)
Resolution: Disabled computer accounts in Active Directory are no longer imported into ePolicy Orchestrator.
Note: If the ePO administrator has configured the Active Directory synchronization to "remove deleted systems" from
the System Tree, deleted systems and disabled systems are automatically removed at the next Active Directory
synchronization.
21. Issue: Installation for ePolicy Orchestrator 4.0 fails if
the password for SQL includes the dollar ($) character. (Reference:
461677)
Resolution: The "$" character is now an acceptable character for the SQL password. For a complete listing of allowed
characters for your ePO and SQL user names and passwords, refer to the first entry under Known Issues (above).
22. Issue: An event purge fails for Purge with 0 Days. (Reference: 471355)
Resolution: An event log will Purge with 0 days.
23. Issue: Users get a message "Exception occurred in OrionCore.dialogBoxOkHandler!" when trying to purge Notification
Logs. (Reference: 472788)
Resolution: Users no longer receive an exception message when purging the Notification Logs.
24. Issue: Items Event Group and Event Type cannot be sorted in the Response Builder. (Reference: 424139)
Resolution: Event Group and Event Type are now sortable, based on the users locale.
25. Issue: Failed to create chart “FSE: FoundScore Trend for Last 30 Days” is displayed when My FoundScore is selected.
(Reference: 428041)
Resolution: Chart creation is now fixed for “FSE: FoundScore Trend for Last 30 Days” when selecting My FoundScore.
26. Issue: Incorrect text appeared in options to filter data for "Description text goes here." (Reference: 428904)
Resolution: This text has been updated to read "Build table filter criteria."
27. Issue: The console date defaults to US format (MM/DD/YY). (Reference: 430784)
Resolution: The date is set to correspond to the system locale format.
28. Issue: The error message "Page cannot be found" is displayed when the Back button is clicked on within the Notification
Log page. (Reference: 449202)
Resolution: The Back button has now been fixed for the Notification Log page.
29. Issue: The Grouped Bar Chart report shows bars in each group, even if not applicable. (Reference: 450500)
Resolution: The Grouped Bar Charts no longer display bars with a group count of "0".
30. Issue: Policy Auditor Dashboard tables incorrectly display the column title "Total" on localized builds. (Reference:
455340)
Resolution: The column title for the Grouped Summary Table has been fixed on localized builds.
31. Issue: Users, within the same admin group, can view the console of the last admin user’s session, until the page is
refreshed. (Reference: 456088)
Resolution: The Admin console session cache now uses a different method to update the cache key.
32. Issue: Users cannot use "§" in the ePolicy Orchestrator user name or password. (Reference: 457497)
Resolution: We now allow the use of "§" in ePolicy Orchestrator user name and password. For a complete listing of
allowed characters for your ePO and SQL user names and passwords, please refer to the first entry under Known Issues
(above).
33. Issue: Exporting a query to email with "Compress the output files" enabled fails. (Reference: 462057)
Resolution: Exporting a query to email with "Compress the output files" enabled is now successful.
34.
Issue: Titles in the export table are truncated when output to PDF format. (Reference: 462067)
Resolution: Titles in PDF format export are no longer truncated.
35. Issue: Radio buttons from one server task action alter the radio buttons for the subsequent action. (Reference: 463196)
Resolution: Radio buttons from one server task action no longer alter the radio buttons for the subsequent action.
36. Issue: Advanced filters are not working correctly when defined systems are selected on the page. (Reference: 472299)
Resolution: Advanced filters are now filtering systems correctly when defined systems are selected on the page.
37. Issue: Users cannot see all created dashboards if they exceed the static viewable area. (Reference: 472925)
Resolution: A scrollbar now appears on the dashboard page if the viewable area is exceeded.
Issues from the Patch 4 release of the software that are resolved in this release are listed below.
1. Issue: When an event package contained System Compliance Profiler and another point-product’s events, the System
Compliance Profiler events would not be saved to the database. (Reference: 370718, 442064)
Resolution: System Compliance Profiler events are now saved in the database when included with other point-product
events.
2. Issue: Replication to a UNC site could fail reporting error code 5 when different download and replication credentials are
specified. (Reference: 411431)
Resolution: The download and UNC replication sessions have been modified to operate independently.
3. Issue: Registered executables with reserved HTML characters in their names could not be duplicated. (Reference:
414572)
Resolution: Registered executable names can now contain reserved HTML characters and be duplicated successfully.
4. Issue: Non-global administrators would receive the message “You are not authorized for this operation” when
attempting to review McAfee Agent push failures. (Reference: 420764)
Resolution: The correct permissions are now enforced, allowing authorized users to review McAfee Agent push failures.
5. Issue: When manually checking in a package to the ePolicy Orchestrator’s master repository, a copy of the package
would be abandoned in a temporary location. (Reference: 423560)
Resolution: The Patch installation removes all packages in the temporary location and prevents additional packages
from being abandoned.
6. Issue: Purge Event Log Tasks would not delete events when the selection “Purge records older than:” was chosen.
(Reference: 424692)
Resolution: The Purge Event Log Tasks routine has been modified to properly delete “Purge records older than:” events.
7. Issue: The Client Task Schedule option, “Only run this task once a day,” would not remain selected or be enforced when
a task was saved. (Reference: 431479)
Resolution: The selection of Client Task Schedule option, “Only run this task once a day,” is now properly saved and
enforced.
8. Issue: When a system requested full policies, the Host Intrusion Protection policies were incomplete when delivered.
(Reference: 432785)
Resolution: The policy preparation routine was modified to ensure that Host Intrusion Protection policies are generated
correctly.
9. Issue: An unexpected error occurred when executing an Events type query with a specified Tag Filter. (Reference:
433592)
Resolution: The user is now able to execute Event type queries with a Tag Filter.
10. Issue: The VirusScan Enterprise DAT Deployment report would display “unexpected error occurred” when attempting to
drill into a DAT group of version “N/A.” (Reference: 437213)
Resolution: The VirusScan Enterprise DAT Deployment report has been modified to allow drilling into a DAT group of
version “N/A.”
11. Issue: Event ID 1038 was incorrectly associated with the event category, “Virus Detected but not
Removed.” (Reference: 437525)
Resolution: Event ID 1038 indicates that no particular action was taken and is now associated with the event category
“Non-compliance.”
12. Issue: When an installation failed and reverted to the previous version, the Site Manager file was not re-registered.
(Reference: 437841)
Resolution: The installation routine has been modified to correctly re-register all critical files when reverting to the
previous version.
13. Issue: The installation routine could replace Tomcat configuration files, causing Tomcat to fail to start. (Reference:
438104)
Resolution: The installation routine has been modified to avoid replacing Tomcat configuration files.
14. Issue: Saving an Enforcement Message Policy Client Assignment could result in the message “unexpected error
occurred.” (Reference: 439548)
Resolution: The Enforcement Message Policy Client Assignment process has been modified to correctly save policy
updates.
15. Issue: Improperly formatted event files resulted in prolonged Event Parser performance degradation. (Reference:
440091)
Resolution: The Event Parser has been modified to skip improperly formatted event files.
16. Issue: The installation process would fail if the SQL Server Agent service was not running. (Reference: 441846)
Resolution: The installation routine has been modified, removing the dependency on the SQL Server Agent service.
17. Issue: Changing the owner of a policy with a large number of registered users could result in error. (Reference: 442364)
Resolution: Changing the owner of a policy is no longer dependant on the number of registered users.
18. Issue: Communication with ePolicy Orchestrator would fail when a system reported its CPU Speed as greater than
32,767 MHz. (Reference: 442734)
Resolution: The ePolicy Orchestrator system update process has been modified to limit CPU Speed properties to 32,767
MHz, allowing the system update to succeed.
19. Issue: Setting the Filter Data option on the Event Log had no effect on the returned events. (Reference: 427905,
434696, 440692, 443370, 444508, 444813, 445867)
Resolution: The process for filtering the Event Log has been modified to include the correct Filter Data options.
20. Issue: When configuring new client tasks in the Client Task wizard, the list of available client task types included client
types the user could only view. (Reference: 443963)
Resolution: The Client Task wizard has been modified to list only the client task types the user has permission to edit.
21. Issue: When a Microsoft Windows-based McAfee Agent was uninstalled through ePolicy Orchestrator before it first
communicated with ePolicy Orchestrator, the corresponding record would not be removed from the ePolicy Orchestrator
database. This system would then continue to be included in compliance reporting, resulting in incorrect information.
(Reference: 444928)
Resolution: Now when a Microsoft Windows-based McAfee Agent is uninstalled before its first communication with
ePolicy Orchestrator, the corresponding record is marked for removal and removed when necessary.
22. Issue: Adding a filter to a list of systems with a specific tag had no effect on the systems returned. (Reference: 445161)
Resolution: The process for filtering tagged systems has been modified to filter the results correctly.
23. Issue: Non-Microsoft Windows-based McAfee Agents that
failed to uninstall through ePolicy Orchestrator, were manually
uninstalled and reinstalled, never reappeared in ePolicy Orchestrator. (Reference: 445488)
Resolution: Non-Microsoft Windows-based McAfee Agents are now listed in ePolicy Orchestrator as expected.
24. Issue: SuperDAT packages could not be deployed from ePolicy Orchestrator to Microsoft Windows 2008 Server and
Microsoft Windows Vista systems. (Reference: 450405)
Resolution: SuperDAT packages can now be deployed from ePolicy Orchestrator to Microsoft Windows 2008 Server and
Microsoft Windows Vista systems.
25. Issue: Under certain conditions the server was becoming non-responsive, and non-paged pool memory for apache.exe
would grow very large. (Reference: 447222)
Resolution: The condition has been addressed so that the server does not become unresponsive, but rather waits until
error handling services are running before issuing error pages.
26. Issue: The “unexpected error occurred” page would be displayed when the user clicked “Update Filter” or “Remove
Filter” from within the Notification Log Report. (Reference: 450126)
Resolution: There is no longer an error when the user clicks the “Update Filter” or “Remove Filter” links.
27. Issue: Upgrading the Issues extension to version 1.5.1 failed. (Reference: 431353)
Resolution: Upgrading the Issue extension to version 1.5.1 now is performed correctly.
28. Issue: There was a failure when trying to install a particular version of the Help files. (Reference: 450059)
Resolution: Help files are now installed without incident.
29. Issue: The ePolicy Orchestrator Help Index tab was empty after upgrading. (Reference: 446253)
Resolution: The ePolicy Orchestrator Help Index tab is now correctly populated.
30. Issue: Remote command execution was failing if the admin password included non-standard ASCII characters, HI-ASCII
characters, or double-byte characters. (Reference: 395890)
Resolution: Remote command execution now works correctly if the admin password contains any of the characters
mentioned.
31. Issue: Pie charts did not have the option to limit the number of pie slices when sorting labels from A to Z or Z to A.
(Reference: 428377)
Resolution: The user now has the option to select the
number of pie slices when sorting labels from A to Z or Z to A in a
pie chart.
32. Issue: Dashboards that contained double quotation marks in the returned data displayed JavaScript errors when the
dashboards were rendered. (Reference: 438775)
Resolution: The dashboards are now correctly displayed if there are double quotation marks in the returned data of the
dashboard.
33. Issue: Double-byte characters were causing problems when submitted to the server on some pages. (Reference:
442581)
Resolution: The encoding has been changed so that double-byte characters do not cause a problem.
34. Issue: The file names of PDF attachments were garbled when sent to a Lotus Notes server. (Reference: 445256)
Resolution: The configuration type has been changed so that the file names are no longer jumbled.
35. Issue: An unexpected error occurred when exporting an audit log query. (Reference: 447865)
Resolution: The user is now able to export audit log queries.
36. Issue: A “Page has expired” error message would be displayed when clicking the Back button after drilling down into
query details. (Reference: 447968)
Resolution: A warning is no longer displayed when clicking the Back button after drilling down into query details.
37. Issue: If a query was exported to PDF with drill-down tables, the drill-down data was not exported to the report.
(Reference: 450205)
Resolution: The drill-down data is now exported if the option is specified in the export page.
38. Issue: The Patch installer was failing when it tried to install on a previously installed version of ePolicy Orchestrator.
(Reference: 447907)
Resolution: The Patch installer now installs correctly on top of ePolicy Orchestrator 4.0 and its patches.
39. Issue: A newer version of the Java Runtime Environment was available. (Reference: 442560)
Resolution: The Patch updates the Java Runtime Environment to version 1.6.0_07.
40. Issue: The Patch installer failed in clustered systems if backup files already existed on the target system. (Reference:
451959)
Resolution: The Patch installer now works correctly, regardless of whether backup files exist on the target system.
41. Issue: Filtering on a Boolean property did not work. (Reference: 426018)
Resolution: Filtering on a Boolean property now works correctly.
42. Issue: Exporting data as a result of an automated server task caused database problems. (Reference: 426432)
Resolution: Exporting data in the Comma Seperated Value (csv) format during an automated server task finishes
correctly.
43. Issue: Filtering in the System Tree was not working correctly. (Reference: 437587)
Resolution: Filtering in the System Tree area now works correctly.
44. Issue: The language selection was not remembered after logging out. (Reference: 438245)
Resolution: The system now remembers the language selected at the last log-on.
45. Issue: The user could not delete an automated response. (Reference: 446974)
Resolution: A user with the correct permissions can now delete an automated response.
46. Issue: The user was not able to complete the server mapping when creating a new ticketing server. (Reference:
447344)
Resolution: The user can now complete the mapping when creating a ticketing server.
47. Issue: When a user tried to assign policies by drilling down in a Compliance Summary query, the user got an
“Unexpected Error” and was unable to assign policies. (Reference: 448620)
Resolution: The user can now successfully assign policies.
48. Issue: Column selection did not work from the System Tree page. (Reference: 448653)
Resolution: Column selection on the System Tree page now works correctly.
49. Issue: An unexpected error occurred while trying to remove the filter from the query in the query page. (Reference:
450209)
Resolution: The user can now successfully remove filters from the query page.
50. Issue: Clicking the update filter button would cause an unexpected error. (Reference: 450224)
Resolution: Clicking the update filter button no longer causes an unexpected error.
51. Issue: Making modifications to the Host Intrusion Prevention events page caused JavaScript errors. (Reference: 450463)
Resolution: There are no more JavaScript errors when making modifications to the Host Intrusion Prevention events
page.
52. Issue: Queries import displayed an error stating that the user was not authorized for the operation. (Reference:
451473)
Resolution: Query import is now properly validated against the user's permissions.
53. Issue: The dashboard data for one administrator was viewable by another administrator upon initial log in. (Reference:
456088, 456090)
Resolution: Users now see only the dashboard data they are authorized to view.
Issues from the Patch 3 release of the software that are resolved in this release are listed below.
1. Issue: SuperAgent Repositories on Windows Vista and
Windows 2008 systems did not appear as Distributed Repositories
in the ePolicy Orchestrator console. (Reference: 371932, 405958)
Resolution: SuperAgent Repositories on Windows Vista and Windows 2008 systems now appear as Distributed
Repositories in the ePolicy Orchestrator console.
2. Issue: A synchronization point could not be created, edited, or deleted for the “My Organization” group. (Reference:
384135)
Resolution: A synchronization point for the “My Organization” group can now be created, edited, and deleted.
3. Issue: Grouped Summary Table queries could not be ordered by label values when grouped by a version number
column. For example, a group summary of managed systems grouped by group name and DAT version could not be
ordered by the group name label and then by DAT version label. (Reference: 386121)
Resolution: Grouped Summary Table queries can now be ordered by the label values when grouped by a version
number column.
4. Issue: When configuring an Active Directory synchronization group, the “Browse” button for browsing and “Add” button
for exceptions were disabled unless the user first selected an NT domain synchronization type. (Reference: 391830)
Resolution: The “Browse” and “Add” buttons are now enabled without having to first select an NT domain
synchronization type.
5. Issue: Active Directory synchronization failed when a synchronized folder name included a semicolon. (Reference:
392803)
Resolution: Active Directory folder names can now contain a semicolon.
6. Issue: When viewing the system properties of a system that has never communicated with the ePolicy Orchestrator
server, clicking on the “more” link resulted in a blank page. (Reference: 398952)
Resolution: Selecting the “more” link for a managed system
that has never communicated with the ePolicy Orchestrator
server no longer results in a blank page.
7. Issue: ExtraDAT packages were not updated on Windows Vista or Windows 2008 Server managed systems. (Reference:
400563)
Resolution: ExtraDAT packages are now updated on Windows Vista and Windows 2008 Server managed systems.
Note: All ExtraDAT packages in the repository must be reinstalled before this change takes effect.
8. Issue: The McAfee Agent failed to enforce Host Intrusion Protection rule policies when the rule name contained an angle
bracket character. (Reference: 400808)
Resolution: The McAfee Agent now enforces Host Intrusion Protection rule policies regardless of the rule name.
9. Issue: A client task with a “repeat starting at” schedule could have a repeat duration that was less than the repeat
interval, resulting in the client task never running. (Reference: 401301)
Resolution: New or modified client tasks with a “repeat starting at” schedule must now have a repeat duration that is
greater than or equal to the repeat interval.
10. Issue: When viewing the results of a query for Events, the “Show Related Systems” action was not available.
(Reference: 402250)
Resolution: The “Show Related Systems” action is now available for Event queries.
11. Issue: Importing managed systems into the System Tree from a Unicode text file created erroneous entries in the
System Tree. (Reference: 402271)
Resolution: An error message is now displayed when non-UTF-8 encoded text files are imported, and the System Tree
is unaffected.
12. Issue: An updated version of the System Compliance Profiler 2.0 extension is available. (Reference: 404381)
Resolution: Version 2.0.2.191 of the System Compliance Profiler 2.0 extension is now installed during ePolicy
Orchestrator 4.0 Patch 3.
13. Issue: Running a previous upgrade a second time, after it had been successfully installed, failed. (Reference: 405288)
Resolution: The upgrade can now be run multiple times.
14. Issue: VirusScan DAT and Engine version information was missing on Managed System Rollup queries. (Reference:
405383)
Resolution: Managed System Rollup queries now include VirusScan DAT and Engine version information.
15. Issue: In the ePolicy Orchestrator console, the option that uninstalls the McAfee Agent from managed systems was not
supported by non-Windows agents, but it was a selectable option. When this option was selected and the agents were
manually uninstalled and later reinstalled, the managed systems never reappeared in the ePolicy Orchestrator System
Tree. (Reference: 405859)
Resolution: A non-Windows managed system, which successfully reinstalls the McAfee Agent after a failed agent
uninstall from the ePolicy Orchestrator console, now reappears in the ePolicy Orchestrator console System Tree.
16. Issue: An ePolicy Orchestrator 4.0 upgrade failed when the SQL Server UDP port was enabled for the initial ePolicy
Orchestrator 4.0 installation and disabled before upgrading. The inverse scenario also caused the upgrade to fail.
(Reference: 406814, 415166)
Resolution: The ePolicy Orchestrator 4.0 upgrade no longer fails when the SQL Server UDP port was enabled for the
initial ePolicy Orchestrator 4.0 installation and disabled before upgrading. The inverse scenario has also been corrected.
17. Issue: The Synchronization Group Agent Deployment checkbox, “Force installation over existing Version,” does not
remain selected after saving the Synchronization Group and accessing it again for editing. (Reference: 410246, 426930)
Resolution: The Synchronization Group Agent Deployment checkbox, “Force installation over existing Version,” now
retains the selected value.
18. Issue: Installations in clustered server environments incorrectly set the ePolicy Orchestrator services to start
“Automatically.” (Reference: 410543)
Resolution: Installations in clustered server environments now correctly set the ePolicy Orchestrator services to start
“Manually.”
19. Issue: The managed system name is truncated to a length of 14 characters on the ePolicy Orchestrator console
“Systems” tab. (Reference: 410779)
Resolution: The column “DNS Name,” containing a “Fully Qualified Domain Name,” can now be selected as the managed
system name on the ePolicy Orchestrator console “Systems” tab.
20. Issue: The import policies process did not verify the ownership of the existing policies, which could result in policies
being overwritten by users other than the owner. (Reference: 410917)
Resolution: The import policies process now verifies the ownership of the existing policies and prevents policies from
being overwritten by users other than the owner.
21. Issue: Changes to existing policies were not recorded in the Audit Log. (Reference: 412589)
Resolution: Changes to existing policies are now recorded in the Audit Log.
22. Issue: The ePolicy Orchestrator Alerting extension, used by Rogue System Detection 2.0, was not localized. (Reference:
412661)
Resolution: The ePolicy Orchestrator Alerting extension is upgraded to a localized version, on ePolicy Orchestrator
servers with Rogue System Detection 2.0 installed.
23. Issue: The ePolicy Orchestrator server failed to respond if a corrupt package file was checked in. (Reference: 413466)
Resolution: The ePolicy Orchestrator server responds correctly when a corrupt package file is checked in.
24. Issue: Editing a client task could result in the error message “An Unexpected error occurred” being displayed in the
ePolicy Orchestrator console. (Reference: 413963)
Resolution: Editing client tasks no longer results in unexpected errors.
25. Issue: Client tasks, for managed product extensions that do not have a default policy, were not available for
configuration. (Reference: 415739)
Resolution: Client tasks, for managed product extensions that do not have a default policy, are now available for
configuration.
26. Issue: An ePolicy Orchestrator 4.0 upgrade stopped installing the included managed product extensions after the first
failure was discovered. (Reference: 415974)
Resolution: An ePolicy Orchestrator 4.0 upgrade now attempts to install each of the included managed product
extensions, even if an error occurs during the installation of a previous managed product extension.
27. Issue: When the ePolicy Orchestrator server did not have a “Master Agent to Server Communication Key,” the ePolicy
Orchestrator 4.0 upgrade failed, leaving the ePolicy Orchestrator server in a non-functional state. (Reference: 419859)
Resolution: The ePolicy Orchestrator 4.0 upgrade now verifies the ePolicy Orchestrator server has a “Master Agent to
Server Communication Key” before it starts the upgrade.
28. Issue: An updated version of the Host Intrusion Prevention 7.0 extension is available. (Reference: 422819)
Resolution: Version 7.0.1.133 of the Host Intrusion
Prevention 7.0 extension is installed during the ePolicy Orchestrator
4.0 upgrade.
29. Issue: The “delayload.log” file could grow without limit in the root (C:\) of the ePolicy Orchestrator server. (Reference:
425738)
Resolution: The “delayload.log” file is no longer used.
Note: The ePolicy Orchestrator 4.0 upgrade process does not remove existing “delayload.log” files.
30. Issue: Event queries could not be chained to ePolicy Orchestrator server task actions. (Reference: 427217)
Resolution: Event queries can now be chained to ePolicy Orchestrator server task actions.
31. Issue: Server tasks could not run an event query that was
chained to these actions: apply, clear, or exclude tag actions.
(Reference: 427708)
Resolution: Server tasks can now run an event query chained to these actions: apply, clear, or exclude tag actions.
32. Issue: The “View Logs” button could fail to display the correct installation log files after an ePolicy Orchestrator 4.0
upgrade failure. (Reference: 429819)
Resolution: The “View Logs” button now displays the main
installation log files after an ePolicy Orchestrator 4.0 upgrade
failure.
33. Issue: An initial ePolicy Orchestrator 4.0 installation, on a system with a local MSDE database and the UDP port
disabled, could result in incorrect ePolicy Orchestrator service dependencies. (Reference: 430390)
Resolution: The ePolicy Orchestrator 4.0 upgrade repairs the ePolicy Orchestrator service dependencies for systems
installed with a local MSDE database and the UDP port disabled.
34. Issue: Miscellaneous language translation and localization issues were reported. (Reference: 429847, 430581)
Resolution: The reported language translation and localization issues were addressed.
35. Issue: An updated version of the ePolicy Orchestrator Help extension is available. (Reference: 433198)
Resolution: Version 1.0.6 of the ePolicy Orchestrator Help
extension is now installed during the ePolicy Orchestrator 4.0
upgrade.
36. Issue: Inconsistent event times would appear in the Server Task Log. (Reference: 417725)
Resolution: The problem of inconsistent event times appearing in the Server Task Log after applying patches has been
fixed.
37. Issue: Console logons using NT authentication worked only when the ePolicy Orchestrator console was located in a
domain where a two-way trust existed between the console and ePolicy Orchestrator server domains. (Reference:
395894)
Resolution: Authentication support for multiple domain
controllers has been added to the product. For more information
see KB article 616709.
38. Issue: The date formats are incorrect for the English (United Kingdom) locale. (Reference: 362588)
Resolution: A new choice of English (United Kingdom) has been added to the Language drop-down list of the ePolicy
Orchestrator Logon screen.
39. Issue: When installing managed product extensions on
ePolicy Orchestrator, the installation could fail with the message:
“ERROR: java.lang.OutOfMemoryError: PermGen space.” (Reference: 407724)
Resolution: The PermGen Memory allocation size has been increased to 128 MB on clean installations and upgrades.
(For more information see KB article: 615843)
40. Issue: There was a performance bottleneck when processing a large number of unrelated dashboard requests.
(Reference: 407724)
Resolution: Performance has been improved to allow many users to view the dashboard.
41. Issue: Dashboard related caching was not functioning correctly, which caused the user to see stale data. (Reference:
411646)
Resolution: Dashboard caching has been fixed so the user views the most current data.
42. Issue: An unexpected error occurred while creating a query using a Grouped Bar Chart with Boolean types of data.
(Reference: 415069)
Resolution: Grouped Bar Charts now correctly display data when using any of the supported data types.
43. Issue: Drilling down into a chart, a user could see an unexpected error page if there was a null value in the returned
time field. (Reference: 413954, 419692)
Resolution: Chart drill-down now works as expected and no longer returns an error when drilling down into null time-
based reports.
44. Issue: Some international characters caused problems in the server log details page. (Reference: 411088)
Resolution: Log entries are now correctly formatted prior to being written to the server task log.
Issues from the Patch 2 release of the software that are resolved in this release are listed below.
1. Issue: When accessing the “Systems/Client Tasks” tab of the ePolicy Orchestrator console, users without Administrator
rights receive the error “An unexpected Error has Occurred.” (Reference:360915, 400549)
Resolution: Users without Administrator rights can now access the “Systems/Client Tasks” tab.
2. Issue: The Product Catalog displayed hidden policy assignments. (Reference:359111)
Resolution: The Product Catalog no longer displays hidden policy assignments.
3. Issue: New DAT detection and installation scripts are available for inclusion in the Patch. (Reference:395895)
Resolution: This Patch includes current DAT detection and installation scripts.
4. Issue: On the Actions page, the Schedule Pull server task incorrectly invoked the “Purge Server Task Log” action.
(Reference:358624)
Resolution: The Schedule Pull server task now correctly invokes the “Repository Pull” option.
5. Issue: Distributed repositories from different ePolicy Orchestrator servers could not be used as a source repository in
another ePolicy Orchestrator server. The second ePolicy Orchestrator server failed to validate the package even after
importing the source repository’s public key. (Reference:375338)
Resolution: Distributed repositories from a different ePolicy Orchestrator server can now be used as source repositories
for other ePolicy Orchestrator servers.
6. Issue: ePolicy Orchestrator extensions did not display their build number as part of their version on the
Configuration/Extensions tab. (Reference:382248)
Resolution: ePolicy Orchestrator extensions now display their product build number as part of their version number in
the Configuration/Extensions tab.
7. Issue: When an incompatible query chart type or result
type was used for the Generate Compliance Event task, an error
message indicated that a query of chart type was needed. The correct required query type is a Boolean Pie Chart.
(Reference:386081)
Resolution: When an incompatible query type is used for the Generate Compliance Event task, the following error
message is now displayed: “Validation error: Invalid input from the Run Query command. The query must be of both
Managed Systems result type and Boolean pie chart type.”
8. Issue: An agent package could fail to rebuild when one of the package’s files had been updated. (Reference:391143)
Resolution: An agent package is now rebuilt for agents even after files in the package have been updated.
9. Issue: There is no way to purge the Rollup Compliance, Rollup Systems, and Compliance History tables.
(Reference:364364)
Resolution: A purge action has been added for the Rollup Systems, Rollup Compliance, and Compliance History
registered types.
10. Issue: An audit log entry was not created when a package was deleted from a repository. (Reference:384013)
Resolution: An audit log entry is now created when a package is deleted from a repository.
11. Issue: When exporting Systems to a CSV file, a blank window appeared and the export failed. (Reference:405890)
Resolution: Systems can now be exported to a CSV file.
12. Issue: When exporting query results, a blank dialog box was displayed due to a NullPointerException.
(Reference:387413)
Resolution: Query results can now be successfully exported.
13. Issue: When exporting query results to CSV file, Tags, Operating System, and Installed Products show as numbers
(Reference: 401779)
Resolution: The OS column now displays the Operating System for the system.
14. Issue: In VirusScan Enterprise, when exporting to PDF, the Detection Response Summary shows incorrect information.
(Reference: 384708)
Resolution: PDF exports now show correct information in the Detection Response Summary.
15. Issue: When clicking the Group Bar header for VirusScan Enterprise queries, “An Unexpected error” is generated.
(Reference: 387594)
Resolution: The Group Bar header for VirusScan Enterprise queries no longer generates an error.
16. Issue: In reports, the graph and the drilled-down report display different information for months. (Reference: 385445,
387247)
Resolution: The graph report shows the correct month or generated events accordingly.
17. Issue: An exception is encountered while exporting to PDF, when numeric values in the file name exist. (Reference:
402642)
Resolution: The customer can now give alpha and numeric names to PDF files.
18. Issue: SQL rollback and recovery with patch upgrade failure was not implemented. (Reference: 403002)
Resolution: The database schema is now kept in synch with the server, allowing the ePolicy Orchestrator Services to
start on recovery.
19. Issue: Reinstalling a plug-in with an external library dependency causes a NoClassDefFound exception. (Reference:
384136)
Resolution: Reinstalling a plug-in with an external library dependency now works as expected.
20. Issue: The calendar popup date picker displays the wrong date. (Reference: 402135)
Resolution: The calendar popup now correctly displays 31 days for the date picker.
21. Issue: JFreeChart should be updated to version 1.0.8 to address a security advisory. (Reference: 384582)
Resolution: JFreeChart has been upgraded to the latest version.
22. Issue: When printing and exporting, the wrong IP address was displayed in the CSV Report format. (Reference: 364866)
Resolution: The IP address now converts to IPv4 correctly.
Issues from the Patch 1 release of the software that are resolved in this release are listed below.
1. Issue: A non-global administrator user was able to perform AD/Domain sync from the Synchronization Settings page.
(Reference: 360307)
Resolution: The “Synchronize now” and “Compare and Update” buttons are now disabled for non-global administrator
users on the Synchronization Settings page.
2. Issue: The Event Parser to Notifications communication was on the same port as the user interface creating contention.
(Reference: 361078)
Resolution: Event Parser to Notifications communication is now on a new secure port.
3. Issue: The performance monitor counters for Event Parser did not include “events per second.” (Reference: 363122)
Resolution: The performance monitor counters for Event Parser now include “events per second.”
4. Issue: Certain dates were not reported in a “normalized” format by extensions. (Reference: 366925)
Resolution: The process for importing dates from extensions now uses a consistent “normalized” format.
5. Issue: Individual products should have a single set of
properties in the database. However, some products had duplicate
sets. (Reference: 369040)
Resolution: Individual products now have only one set of properties in the database.
6. Issue: When an extension was removed right after it was installed, an error message appeared, stating that the
extension could not be fully removed. (Reference: 373129)
Resolution: Now extensions can be removed right after being installed without generating an error.
7. Issue: In the McAfee Agent “More” properties, the Last Update property displayed the server’s time rather than
Coordinated Universal Time. (Reference: 382716)
Resolution: The Last Update property in the McAfee Agent “More” properties now displays Coordinated Universal Time.
8. Issue: In rare cases, when a user logged on to the
ePolicy Orchestrator console, the Application Server Service restarted
or wrote crash information in the ePolicy Orchestrator Application Server log file. (Reference: 382685)
Resolution: A user logging on to the ePolicy Orchestrator console no longer causes the Application Server Service to
restart or write crash information in the ePolicy Orchestrator Application Server log file.
9. Issue: When downloading DATs only, the Task details incorrectly stated that additional packages were not downloaded
because “no managed product is installed.” (Reference: 361989)
Resolution: Packages not selected for download are now identified in the Server Task log file as “not selected for
selective pull” rather than displaying the message “no managed product is installed.”
10. Issue: ePolicy Orchestrator 3.6 exported policies that included McAfee default policies. When imported in to ePolicy
Orchestrator 4.0, the default policies resulted in an error. (Reference: 364021)
Resolution: McAfee default policies are now ignored when importing XML-based policy files.
11. Issue: The NT Domain Sync process removed subgroups and computers defined later in the System Tree group.
(Reference: 364380)
Resolution: The NT Domain Sync process no longer removes subgroups.
12. Issue: A failed SuperAgent replication was reported in the Task Log file as a GUID rather than as the system name of
the failed repository. (Reference: 382679)
Resolution: A failed SuperAgent replication is now
reported in the Task Log file as the SuperAgent name (which includes
the system name), rather than as the system name of the failed repository.
13. Issue: Saving an inherited task at the subgroup level broke the task’s inheritance. (Reference: 353133)
Resolution: Saving an inherited task at the subgroup level no longer breaks the task’s inheritance.
14. Issue: When defining a Registered Server, the field for the database port was not available for user input and port 1433
was always used. (Reference: 366558)
Resolution: When defining a Registered Server, the user is now allowed to type a database port number. This value is
also editable by the user when specifying properties for registered servers.
15. Issue: When a query for rolled-up managed systems was made from a remote server, the system details were not
displayed. (Reference: 360857)
Resolution: Now when a query for rolled-up managed systems is made from a remote server, the system details are
available.
16. Issue: The audit log description entries for paste assignment actions did not include the source and destination node
names. (Reference: 363210)
Resolution: The audit log description entries for paste assignment actions now include the source and destination node
names.
17. Issue: On the Server Settings | Repository Packages page, the setting for “Allow package check-in for any repository
branch” incorrectly displayed “Caution: When this setting is enabled, agent versions 3.6 and prior can only use DAT and
Engine packages located in branches other than ‘Current.’” (Reference: 364777)
Resolution: The Server Settings | Repository Packages page setting for “Allow package check-in for any repository
branch” now displays the following: “If Yes is selected, deployable packages can be checked into the Previous and
Evaluation branches. However, only agent version 4.0 and later can use the Previous and Evaluation branches for
deployable files. Agent version 3.6.0 and earlier can only use the Current branch’s deployable packages, regardless of
this setting.”
18. Issue: When importing policies from the Product Policy Import page, an error occurred if the user clicked “OK” more
than once. (Reference: 366333)
Resolution: When importing policies from the Product Policy Import page, the “OK” button can now be clicked only
once.
19. Issue: The Event Generated Time (UTC) date and time fields on the Reporting | Event Log page were formatted using
English formatting rules rather than the formatting rules for the user-selected language. (Reference: 366751)
Resolution: The Event Generated Time (UTC) date and time
fields on the Reporting | Event Log page are now formatted
with the user’s selected language.
20. Issue: The computer property “Is 64 bit OS” was shown as “unknown” on the Query Filters, Tag Criteria, and System
Details pages. (Reference: 369885)
Resolution: The computer property “Is 64 bit OS” now includes the end node state on the Query Filters, Tag Criteria,
and System Details pages for end nodes using McAfee Agent 4.0. This property continues to show “unknown” for end
nodes running Common Management Agents released prior to McAfee Agent 4.0.
21. Issue: The Group Sorting Criteria List on the System Tree did not remove duplicate IP range entries when it was saved.
(Reference: 374201)
Resolution: Saving the Group Sorting Criteria List on the System Tree now removes exact string matches for IP
addresses and IP ranges.
22. Issue: Step 2 of the Editing a Registered Server wizard did not allow the password to be changed. (Reference: 315318)
Resolution: Step 2 of the Editing a Registered Server wizard now allows the password to be changed.
23. Issue: Clicking the “Version” header on the Master Repository page does not sort the report by version. (Reference:
320509)
Resolution: Clicking the “Version” header on the Master Repository page now sorts the report by version.
24. Issue: When modifying a new Update Task (Systems | Schedule tab | Options), data can be entered even though the
fields appear disabled. (Reference: 335892)
Resolution: On the Systems | Schedule tab | Options page, data can no longer be entered in the disabled fields when
modifying a new Update Task.
25. Issue: When creating an Assign Policy Server Task, if the wrong type of query was chosen for the selected action, the
message read: “Task validation failure: Assign Policy validation fail.” (Reference: 355840)
Resolution: When creating an Assign Policy Server Task, now if the wrong type of query is chosen for the selected
action, the message reads: “The selected query returned a summary chart instead of a table of systems. The Assign
Policy action can only be used with queries that return a table of systems.”
26. Issue: When configuring UNC distributed repositories, the text “Replication UNC path” was incorrectly displayed.
(Reference: 356957)
Resolution: Now the text “UNC path” is displayed when configuring UNC Distributed Repositories and “Replication UNC
path” is displayed when configuring HTTP Distributed Repositories.
27. Issue: The title bar on the Enforcement | Broken Inheritance page incorrectly displayed “.EPO_ENFORCE” and the entry
in the Assigned Policy column incorrectly displayed “EPO_ENFORCE_NO.” (Reference: 360904)
Resolution: # The title bar on the Enforcement | Broken Inheritance page is now based on the product’s Category ID
and the Assigned Policy column now displays “Not Enforcing.”
28. Issue: The “Schedule Pull” button was enabled for users with the permission set “View packages and
repositories.” (Reference: 361017)
Resolution: The “Schedule Pull” button is now disabled for users with the permission set “View packages and
repositories.”
29. Issue: On the Permission Sets | System Tree Access page, when “My Organization” was selected, the selected node was
not displayed. (Reference: 361205)
Resolution: Now when “My Organization” is selected, the top of the System Tree is displayed if the user has access to
the root level, and an indicator was added to highlight when the user does not have root level access.
30. Issue: When creating a distributed repository and a user correctly entered download credentials on the Credentials
page, the Summary page incorrectly displayed “Anonymous” as the Download user name. (Reference: 363162)
Resolution: Now when creating a distributed repository,
the Summary page correctly displays the user name entered on
the Credentials page as the Download user name.
31. Issue: An Audit Log file entry was not created when the “Change Credentials” button was used to change a distributed
repository’s credentials. (Reference: 363173)
Resolution: An Audit Log file entry is now created when the “Change Credentials” button is used to change a distributed
repository’s credentials.
32. Issue: When a policy was imported, the Audit Log file incorrectly reported the status as “Failed” if a policy with same
name already existed in the Policy Catalog. (Reference: 363786)
Resolution: # The Audit Log file now correctly reports the status of importing a policy.
33. Issue: Clicking the “Back” button on the Change Credentials | Summary page generated an unexpected error.
(Reference: 364833)
Resolution: The “Back” button on the Change Credentials | Summary page now works as expected.
34. Issue: If the “Refresh” button is clicked after deleting or importing a distributed repository, the following message
appears: “There was an error deleting the repository.” Reference: (365056, 365058)
Resolution: Now if you click the “Refresh” button after deleting or importing a distributed repository, control is passed
to the last page of the Delete and Import process.
35. Issue: An Audit Log file entry was not created when a Package was checked in to a distributed repository. (Reference:
368598)
Resolution: An Audit Log file entry is now created when a Package is checked in to a distributed repository.
36. Issue: When 20 or more IP address ranges were added to a Group for IP sorting, the message “Unknown error has
occurred” was displayed. (Reference: 372259)
Resolution: The field length limit was removed for adding IP address ranges to a Group for IP sorting.
37. Issue: The Agent Key Update Package sometimes failed to deploy to a system during an Update Task, causing agent-
server communications to fail. (Reference: 366793)
Resolution: The Agent Key Update Package now successfully deploys to systems during an Update Task.
38. Issue: After upgrading from ePolicy Orchestrator 3.6.1 to 4.0.0, agents sometimes failed to access the master and
distributed repositories before a change was made to the their configuration. (Reference: 367270)
Resolution: Following the Patch installation, the master and distributed repository configurations are rebuilt and sent to
all agents.
39. Issue: DAT versions could be reported in different formats in Product Properties and Product Update Events, causing
compliance queries to fail. (Reference: 369436)
Resolution: DAT versions in Product Properties and Product Update Events are now reported in the same format.
40. Issue: Updates to point product extensions are available. (Reference: 384955)
Resolution: The following point product extensions are upgraded to the following versions during the Patch installation:
{
McAfee Agent version 4.0.0.207
{
VirusScan Enterprise 8.0i version 8.0.0.182
{
VirusScan Enterprise 8.5 version 8.5.0.172
{
System Compliance Profiler version 2.0.1.189
41. Issue: An update to the ePO_Help extension is available. (Reference: 391464)
Resolution: The ePO_Help extension version 1.0.1 is included with this patch.
42. Issue: When a migration was performed and the System Tree was viewed in ePolicy Orchestrator 4.0, a domain group
was unnecessarily added. (Reference: 364337)
Resolution: his behavior is considered expected and is further documented in KB article 614430.
43. Issue: The ComputerMgmt.PushAgent command no longer works in the Shell Client. (Reference: 363575)
Resolution: # The ComputerMgmt.PushAgent command now works in the Shell Client.
44. Issue: Policy Settings Names were created by concatenating the Policy Name with additional internal information,
resulting in Policy Setting Names longer than 255 characters in length. Certain stored procedures truncated the Policy
Settings Name at 255 characters, resulting in non-unique names. (Reference: 345541)
Resolution: # The Policy Settings Name length has been increased to 512 characters.
45. Issue: When attempting to create a Duplicate Policy Name from the “Edit Assignment” page, the message “Unhandled
OrionCore.handleResponse doSuccess Exception” was displayed.
Resolution: Creating a Duplicate Policy Name from the “Edit Assignment” page no longer results in an error.
46. Issue: The Server Task Log file incorrectly reported “Migration Failed(null)” when no Date Transformation Services
packages were selected for Event Migration. (Reference: 362050)
Resolution: # The Server Task Log file now reports “Event Migration (nothing done)” when no Date Transformation
Services packages were selected for Event Migration.
47. Issue: When creating an Export File Name for a long Policy Name, the maximum allowable Windows File Name Size was
exceeded, resulting in an error message, “An unexpected error occurred.” (Reference: 362066)
Resolution: When creating Export File Names, the Policy Name is truncated to 128 characters.
48. Issue: For users with limited access to the System Tree, the Purge Action deleted all records from the Events Table.
(Reference: 363757)
Resolution: The Purge Action is now bound to user’s assigned permissions.
49. Issue: On the Synchronization Settings page for NT Domain or Active Directory, the Last synchronization message
“(never synchronized)” disappeared after the McAfee Agent Deployment page was configured. (Reference: 364376)
Resolution: The NT Domain or Active Directory Last synchronization message “(never synchronized)” is now displayed
until synchronized.
50. Issue: An Audit Log file entry was not created when systems were added through the “Compare and Update”
synchronization process. (Reference: 364561)
Resolution: An Audit Log file entry is now created when systems are added through the “Compare and Update”
synchronization process.
51. Issue: Users were allowed to move and copy “Agent Install” packages. (Reference: 364973)
Resolution: The Change Branch Link in the Packages table, the “Move” and “Copy” buttons on the Change Branch page,
and the Step 2 “Move” checkbox on the Check in Wizard page are now disabled for “Agent Install” packages.
52. Issue: Notification Rules migrated from 3.6.1 would incorrectly report “Defined At Path.” (Reference: 365524)
Resolution: Notification Rules migrated from 3.6.1 now correctly reports “Defined At Path.”
53. Issue: An Audit Log file entry was not created when a system was first “Detected” or “Created” after installation.
(Reference: 367700)
Resolution: An Audit Log file entry is now created when a system is first “Detected” and “Created” after installation.
54. Issue: The “Show Agent Log” action did not display the system’s “Agent Log” file. (Reference: 369042)
Resolution: The “Show Agent Log” action now displays the system’s “Agent Log” file.
55. Issue: The computer property “Is Laptop” was shown as “Unknown” on the Query Filters, Tag Criteria, and System
Details pages. (Reference: 372294)
Resolution: The computer property “Is Laptop” now includes the end node state on the Query Filters, Tag Criteria, and
System Details pages for end nodes using the McAfee Agent 4.0. This property continues to show “Unknown” for end
nodes running Common Management Agents released prior to McAfee Agent 4.0.
56. Issue: The Event Log page displayed “an unknown error occurred” when the database was hosted on a non-English SQL
server. (Reference: 383081)
Resolution: The Event Log page now works as expected when the database is hosted on a non-English SQL server.
57. Issue: Many language translation and localization issues were reported. (Reference: 334120, 337902, 361331, 365155)
Resolution: Key language translation and localization issues were addressed.
58. Issue: SMTP Authentication failure generated an error message when an improper “Return address” was used.
(Reference: 363956)
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24

McAfee ePolicy Orchestrator 4.0 Release note

McAfee
Brand
McAfee
Model
ePolicy Orchestrator 4.0
Category
Networking
Type
Release note
This manual is also suitable for
Download PDF
report

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI

Related papers

Other documents