Owner's Manual
For more information, see Microsoft KB 321363 and KB 319942.
Issue 35: The Compliance report for a server is displayed only if there are updatable components.
Issue 36: Systems that are rebooted after an update still display a Reboot Required message.
The return code is from the actual update process. You can go to the job and check the status of the task,
including the status of the reboot.
Issue 37: The Check applicable updates by Computers report may display multiple entries for the same
server name even if the report is grouped by computer name
Issue 38: Patch Rollout Job fails with message Schedule occurs in the past. Scheduling a stage and
distribute task does not schedule the Staging and Preparing For Distribution task. It only schedules the
Rollout Job.
If the staging and preparing for distribution task takes a longer time and surpasses the scheduled time for
rollout job, the rollout job times out and the update task does not run on schedule. In such cases, Dell
recommends using the Run now option to apply the patch.
If scheduling is required, then maintain a time delay between Staging and distribute task and a Rollout
job, so that the Rollout Job can start after the staging and distribute task is completed.
Issue 39: A Server Error message is displayed when you launch the Security Permissions page by clicking
Settings> Security> Permissions menu on the Web page that is opened from the Getting Started Web part
on Dell Patch Management solution portal page.
Resolution: The security permissions page can be launched without errors from the main console window
by clicking Settings> Security> Permissions.
Issue 40: For a server that supports updates using Altiris Agent and updates using Lifecycle Controller, if an
update is applied using one of the methods, that update is still seen as applicable under the Hardware
Update Compliance reports.
Resolution: After applying the update to the server using either the Altiris Agent or the Lifecycle Controller,
the user needs to run the following tasks for the Hardware Update Compliance reports to display the
correct info :
1. Compliance Check task on Windows/Linux Servers
2. Dell Management Console Inventory task
3. Compliance task on Lifecycle Controller Enabled Servers
Issue 41: Dell 32 bit Diagnostics do not appear in the hardware compliance reports when updating Lifecycle
Controller enabled servers As this update does not report component type currently, it cannot be updated
using Patch Management Solution.
Issue 42: Under hardware compliance reports, Lifecycle Controller based updates will show up when the
OS Type is selected as Windows or Linux. The Operating System column in the report will either be blank
or is displayed as NA for Lifecycle Controller based updates.
Issue 43: When a bundle update is run on multiple LifeCycle Controllers Enabled Servers using WS-MAN
(Apply updates using LifeCyle Controller), some of the updates may fail with an error message "A WSMAN
connection could not be established". Run the job instance again to perform the update.
Issue 44: When a server and its iDRAC is discovered and inventoried using SNMP + WS-MAN protocol, users
may see SNMP inventory information only. Re-run the discovery and inventory to get WS-MAN inventory.
Without WS-MAN inventory, you cannot apply updates using LifeCycle Controllers.