Owner's Manual
Table Of Contents
- User’s Guide
- Getting Started With Dell Update Packages
- Using Dell Update Packages
- Performing BIOS and Firmware Updates Using Dell Linux Online Repository
- Update and Rollback in Unified Server Configurator - Lifecycle Controller Enabled
- Command Line Interface Reference
- Linux Troubleshooting
- Known Issues
- Diagnostic Tasks Will Not Run While a DUP Reboot is Pending
- Abnormal Termination of a DUP
- Error While Loading Shared Libraries
- Insufficient Free Physical Memory to Load the BIOS Image
- Kernel Panic While Running Storage Controller Firmware Update Packages
- Loss of Functionality While Renaming Linux DUPs
- Yum and Up2date Repository Management Software Caches Incorrect Repository Metadata
- Use Dell Linux Repository with yum and Red Hat Enterprise Linux Version 4
- DUPs Fail on 64-bit Red Hat Enterprise Linux Operating System
- DUP Update of Firmware Might Fail While Running in the UEFI Mode
- Messages
- DUP Message Logs
- Known Issues
- Windows Troubleshooting and FAQs
- Index

Using Dell Update Packages 19
3
Click
Properties
in the pop-up menu.
4
In the
Properties
window, click the
Digital Signatures
tab.
NOTE: If this tab is not displayed, the Update Package is not signed.
5
Select the signature from the signature list, and click
Details
.
NOTE: The signature is not verified until you click Details.
The
Digital Signature Details
window appears.
6
Read the digital signature information to verify that the digital signature is
OK.
7
Click
OK
to close the window.
Compatibility Concerns
DUPs are designed to confirm that all prerequisites are satisfied before applying
the update to your system. Each DUP checks to ensure the following:
• The logged-on user has root privileges.
• The DUP to be applied in the command is compatible with your target system.
• The DUP to be applied in the command is compatible with the operating
system running on your system.
• The device associated with the DUP is present on your system.
• The minimum required versions of related system software are running on
your 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 your system, you can invoke the
package by using the following CLI command:
./Packagename.bin -c for Linux
packagename.exe /c /s for Windows