Users Guide

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 eects 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 eect. 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 o 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.

Saving Console Output for Linux

As the DUPs are executed, messages are printed to the console. To redirect console output, use the following syntax with interactive

commands:

./packagename.bin|tee -a logname.lo

The |tee species the output from the DUP to be sent to both the console and to a log le. The ‑a switch ensures that the output is

appended to a le, protecting any previous log le output from being overwritten.

Delivering DUPs to the Systems

The DUP application does not provide scheduling and delivery of the packages to multiple systems. You must rely on third‑party or native

operating system applications to accomplish script execution and distribution on multiple systems.

Updating Multiple Systems

For large environments that consists of multiple systems, remote software distribution applications provide the best solution. Many of these

tools can eectively leverage the DUP and provide the convenience of installing and updating a variety of software, such as operating

systems and applications, in a heterogeneous environment.

Using Dell Update Packages