This article contains important information about known issues of high or medium rating that have been resolved with the Security for Lotus Domino 7.5 Patch 3 release. To read the Release Notes, see
PD26433.
NOTE: As mentioned in the Release Notes, this patch can be used to install Security for Lotus Domino 7.5.3 as a new installation or to upgrade the software from Security for Lotus Domino Patch 2 (Windows).
For a list of all issues resolved in the MSDW 7.5 Patch 2 release, see the Security for Lotus Domino 7.5 Patch 2 Release Notes:
PD24632.
The following issues are resolved in McAfee Security for Lotus Domino 7.5 Patch 3:
| Resolved Issue |
Description |
| 907245 |
The On-Demand Scan (ODS) exclusions configured in ePolicy Orchestrator are not excluded from on-demand scanning. |
| 907095 |
The Engine version registry entry is not updated in an Active/Passive cluster if the Engine and the DAT are pushed from ePolicy Orchestrator on a client that has an Extra.DAT. |
| 936181 |
No results are displayed for Filtered Search in Detected Items in the Japanese language console. |
| 930421 |
Javascript error when you attempt to expand a Domino folder that contains 2656 active NSF files as part of an ODS configuration. |
| 898406, 902179 |
Setting the number of threads for an ODS task in extensions is not persistent. |
| 897121 |
Scanning fails to work after a DAT autoupdate. |
| 903798 |
The Engine update process does not retain the Extra.DAT information when an update task is scheduled from ePolicy Orchestrator. |
| 925834 |
Custom alerts are not saved in the original format in ePolicy Orchestrator extensions. |
| 836475 |
The Purge old definition functionality for DAT retention is set to retain 3 DATs. |
