INTRODUCTION
Updates released by Lumension are designed for Lumension Endpoint Management and Security Suite (L.E.M.S.S.) but may update other components as they are required. Updates include any previous released items, excluding Service Packs and Patches. Any future release will include these Updates.
Notes:
- It is recommended that updates be tested before entering production environments.
- Updates cannot be uninstalled via Add/Remove Programs.
DETAILS
Update Name: Lumension Endpoint Management and Security Suite 7.0 Service Pack 1 Server Update 3
Impact: Critical
Pre-Requisites
- Lumension Endpoint Management and Security Suite 7.0 SP1 (7.0.0.868), 7.0 SP1 Update 1 (7.0.0.963), or 7.0 SP1 Update 2 (7.0.0.1007)
What's Fixed
| Component |
Type |
Summary |
| Agent Management |
Fix |
Stat eng fails to start with an Agent Management Job |
| EDS |
Fix |
An Agent watchdog exception can occur if LMAgent performs a heartbeat and the EndpointID no longer exists in the database |
| Group Management |
Fix |
Cannot create a custom group under the My Groups group |
| Group Management |
Fix |
Groups that are immediate children of "My Groups" cannot be moved |
| Performance |
Fix |
Response time degradation on Vulnerabilities, Endpoint, and Groups web pages |
| Group Management |
Fix |
Child Group Distinguished Names do not get updated when moving multiple groups in the Group Browser |
| Cache Management |
Fix |
IIS6/IIS7 Cache Control settings for OSPacks folder is disabled -- proxies cannot cache OSPack files |
| EDS |
Fix |
The EDS LanPortal service on LEMSS Server hung on starting |
| Group Management |
Fix |
Groups cannot be moved to be children of "My Groups" level |
| Group Management |
Fix |
Source-grouped agents become manually assigned when a group is moved and the group can no longer be moved afterward |
| Reports |
Fix |
PDF Reports returns a 401 Exception when a Timeout Occurs on the Agent Group List Boxes |
| Replication Services |
Fix |
Agent Manifest files downloaded always pass hash validation |
| Wake on LAN |
Fix |
Filters do not work when attempting to search for machines in the Add WakePoints screen |
| Group Management |
Fix |
Group Vulnerability counts include endpoints that are disabled |
| Replication Services |
Fix |
LEMSS server is unable to cache packages |
| Notifications |
Fix |
New Agent Registrations Email Notification is Not Functional |
| Reports |
Fix |
STAT_Guardian dbo.Report_Deployment_History causes 4.7 trillion logical reads on servers with large node counts |
| Enterprise Reporting |
Fix |
rpt_VulnerabilityCodes includes orphaned Vulnerability Codes, behavior that may cause ETL failure on ERS |
| Mandatory Baseline |
Fix |
LEMSS 7.0 Mandatory Baseline redeployments halt after cleanup job runs |
| KB 741 |
|
Includes L.E.M.S.S. 7.0 Service Pack 1 Server Update 2 |
FAQ
How do I obtain Update 3?
See linked download attached to this KB.
How will I know if this update is applied successfully?
There are two main ways to find out if this has been applied successfully:
- Add/Remove Programs entry will be present (Lumension EMSS 7.0 SP1 Update 3), which will not be able to be uninstalled.
- The Version will change in the Web UI under Help > About to 7.0.0.1066
Where are the installation logs placed during execution?
The installer will create a log file named Update1Install.log in the TEMP directory of the user who executed Update 3.
ADDITIONAL INFORMATION
Revisions: (Recent Changes Are Highlighted In Red)
- V1.0 (Jul 13, 2011): Answer and Binary Published
FILE ATTACHMENTS:
File:
LumensionEMSS_SP1Update3.zip