Software Overview for HP 8200 Elite and 6200 Pro Desktop Models

3
NOTE: UEFI tool version level is at publication time. Later revisions will be available in future
timeframes
Table 2. Windows-based tools
Legacy Tool UEFI Tool Description of UEFI tool
HPQFlash.exe HPQFlash.exe
v4.30.13.1
No changes required to support UEFI BIOS. Backward-
compatible.
HPQPswd.exe HPQPswd.exe
v3.0.1.2
No changes required to support UEFI BIOS. Backward-
compatible.
System
Software
Manager
(SSM)
SSM.exe
v2.14 Rev. A
No changes required to support UEFI BIOS. Backward-
compatible.
BiosConfigUtility.
exe
BiosConfigUtil
ity.exe
v2.14.0.8
Using BiosConfigUtility.exe to configure a Desktop
system requires a text file in UCS-2 format (UTF-16
Unicode with fixed-width 16-bit characters) typically
generated by REPSETUP.EXE or similar method, which
specifies the BIOS settings and appropriate selection for
each feature.
UEFI BIOS no longer accepts passwords as a string of
scan codes. Password parameter must be provided as a
string with <utf-16/> prefix.
FWUpdLcl.exe FWUpdLcl.exe Intel Windows-based application to update the ME
firmware.
Use version from respective ME Firmware update kit.
Backward compatibility defined by Intel.
Xerces-c_2_7.dll Xerces-
c_2_7.dll
Library support file required for some versions of the
Windows update application.
Use version from respective ME Firmware update kit.
Backward compatibility defined by Intel.
NOTE: Although some tools are backwards compatible, it is good practice to update to the specified
version or later to avoid possible future complications with older revisions. UEFI tool version level is at
publication time. Later revisions will be available in future timeframes.
Customer Impact
The transition from legacy BIOS to UEFI BIOS will require some changes to
customer toolsets. The following subsections discuss considerations for a strategy to
minimize workflow disruption in an enterprise environment.
DOS-based Tools
DOS-based tools need to be updated. UEFI tools supporting UEFI BIOS are
required for updating, restoring, and/or configuring desktop systems. In addition,
scripts and batch files will need to be updated to reflect account tool name changes
and utilize new command line parameter switches.