HP BL680c HP ProLiant Firmware Maintenance CD User Guide - Page 48

Update Manager GUI appears.

Page 48 highlights

Command line argument /s[ilent] /c[omponent] or /group "group_name" /b[undle] or /allow_update_to_bu ndle /allow_non_bundle_c omponents /use_latest /use_location "file_share" Description This argument causes the installation to run silently with no GUI or console output. All data writes to the log file. Any generated prompts use the default option and continue the installation without user input. If a component requires input before installation (such as configuration information), then the component installation fails, and an error message writes to the log file. Failed dependencies are not reported to the user when using the /s[ilent]argument. To check for failed dependencies, remove the /s[ilent] argument, reissue the command line, and then the HP Smart Update Manager GUI appears. This argument specifies the components to install. Components to install can be specified with or without the /c[omponent] argument. If using the /c[omponent] argument, only one component can be specified with the argument. However, multiple /c arguments and components can be specified on the same line. If the /c[omponent] argument is not used, multiple components can be specified at the same time, but the components must be separated by a blank and listed after all the arguments on the command line. The components are installed in the order provided unless dependencies between components require installation in a different order. If so, the utility changes the installation order based on the component dependencies to ensure the successful installation of as many components as possible. Multiple components and bundles can be specified on the same command line. When mixing components and bundles on the command line, the filter switches control what components and bundles are installed. This argument specifies an already defined group name in the HP Smart Update Manager GUI. This argument specifies the bundles to install. Bundles to install can be specified with or without the /b[undle] argument. If using the /b[undle] argument, only one bundle can be specified with the argument. However, multiple /b arguments and bundles can be specified on the same line. If the /b[undle] argument is not used, multiple bundles can be specified at the same time, but the bundles need to be separated by a blank and listed after all the arguments on the command line. Multiple components and bundles can be specified on the same command line. When mixing components and bundles on the command line, the filter switches control what components and bundles are installed. This argument is a filter switch and enables the user to install newer versions of components defined in a PSP or firmware bundle. This argument enables these components to replace the older versions of the same component that might have shipped with the bundles. This argument is a filter switch and enables the user to install components that are not included in the bundle but reside in the directory with the components in the bundle. This argument is a filter switch for use with bundles. The argument enables you to use the latest version of the bundle when multiple versions of bundles are listed on the command line. If there are no bundles specified on the command line, and multiple bundles are in the directory, the /use_latest argument allows HP Smart Update Manager to use the bundle with the latest version for installation. This argument specifies a directory or file share that contains the PSP and components for use with HP Smart Update Manager. The "file_share" format Scripted deployment 48

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87

Scripted deployment 48
Command line
argument
Description
/s[ilent]
This argument causes the installation to run silently with no GUI or console
output. All data writes to the log file. Any generated prompts use the default
option and continue the installation without user input. If a component
requires input before installation (such as configuration information), then the
component installation fails, and an error message writes to the log file.
Failed dependencies are not reported to the user when using the
/s[ilent]
argument. To check for failed dependencies, remove the
/s[ilent]
argument, reissue the command line, and then the HP Smart
Update Manager GUI appears.
/c[omponent]
<component to install>
or
<component1_to_install>
<component2_to_install>
This argument specifies the components to install. Components to install can
be specified with or without the
/c[omponent]
argument. If using the
/c[omponent]
argument, only one component can be specified with the
argument. However, multiple
/c
arguments and components can be specified
on the same line. If the
/c[omponent]
argument is not used, multiple
components can be specified at the same time, but the components must be
separated by a blank and listed after all the arguments on the command line.
The components are installed in the order provided unless dependencies
between components require installation in a different order. If so, the utility
changes the installation order based on the component dependencies to
ensure the successful installation of as many components as possible. Multiple
components and bundles can be specified on the same command line. When
mixing components and bundles on the command line, the filter switches
control what components and bundles are installed.
/group
"group_name"
This argument specifies an already defined group name in the HP Smart
Update Manager GUI.
/b[undle]
<bundlename>
or
<bundle1_to_install>
<bundle2_to_install>
This argument specifies the bundles to install. Bundles to install can be
specified with or without the
/b[undle]
argument. If using the
/b[undle
]
argument, only one bundle can be specified with the argument. However,
multiple /b arguments and bundles can be specified on the same line. If the
/b[undle]
argument is not used, multiple bundles can be specified at the
same time, but the bundles need to be separated by a blank and listed after
all the arguments on the command line. Multiple components and bundles
can be specified on the same command line. When mixing components and
bundles on the command line, the filter switches control what components
and bundles are installed.
/allow_update_to_bu
ndle
This argument is a filter switch and enables the user to install newer versions
of components defined in a PSP or firmware bundle. This argument enables
these components to replace the older versions of the same component that
might have shipped with the bundles.
/allow_non_bundle_c
omponents
This argument is a filter switch and enables the user to install components that
are not included in the bundle but reside in the directory with the components
in the bundle.
/use_latest
This argument is a filter switch for use with bundles. The argument enables
you to use the latest version of the bundle when multiple versions of bundles
are listed on the command line. If there are no bundles specified on the
command line, and multiple bundles are in the directory, the
/use_latest
argument allows HP Smart Update Manager to use the bundle with the latest
version for installation.
/use_location
"file_share"
This argument specifies a directory or file share that contains the PSP and
components for use with HP Smart Update Manager. The "file_share" format