Users Guide
1. Enumerate the class DCIM_SoftwareIdentity to retrieve the inventory of the system.
The inventories are collected as Installed and Available CIM instances.
NOTE: Users that have administrator or Execute Server Command privileges can retrieve the firmware and
embedded software inventory of the system.
NOTE: Inventory instances are pulled up from the system in both system-off and system-on conditions.
– The software currently installed on the component is listed as the Installed Software Instance.
The status value of this instance is represented as Installed.
– The available software in the persistent storage is listed as the Available Software Instance. The key
property value of the instance, InstanceID represented as DCIM: AVAILABLE :< COMPONENTTYPE> :<
COMPONENTID> :< Version> and the status value of this instance is represented as “Available”. Current
installed software instances are also represented as available software instances.
2. Inventory instances provide input values for the update and rollback operations. To perform the update operation,
pick the InstanceID value from the Installed Instance, DCIM: INSTALLED :< comptype> :< compid> :< version>. For
the rollback operation, pick the InstanceID Value from the Available instance,
DCIM:AVAILABLE:<comptype>:<compid>:<version>. You will not be able to edit InstanceID values.
NOTE: If the version string property value of Available Software Instance is equal to the
Installed Software Instance, then do not use the Instance ID value of that Available Software Instance
for the rollback operation.
Remote Scheduling Types
There are two methods for scheduling:
• Immediate update
• Scheduled update
Immediate Update
To immediately update component firmware, schedule the update and reboot jobs with start time as TIME_NOW.
Scheduling a reboot or update is not required for updates to the Lifecycle Controller components such as Lifecycle
Controller, Diagnostics, and OS Driver Packs. The updates are immediate for these components.
Scheduled Update
Specifying a scheduled start time for one or more jobs using the SetupJobQueue() method involves specifying a date
and time value for the StartTimeInterval parameter. Optionally, a date and time value can be also be specified
for the UntilTime parameter.
Specifying an UntilTime defines a maintenance window to run the updates within a time-bound slot. If the time
window expires and the updates are not completed, any of the update jobs that are currently running are completed.
However, any unprocessed jobs whose scheduled start time has begun fail.
58