Lenovo System Update is a small Win32 application that can be preinstalled at the factory as part of a custom image or downloaded by IT. When launched, Lenovo System Update checks your local repository or Lenovo’s support site for updates. This location is configurable by IT. How does System Update compare to other Lenovo Deployment Solutions? System Update enables IT administrators to distribute updates for software, drivers, and BIOS in a managed environment from a local server.

To update the server firmware use the information in this topic.

The Server Firmware option displays firmware levels and allows you to update the DSA, IMM2, and UEFI firmware. The current versions of the IMM2, UEFI, and DSA firmware are displayed. This includes the Active, Primary, and Backup versions.

The following illustration shows the Server Firmware window.

• Active: The firmware is active.
• Inactive: The firmware is not active.
• Pending: The firmware is waiting to become active.

To update the server firmware complete the following steps:

1. Click Server Firmware from the Server Management menu list.

2. Click Update Firmware. The Update Server Firmware window opens (as shown in the following illustration).

3. Read the warning notice before continuing with the next step.
4. Perform one of the following steps:
   • Click Cancel and return to the previous Server Firmware window.
   • Click Select File... to select the firmware file that you want to use to flash the server firmware.
     Note: All other options are grayed out when the Update Server Firmware window initially opens.

     When you click Select File..., a File Upload window opens (as shown in the following illustration). This window allows you to browse to the desired file.

5. Navigate to the file you want to select and click Open. You are returned to the Update Server Firmware window with the selected file displayed (as shown in the following illustration).

6. Click Next > to begin the upload and verify process on the selected file. A progress meter will be displayed as the file is being uploaded and verified (as shown in the following illustration).

   You can view this status window to verify that the file you selected to update is the correct file. The status window will have information regarding the type of firmware file that is to be updated such as DSA, IMM, or UEFI.

   After the firmware file is uploaded and verified successfully, a Successful upload window opens (as shown in the following illustration).

7. Click Next > if the information is correct. Click < Back if you want to redo any of the selections.

   If you click Next >, a set of additional options are displayed (as shown in the following illustration).

8. The drop-down menu beside the Action 1 field gives you the choice to Update the primary bank (default action) or Update the backup bank (as shown in the following illustration).

   After you select an action, you are returned to the previous screen with the requested additional action displayed.

   After the selected action is loaded, that action and a new Action 2 drop-down menu are displayed (as shown in the following illustration).

   Note: To disable an action and start the additional option process again, click the checkbox beside the related action.
   The previous screen shows that for Action 1, the primary bank is selected to be updated. You can also select to update the backup bank under Action 2 (as shown in the previous screen). Both the primary bank and the backup bank will be updated at the same time when you click Next >.

   A progress meter shows the progress of the update for the primary and backup banks, (as shown in the following illustration).

   When the firmware update is completed successfully, the following window opens. Select the related operation according to the displayed content to complete the update process.

   If the primary firmware update did not complete, the following window opens when the Server Firmware screen is displayed.

Windows supports a platform for installing system and device firmware updates via driver packages that are processed by using the UEFI UpdateCapsule function. This platform provides a consistent, reliable firmware update experience, and it improves the discoverability of important system firmware updates for end-users.

The UEFI firmware update platform guidance is intended for SoC vendors and OEMs who are building hardware platforms that run Windows. The UEFI firmware update platform is supported by the following operating system versions:

• Windows 8
• Windows 8.1
• Windows 10 for desktop editions (Home, Pro, Enterprise, and Education)
• Windows 10 Mobile

UEFI firmware update support in Windows 10

All systems that run Windows 10 for desktop editions should implement UEFI firmware updates by following the UpdateCapsule-based update process described in this section of the documentation.

Devices that run Windows 10 Mobile can follow the UpdateCapsule-based process used for Windows 10 Desktop. These devices can also follow the binary update process, which performs a binary update to the storage partition which contains the UEFI firmware.

Microsoft strongly recommends that devices running Windows 10 Mobile should update UEFI firmware by using the binary update process. Devices that run Windows 10 Mobile can use the UpdateCapsule-based process only in scenarios where the binary update process cannot be used. For example, if the partition layout of the device prevents the UEFI firmware from being updated by using a binary update package.

For more information about .spkg packages for Windows 10 Mobile, see Creating packages.

Overview of the UEFI firmware update platform

There are two types of firmware that can be serviced via Windows: system firmware and device firmware. System firmware is responsible for providing critical boot and runtime services to the system as a whole, and device firmware is associated with a particular device integrated into a system. Such device firmware typically works together with a device driver, allowing the OS to expose the device to OS-level services and applications.

System firmware updates

System firmware updates for UEFI-based systems will be deployed as device driver packages (INFs). Windows will use information provided by the platform to ensure that the update package only applies to appropriate systems. A firmware update package contains a binary file containing the system firmware image. After the firmware update package is on the end-user's system, Windows will use the UEFI UpdateCapsule function to hand-off the firmware payload to the platform firmware for processing.

Deploying the update as a driver package allows the firmware update process to align with many existing deployment and servicing tools, and ensures simple update package authoring for hardware vendors.

Note

The fact that the firmware update is delivered as a driver package does not mean that the update is written as an actual driver. The driver package will contain an INF file and a binary file containing the system or device firmware image.

Device firmware updates

Lenovo Bios Update Download

For the purposes of updating device firmware, the device firmware can be assigned to one of these two categories:

• UEFI-updatable device firmware.

  This device firmware can be updated using a device driver package leveraging the same mechanism as system firmware. A device firmware update is distributed as a firmware update package. After the firmware update package is on the end-user's system, Windows will use the UEFI UpdateCapsule function to hand-off the device firmware payload to the platform firmware for processing. This process is virtually identical to how Windows hands off system firmware update payload, and is discussed below.

  It is recommended that device firmware be updated using a discrete firmware update driver package, but device firmware may also be updated with system firmware as part of a single firmware update driver package.

  Note UEFI should not be used to update peripheral devices. UEFI requires devices to be present during reboot to apply a firmware update which cannot be guaranteed with (external, removable) peripheral devices.

• Driver-updatable device firmware.

  This device firmware can be updated by the device driver during the normal Windows OS runtime. Updating device firmware using normal Windows OS drivers is not covered by this paper.

System requirements for Windows firmware updates

Lenovo Mobile Software Update Download

In order for a system to be compatible with the Windows firmware updating mechanism, it must meet the following requirements:

• The system must implement UpdateCapsule and QueryCapsuleCapabilities as defined by section 8.5.3 of the UEFI specification 2.8.

  UpdateCapsule is used to pass the firmware update payload between Windows and the platform firmware.

• Platform firmware must support firmware updates initiated by Windows.

  System firmware, and some classes of device firmware, must be updatable using this process. Firmware code recognizes a firmware update payload passed to UpdateCapsule and initiates the update process. The implementation is owned by the partner.

• Must specify a Firmware Resource in the EFI System Resource Table (ESRT)

  The Firmware Resource allows Windows to surface a device instance with a Hardware ID, which will be used to target the system or device firmware update to appropriate systems and devices. It also describes the current firmware version and provides status for previous updates.

  There exists a single entry for system firmware updates. All devices with updateable firmware must have a resource specified in the ESRT, unless a device's firmware is updated as part of a system firmware update.

  For more information, see ESRT table definition.

In this section