background image

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) 

Summary of Contents for ePolicy Orchestrator 4.0

Page 1: ...s 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 bel...

Page 2: ...erence 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 App...

Page 3: ...ator 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 ...

Page 4: ...appings 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 assigne...

Page 5: ... 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...

Page 6: ...20764 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 ...

Page 7: ... 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 prope...

Page 8: ...nsion 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...

Page 9: ...ackup 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 I...

Page 10: ...tor 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 group...

Page 11: ...ution 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 Win...

Page 12: ...r 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 defaul...

Page 13: ...strator 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 locat...

Page 14: ...r 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 pub...

Page 15: ...roup 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 40...

Page 16: ...er 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 us...

Page 17: ...d 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 ...

Page 18: ... 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 a...

Page 19: ...rmat 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 ex...

Page 20: ... 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...

Page 21: ...lt server tasks that are not directly related to a plug in are being marked as invalid and cannot be accessed through the user interface Reference 385880 Resolution Server tasks are now checked to see if they are valid 65 Issue Connection objects were declared but never used Reference 370991 Resolution The orphaned connection has been removed 66 Issue The Scheduler ran a task regardless of whether...

Page 22: ...hestrator 4 0 Patch 5 installation instructions Note Cluster installation is not currently supported on Windows 2008 Server ePolicy Orchestrator software provides high availability for server clusters with Microsoft Cluster Server MSCS software Removing the Generic Service resources 1 In Cluster Administrator take the ePolicy Orchestrator service resources offline right click each resource and sel...

Page 23: ... that are licensed or sublicensed to the user under the GNU General Public License GPL or other similar Free Software licenses which among other rights permit the user to copy modify and redistribute certain programs or portions thereof and have access to the source code The GPL requires that for any software covered under the GPL which is distributed to someone in an executable binary format that...

Page 24: ...ighted by Cambridge Broadband Ltd 2001 2003 Software copyrighted by Sparta Inc 2003 2004 Software copyrighted by Cisco Inc and Information Network Center of Beijing University of Posts and Telecommunications 2004 Software copyrighted by Simon Josefsson 2003 Software copyrighted by Thomas Jacob 2003 2004 Software copyrighted by Advanced Software Engineering Limited 2004 Software copyrighted by Todd...

Reviews: