Users Guide

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.
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 specifies the output from the DUP to be sent to both the console and to a log file. The ‑a switch ensures that the output is
appended to a file, protecting any previous log file 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 effectively 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.
Network file shares also are an effective method of making DUP accessible in a distributed environment. When a DUP begins execution, it
first copies the contents of the package to a temporary location on the local drive of the system. This process ensures that the update
can be completed even if the connection to the network share is lost for any reason.
Remote Terminal Sessions
In today's highly distributed environment, it is common for IT organizations to use remote access solutions, such as Microsoft Terminal
Services, to gain access to their remote systems. You may use this type of solution to run DUPs.
NOTE:
If the terminal session is disconnected during a NIC driver update, you will need to re-connect and verify that the
update has completed successfully.
Stand-Alone Systems and Firewalls
For systems that are not connected to the Internet or that have firewall which block user downloads, you need to download DUP from
dell.com/support by using a system that has Internet access, such as desktop or portable computer. You can make DUP available to the
system by copying them onto removable media that the system supports.
Confirming the Update
To ensure that the DUPs were applied to the system, review the console output that was generated during execution. For detailed
information about the messages, see Linux Troubleshooting.
If you want to revert to a previous (older) version of the software after updating to a newer version, you must download the appropriate
DUP from dell.com/support/manuals and install it.
For Systems Running Linux:
To install the previous version from a script, use -q (unattended) mode. In addition, you must use the CLI -f option, which forces the
downgrade.
Using Dell Update Packages
13