This section provides information for using the command line interface (CLI) for Update Packages.
CLI Options
You can display information about CLI options by typing the Update Package name and either /? or /h at a command line prompt. For example, type the following command to get a help screen about the CLI options:
PE2650-BIOS-WIN-A10.exe /?
Table 3-1 provides a list of the CLI options, a description of each option, and the command syntax.
Table 3-1. CLI Options: Usage
CLI Option
CLI Task Description
Command Syntax
/? or /h
Help option
Displays command line options and help information.
packagename.exe /?
packagename.exe /h
/c
Check option
Determines if the update can be applied to the target system.
The /s option is required with this option.
Options /f, /e, and /r are not valid with this option.
When you click Install in the graphical user interface (GUI) mode, the same checking process is performed.
packagename.exe /s /c /l=c:\pkg.log
/e=<path>
Extract option
Extracts all files contained in the Update Package to the path you specify. If the directory specified in the path does not exist, it is created.
If the path contains spaces, use quotation marks around the <path> value.
The /s option is required with this option.
Options /f, /c, and /r are not valid with this option.
packagename.exe /s /e=c:\update
packagename.exe /s /e="c:\update files"
/f
Force option
Allows reinstallation or downgrade of the software to a previous (older) version.
The /s option is required with this option.
Options /e and /c are not valid with this option.
packagename.exe /s /f /l=c:\pkg.log
/l=<filename>
Log option
Appends logged messages to a specified ASCII file; creates a new file if one does not exist. If the file name contains spaces, use quotation marks around the <filename> value.
The /s option is required with this option.
packagename.exe /s /l=c:\pkg.log
packagename.exe /s /l="c:\Update Log\pkg.log"
/r
Reboot option
Reboots the system, if required, after performing the update. The reboot does not occur:
If the Update Package fails or is not applicable to the target system
If the Update Package does not require a reboot
The /s option is required with this option.
Options /e and /c are not valid with this option.
packagename.exe /s /r /l=c:\pkg.log
/s
Silent option
Executes the update silently without user intervention. When /s is not specified, the Update Package is launched in GUI (interactive) mode.
The /s option is required when using the /e, /f, /c, /l, and /u options.
packagename.exe /s /l=c:\pkg.log
/u=<filename>
Unicode Log option
Appends logged messages to a specified unicode file; creates a new file if one does not exist. If the file name contains spaces, use quotation marks around the <filename> value.
The /s option is required with this option.
packagename.exe /s /u=c:\pkg.log
packagename.exe /s /u="c:\Update Log\pkg.log"
Exit Codes for CLI
After running Update Packages, the exit codes described in Table 3-2 are set.
The exit codes help you determine and analyze the execution results after you run Update Packages.
Table 3-2. Exit Codes
Value
Message Name
Description
0
SUCCESS
The update was successful.
1
UNSUCCESSFUL
An error occurred during the update process; the update was unsuccessful.
2
REBOOT_REQUIRED
You must restart the system to apply the updates.
3
DEP_SOFT_ERROR
Some possible explanations are:
You attempted to update to the same version of the software.
You tried to downgrade to a previous version of the software.
4
DEP_HARD_ERROR
The required prerequisite software was not found on your system.
5
QUAL_HARD_ERROR
The Update Package is not applicable. Some possible explanations are:
The operating system is not supported by the Update Package.
The system is not supported by the Update Package.
The Update Package is not compatible with the devices found in your system.
6
REBOOTING_SYSTEM
The system is being rebooted.
Sample Script
The following example shows how you can use scripts to run Update Packages.
The Update.bat script is an example of updating the BIOS and ESM firmware on a PowerEdge 2600. The execution results are placed in a log file named PE2600.log. Text that represents the exit codes from the execution of each package is also placed in the file. You may want to handle some of the exit codes differently in the scripts you write.
This script assumes that Update Packages have been already downloaded to a folder on the target system.
