Dell™ Update Packages for Microsoft® Windows® Operating Systems User’s Guide w w w. d e l l . c o m | s u p p o r t . d e l l .
Notes and Notices NOTE: A NOTE indicates important information that helps you make better use of your computer. NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. ____________________ Information in this document is subject to change without notice. © 2003–2008 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Getting Started With Dell Update Packages . . . . . . . . . . . . . . . . . . Overview . . . . . . . 7 . . . . . . . . . . . . . . . . . . . . . . . . . 7 Server Update Utility and DUPs . Update Options . . . . . . . . . . . . . . 9 . . . . . . . . . . . . . . . . . . . 9 Supported Operating Systems . Before You Begin . . . . . . . . . . . . . 10 . . . . . . . . . . . . . . . . . . . . 11 How to Obtain DUPs from the Dell Support Website . . . . . . . . .
2 Using Dell Update Packages . Before You Begin . . . . . . . . . 19 . . . . . . . . . . . . . . . . . . . . 19 . . . . . . . . . 20 . . . . . . . . . . . . . . . . . . 20 . . . . . . . . . . . . . . . . . . . . . 21 Develop Your System Update Plan Acquiring DUPs . Executing DUPs . . . . . . . . . . . 21 . . . . . . . . . . . . . . . . . 22 Verifying the Digital Signature Compatibility Concerns Meeting System Prerequisites . . . . . . . . . . . Updating Non-English Operating Systems . .
3 Command Line Interface Reference . . . . . . . . . . . Using the CLI . . . . . . . . . . . . . 31 . . . . . . . . . . . . . . . . . . . . . . 31 CLI Options . . . . . . . . . . . . . . . . . . . . . Exit Codes for CLI Sample Script . . . . . . . . . . . . . . . . . . . . 33 . . . . . . . . . . . . . . . . . . . . . . 35 Update.bat script 4 . . . . . . . . . . . . . . . . . . 35 . . . . . . . . . . . . . . . . . . . 37 . . . . . . . . . . . . . . . . . . . . . . . .
B Trusted Platform Module (TPM) and BitLocker Support . . . . . . . . . . . . . . 57 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Index 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting Started With Dell Update Packages Overview Dell™ Update Packages (DUPs) allow administrators to update a wide range of system components simultaneously and apply scripts to similar sets of Dell systems to bring system software components up to the same version levels.
Likewise, updating only the miniport driver of a storage controller may also create problems. The Update Packages will now support installation of a single driver for a device as well as multiple drivers, in a single package. Each DUP contains the execution logic to verify that the update will work on your system.
Server Update Utility and DUPs Dell OpenManage Server Update Utility (SUU) is a DVD–based application that is used to identify and apply the latest updates to your system. It is both a Graphical User Interface (GUI) and a Command Line Interface (CLI) based application.
• report on discrepancies and recommend updates, including any prerequisites that may impact the update sequence • update and (if needed) reboot the system NOTE: See the Server Update Utility User's Guide available on the Dell Support website at support.dell.com or on the Dell Systems Management Tools and Documentation DVD for information on how SUU identifies and applies updates to your entire system. Figure 1-1 illustrates when you should use SUU and DUPs while performing updates: Figure 1-1.
• Microsoft Windows Server 2003 R2 Standard and Enterprise (x64) Gold Editions with SP2 • Microsoft Windows Storage Server 2003 R2 Express, Workgroup, Standard, and Enterprise x64 Editions • Microsoft Windows Server 2008 Web, Standard, and Enterprise (32- bit x86) Editions • Microsoft Windows Server 2008 Standard, Enterprise, and Datacenter (x64) Gold Editions • Microsoft Windows Server 2008 Core Standard and Enterprise (32-bit x86) Editions • Microsoft Windows Server 2008 Core Standard, Enterpri
How to Obtain DUPs from the Dell Support Website 1 Log on to support.dell.com. 2 Select Drivers and Downloads. 3 Enter your service tag or choose your product model. 4 Select your product family and product line. 5 Select your operating system, language, category, and the update importance. A list of applicable updates are displayed. 6 Click Download Now. 7 You can also download a different file format from the column labeled File Title. Select a file format for your DUP and single-click its filename.
3 Create a directory structure for performing the updates (for example, create a directory for each system type). 4 Determine a methodology for performing the updates. • Single update method: Run DUPs from the GUI in the interactive mode to perform the update. • Script method: Use this method if you have a requirement for running one or more updates from a script on a single system. See the sample scripts in "Command Line Interface Reference.
Important Tips to Remember for Using DUPs • Prepare repair disks before you perform any updates. • Download the currently installed version of drivers, BIOS, and firmware so that you have a backup plan in case any issues arise. • When you are upgrading any RAID controller software drivers, the enhanced Storage Management Service may need to be upgraded. Check the Dell OpenManage Server Administrator Compatibility Guide before proceeding. See "Other Documents You Might Need" for more information.
Non–Interactive Mode When a fresh install is applicable, executing DUPs with the /s switch installs the driver. For example, packagename.exe /s and packagename.exe /s /r does a fresh install of driver DUPs. See "CLI Options" for more information on the command syntax. NOTE: Not all driver DUPs support fresh install. See the Dell Update Packages for Microsoft Windows operating systems readme file for the list of drivers that do not support fresh install.
Other Documents You Might Need • The Dell OpenManage Server Administrator Compatibility Guide on the Dell Support website at support.dell.com, or on the Dell Systems Management Tools and Documentation DVD that came with your system. This document summarizes all Dell systems management releases that precede the current release date. NOTE: Dell Update Packages do not require Dell OpenManage Server Administrator to be installed on your system.
• The Dell OpenManage IT Assistant User’s Guide on the Dell Support website at support.dell.com or on the Dell Systems Management Tools and Documentation DVD. Dell OpenManage IT Assistant allows you to load DUPs and System Update Sets into a central repository, then compare the packages to the versions of the software currently running on your enterprise systems. You can then decide whether to update systems that are not in compliance, either immediately or according to a schedule you define.
Getting Started With Dell Update Packages
Using Dell Update Packages Before You Begin This section is to help you get the most out of Dell™ Update Packages (DUPs). Updating the system software on your Dell systems should be a key element of your company's overall change management policies and procedures. Maintaining the system software on your Dell systems helps ensure troublefree operation. Before you apply any update to your system, you may want to carefully plan your update strategy, based on the conditions that are necessitating the update.
Develop Your System Update Plan You may want or need to update your system for many reasons, as mentioned in the preceding section. This update requirement may be classified as either planned or unplanned. Planned updates occur as a part of your regular cycle of maintaining your systems with up-to-date BIOS, firmware, and drivers. Many IT organizations establish a regular schedule for performing the updates, which are integrated with the planned maintenance functions.
service tag. Each e-mail notification includes a short summary of the new file available for your system and a Web link to locate that update file on support.dell.com. After you locate your Update Package, read the summary information to determine whether or not you should download the update and apply it to your system. You can run the Update Package on the target system and read the summary information displayed in the Update Package's interactive window.
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.
This command executes the dependency rules within the DUP, issues any warnings, exits without applying the update to your system, and writes the results to a log file (located in the C:\dell\updatepackage\log default directory). You can also use the DUP to set an exit code to perform decisions within your scripts. Updating Non-English Operating Systems You can use DUPs on non-English operating systems; however, DUPs are not provided in other languages at this time.
Specifying the Order of Multiple Updates When applying multiple updates at the same time, be sure to use the order indicated in the "Installation Order of DUPs" section. As previously noted in the "System Reboot Required" section, you may defer rebooting the system until after running the last of multiple Update Packages. You may also want to use the /l option to specify that each of the Update Packages writes to the same log file.
Remote Terminal Sessions In today's highly distributed environment, it is quite 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 your terminal session is disconnected during a NIC driver update, you will need to re-connect and verify that the update has completed successfully.
Typical Usage Scenarios Scenario One — Firmware Update During a Hardware Upgrade As the systems administrator, you are responsible for your company's Dell system, which runs the electronic mail services for 42 employees. You have scheduled a weekend hardware upgrade for the mail server to add additional SAS drives. You plan to use the enhanced Storage Management Service, RAID systems management software to stripe the new disk drives.
10 Verify that all users have disconnected, and then execute the firmware Update Package by double-clicking the filename from within Windows Explorer. 11 Read the information displayed in the Update Package window and confirm that this is the correct firmware for your PERC controller. 12 Click Install to load the PERC 6/E firmware. 13 Reboot the system to confirm that the new firmware has been loaded and that the system is fully operational.
5 Locate the BIOS, ESM firmware, and PERC 6/E Update Packages for the Dell system and download them. Additionally, download the Server Administrator application. NOTE: To install the current version of drivers for your operating system, download the current version of the Dell Systems Management Tools and Documentation DVD from the Dell Support website at support.dell.com. Drivers are located in the SERVICE directory in the DVD. 6 Copy the files that you downloaded to the system’s C:\temp directory.
Scenario Three — BIOS Update for 200 Systems You are the systems administrator for a large business with over 500 stores. Every store location has a Dell system that is used to manage the company’s inventory and billing systems. About 200 of these stores are running on Dell systems. You have entered all your system model types into Dell's File Watch service on support.dell.com. File Watch notifies you when Dell posts any new software updates on support.dell.com for the system types that you registered.
7 On Sunday morning, you log in to your system and check the execution results report within the software distribution tool and determine that the BIOS DUP was successfully applied to 180 of your 200 systems. 8 The attempted BIOS update on the remaining 20 systems returned the message that the update was not required. 9 Log on to any one of the 20 systems and check the BIOS DUP log file.
Command Line Interface Reference Using the CLI This section provides information for using the command line interface (CLI) for Dell™ Update Packages (DUPs). CLI Options You can display information about CLI options by typing the DUP 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: PE2850-BIOS-WIN-A02.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 (continued) CLI Option CLI Task Description Command Syntax /e= Extracts all files contained in the DUP to the path you specify. If the directory specified in the path does not exist, it is created. packagename.exe /s /e=c:\update Extract option packagename.exe /s /e="c:\update If the path contains spaces, use quotation files" marks around the value. The /s option is required with this option. Options /f, /c, and /r are not valid with this option.
Table 3-1. CLI Options: Usage (continued) CLI Option CLI Task Description /s Executes the update silently without packagename.exe /s user intervention. When /s is not /l=c:\pkg.log specified, the DUP is launched in GUI (interactive) mode. Silent option Command Syntax The /s option is required when using the /e, /f, /c, /l, and /u options. NOTE: Using the /s option causes all output to be written to log files.
Table 3-2. Exit Codes (continued) Value Message Name Description 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. To avoid receiving this error, provide the /f option. 4 DEP_HARD_ERROR The required prerequisite software was not found on your system.
Sample Script The following example shows how you can use scripts to run DUPs. The Update.bat script is an example of updating the BIOS and ESM firmware on a Dell system. 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 DUPs have already been downloaded to a folder on the target system.
if %ExitCode% >>%LOG% if %ExitCode% >>%LOG% if %ExitCode% >>%LOG% if %ExitCode% >>%LOG% 36 EQU 3 echo Result: DEP_SOFT_ERROR EQU 4 echo Result: DEP_HARD_ERROR EQU 5 echo Result: QUAL_HARD_ERROR EQU 6 echo Result: REBOOTING_SYSTEM Command Line Interface Reference
Troubleshooting Messages Table 4-1 provides descriptions and solutions to messages that you may receive when running Dell™ Update Packages (DUPs). NOTE: The Readme.txt file, which is available on the Dell Support website at support.dell.com, provides the latest information regarding known issues. Table 4-1. Update Packages: Message Information Message Description/Solution This Update Package is not compatible with your system.
Table 4-1. Update Packages: Message Information (continued) Message Description/Solution Your system does not have the minimum operating system version or service pack required for this Update Package. The DUP you selected cannot be installed because the minimum operating system version or service pack requirements were not met. Install the appropriate version, and try the update again. Or, use an alternate update method on support.dell.com.
Table 4-1. Update Packages: Message Information (continued) Message Description/Solution The version of this This message confirms the version of the Update Package is newer currently installed software before the update is performed. than the currently installed version. Software application name: Package version: Installed version: The version of this Update Package is older than the currently installed version.
Table 4-1. Update Packages: Message Information (continued) Message Description/Solution You must reboot the system for the update to take effect. If you shut down or power off the system after performing an update, you will lose the update. An Update Package is already running. Wait until it is complete before proceeding with another update. You can run only one DUP at a time. This Update Package is not installed.
Package Log File Example ====> Dell Update Package application started <==== Command:C:\WINNT\TEMP\DUPBIOS\PE2650_BIOS_WIN_A21.EXE /f /s /l=C:\WINNT\TEMP\5000021.dup Date:2006-11-09 10:22:56 ===================================================== All files extracted OK Release ID: R136685 Update Package version: 5.3.0 (BLD_31) User: SYSTEM Collecting inventory... Running validation... The version of this Update Package is newer than the currently installed version.
Support Log Use the Support log to view and analyze execution details that have occurred during the package installation. Contents of this log are useful when communicating with Dell™ support representatives during issue diagnosis. This log includes package XML details for the specific device updated. The Support log file resides in the following default location: C:\dell\updatepackage\log\support\packagename.log where C: is your system drive and packagename is the name of the DUP that you installed.
Package source: C:\Temp\PE2850_BIOS_WIN_A06\SPSETUP.exe << PACKAGE LOG >>Collecting inventory... Inventory command: biosie.exe -i inv.
Package version: A06 Installed version: A04 << PACKAGE LOG >>Executing update... Execution command: biosie.exe -u update.xml Update Execution: returnCode=0, exitCode=0 The update was successful. Reboot the system to complete the BIOS update.
PAGE 46
-
PAGE 48Windows Operating System Event Log Messages are logged to the Windows System Event Log (SEL) if the update is attempted. You can use the Windows Event Viewer to view and manage Windows events.
Frequently Asked Questions Question: Must I reboot my system after applying every Dell™ Update Package (DUP)? Answer: DUPs that are running in the interactive mode determine if it is necessary to reboot your system. If so, you are prompted to reboot. In the silent unattended mode, the exit code is set to 2, which indicates that a system restart is required. Question: Which operating systems are supported by DUPs? Answer: See "Overview" for information about supported operating systems.
Question: Where can I find the error messages generated by a DUP that is running in unattended mode? Answer: The execution messages are stored in the Package log file and in the Windows System Event Log (SEL), which are described in "DUP Message Logs" section of this guide. The Package log file resides in the following default directory: C:\dell\updatepackage\log\packagename.txt The Windows SEL is available through the Windows Event Viewer.
Question: I'd like to apply several updates to my system at once. Can I do this with DUPs? Do I need to be concerned about the order in which I apply the updates? Answer: Yes, you can apply multiple updates to your system at the same time. See the "Scenario Two — Retasking a System" section for more information. The installation order is very important. See Table 1-1 for information about the update order. Question: If I rename Windows DUPs, will they still function correctly? Answer: Yes.
Question: Why does my system only execute one of the CLI options that I entered in a command string? Answer: Only certain CLI options can be used simultaneously. When invalid combinations of CLI options are entered in a single command string, only the option with the highest priority is executed. See Table 3-1 for details on which commands can be used together.
Microsoft Windows Server 2008 User Account Control In previous versions of Windows®, user accounts were often members of the local Administrators group and had access to administrator privileges. Members of the local Administrators group could install, update, and run software since an Administrator account has system-wide access. When a user was added to the local Administrators group, that user was automatically granted every Windows privilege.
UAC prompts users in the Domain Administrators group (except the Administrator account) to click Continue, if they need to elevate privileges, or to click Cancel when performing functions that may entail a security risk. With UAC, users have to upgrade to an Administrator account before running DUPs. NOTE: Since the user experience is configurable with the Security Policy Manager snap-in (secpol.msc) and with Group Policy, there are multiple UAC user experiences.
• Disabling UAC for all users on remote machines (not a recommended option). • Not upgrading to Administrator account on remote machines. NOTE: Only two accounts (the Local Administrator Account and the Local System Account) are not protected by UAC. All other users including accounts with local administrator rights or domain administrator rights have UAC enabled by default. Even though UAC can be disabled by updating the local or domain security policy, it is not recommended.
Microsoft Windows Server 2008 User Account Control
Trusted Platform Module (TPM) and BitLocker Support A TPM is a secure microcontroller with cryptographic capabilities designed to provide basic security-related functions involving encryption keys. It is installed on the motherboard of your system, and communicates with the rest of the system using a hardware bus. You can establish ownership of your system and its TPM through BIOS setup commands. TPM stores the platform configuration as a set of values in a set of Platform Configuration Registers (PCRs).
BitLocker is designed for systems that have a compatible TPM microchip and BIOS. A compatible TPM is defined as a version 1.2 TPM. A compatible BIOS supports the TPM and the Static Root of Trust Measurement. BitLocker seals the master encryption key in the TPM and only allows the key to be released when code measurements have not changed from a previous secure boot. It forces you to provide a recovery key to continue boot if any measurements have changed.
Glossary The following list defines or identifies technical terms, abbreviations, and acronyms used in this guide. ASCII Acronym for American Standard Code for Information Interchange. A text file containing only characters from the ASCII character set (usually created with a text editor, such as Notepad in Microsoft® Windows®), is called an ASCII file. BIOS Acronym for basic input/output system. Your system's BIOS contains programs stored on a flash memory chip.
device driver A program that allows the operating system or some other program to interface correctly with a peripheral device, such as a printer. Some device drivers—such as network drivers—must be loaded from the config.sys file (with a device= statement) or as memory-resident programs (usually from the autoexec.bat file). Others—such as video drivers—must load when you start the program for which they were designed.
Interactive mode The method by which you can install DUPs interactively through a GUI. IPMI Acronym for Intelligent Platform Management Interface. The Intelligent Platform Management Interface (IPMI) specification defines a set of common interfaces to computer hardware and firmware, which system administrators can utilize to monitor the system health and manage the system. ITA Acronym for Dell OpenManage IT Assistant.
SEL Acronym for Microsoft Windows System Event Log. SUU Acronym for Dell OpenManage Server Update Utility. SUU is one of the applications used for identifying and applying updates to your system. You can use SUU to update your Dell system or to view the updates available for any system supported by SUU. SUU compares the versions of components currently installed on your system with update components packaged on the Dell Server Updates DVD.
Index B D BIOS update for 200 systems usage scenario, 28 default log file location, 12, 22 BitLocker, 59 C delivering Update Packages to your systems, 24 Dell File Watch update notification service, 20, 28 Catalog.
M message logs for Update Packages, 40 multiple drivers, 8 Server Administrator documentation, 12, 15 specifying order of multiple updates, 23 strategy for running Update Packages, 13 O obtaining Update Packages, 11 operating systems supported, 10 Support log, 42 log file example, 42 system reboot required after installing some Update Packages, 23 P Package log, 40 default location, 40 log file example, 41 Platform Configuration Registers, 59 T terminal mode commands, 59 troubleshooting Update Packages
Update Packages acquiring, 20 before you begin, 19 CLI mode, 31 CLI options, 22 CLI reference information, 31 delivering to your systems, 24 executing, 21 how to obtain, 11 information provided about updates, 12 message logs, 40 overview, 7 remote terminal sessions, 24 resolving compatibility concerns, 22 sample script, 35 silent/unattended mode, 25 some require system reboot, 23 stand-alone systems, 25 supported devices, 51 supported installation order of Update Packages, 13 supported order of installation
Index
