Users Guide

Verifying the Digital Signature On Systems Running Windows
To verify the Update Package’s digital signature:
1. Start Windows Explorer and locate the Update Package whose digital signature you want to verify.
2. Right-click the filename.
3. Click Properties in the pop-up menu.
4. In the Properties window, click the Digital Signatures tab. If this tab is not displayed, the Update Package is not signed.
5. Select the signature from the signature list, and click Details.
The Digital Signature Details window appears.
NOTE: The signature is not verified until you click Details.
6. Read the digital signature information to verify that the digital signature is OK.
7. Click OK to close the window.
Compatibility checking
DUPs are designed to confirm that all prerequisites are satisfied before applying the update to the system. Each DUP checks to
ensure the following:
• The logged-on user has root privileges.
• DUP to be applied in the command is compatible with the target system and the operating system running on a system.
• The device associated with the DUP is present on the system.
• The minimum required versions of related system software are running on the system.
DUPs are designed with built-in error handling capabilities to ensure that the preceding requirements are validated. If the conditions
are not met, no update occurs. DUPs also check for dependencies between BIOS and certain ESM packages. The application design
allows you to create groups of DUPs and apply them to a wide range of systems. Additionally, if you only want to verify that a given
package can be applied to the system, you can invoke the package by using the following CLI command:
./Packagename.bin ‑c for Linux
packagename.exe /c /s for Windows
This command executes the dependency rules within the DUP, issues any warnings, exits without applying the update to the
system, and writes the results to the console. You can also use the DUP to set an exit code to perform decisions within the scripts.
Information while applying the Updates on a Running System
This section describes all the effects of applying the updates on a running system.
System Reboot Required
Certain packages, such as those that update the system BIOS, require a reboot for the new software to take effect. After you apply
an update that requires a reboot, you must restart the system to complete the update.
You have the option of choosing to defer the reboot until another time as long as you do not turn off the system. This feature is
primarily intended to allow you to apply any number of updates together and perform the system reboot after the last update has
been applied. If this process is interrupted, for example, through a power interruption, you must repeat the updates. Therefore, it is
recommended that you schedule updates for a time when the reboot can take place immediately after you apply the last update.
12