HP Integrity rx2800 HP Smart Update Manager User Guide - Page 71

Component configuration for Windows components only, Command-line examples, Windows® PSPs

Get HP Integrity rx2800 - i2 PDF manuals and user guides View all HP Integrity rx2800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 71 highlights

Command-line argument /report /inventory_report /firmware_report Using input files /inputfile "filename" /deleteinputfile "filename" Description This argument generates a report listing, a target summary, and how the components in the repository affect the target (For example, whether each component applies to the target or not). The report name is of the format, HPSUM_ Report__.html By default, it is located in the present working directory from where HP SUM is initiated. If that location is write-protected, the report can be found in the same directory as the HP SUM log files. This argument generates a report listing of the components in the specified repository. The report name is of the format, HPSUM_Inventory_Report__.html By default, it is located in the present working directory from where HP SUM is initiated. If that location is write-protected, the report can be found in the same directory as the HP SUM log files. This argument generates a report listing of the firmware in the specified repository. The report name is of the format, HPSUM_Firmware_Report__.html By default, it is located in the present working directory from where HP SUM is initiated. If that location is write-protected, the report can be found in the same directory as the HP SUM log files. (This CLI does not apply to firmware updates on the HP Integrity BL860c/BL870c/BL890c i2 Servers.) This argument enables you to script the deployment of firmware and software to multiple remote systems at one time. For details of the file format and commands, see "Input files (on page 74)". This argument enables you to instruct HP SUM to delete the input file after it has been read in. Component configuration for Windows components only To configure components without using the HP Smart Update Manager GUI, issue the command, hpsum_config . This command presents the same configuration screens seen in the HP Smart Update Manager GUI. You must run this command from a CD or other read-only media, or the component cannot be configured. Configuration for a given component only needs to be executed one time. The configuration is stored within the component and is propagated to all target servers when deployed through HP Smart Update Manager GUI or command line. To change the configuration, rerun hpsum_config against the component and a new configuration writes out. If a component does not need configuration, the hpsum_config command returns to the console. To configure components to be deployed on all editions of the Windows Server® 2008 with the Server Core option, you must access the system as a remote host using HP Smart Update Manager running on a system with a supported Windows® operating system, and then configure the components before deployment. Command-line examples The following command-line parameter examples can be executed within these environments: • Windows® PSPs: Scripted deployment 71

  • 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
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
Scripted deployment 71
Command-line
argument
Description
/report
This argument generates a report listing, a target summary, and how the
components in the repository affect the target (For example, whether each
component applies to the target or not). The report name is of the format,
HPSUM_ Report_
<date>
_
<time>.html
By default, it is located in the present working directory from where HP SUM
is initiated. If that location is write-protected, the report can be found in the
same directory as the HP SUM log files.
/inventory_report
This argument generates a report listing of the components in the specified
repository. The report name is of the format,
HPSUM_Inventory_Report_
<date>
_
<time>.html
By default, it is located in the present working directory from where HP SUM
is initiated. If that location is write-protected, the report can be found in the
same directory as the HP SUM log files.
/firmware_report
This argument generates a report listing of the firmware in the specified
repository. The report name is of the format,
HPSUM_Firmware_Report_
<date>
_
<time>
.html
By default, it is located in the present working directory from where HP SUM
is initiated. If that location is write-protected, the report can be found in the
same directory as the HP SUM log files. (This CLI does not apply to firmware
updates on the HP Integrity BL860c/BL870c/BL890c i2 Servers.)
Using input files
/inputfile
“filename”
This argument enables you to script the deployment of firmware and software
to multiple remote systems at one time. For details of the file format and
commands, see "Input files (on page
74
)".
/deleteinputfile
“filename”
This argument enables you to instruct HP SUM to delete the input file after it
has been read in.
Component configuration for Windows components only
To configure components without using the HP Smart Update Manager GUI, issue the command,
hpsum_config
<component_to_configure>.
This command presents the same configuration screens
seen in the HP Smart Update Manager GUI. You must run this command from a CD or other read-only
media, or the component cannot be configured. Configuration for a given component only needs to be
executed one time. The configuration is stored within the component and is propagated to all target
servers when deployed through HP Smart Update Manager GUI or command line. To change the
configuration, rerun
hpsum_config
against the component and a new configuration writes out. If a
component does not need configuration, the
hpsum_config
command returns to the console.
To configure components to be deployed on all editions of the Windows Server® 2008 with the Server
Core option, you must access the system as a remote host using HP Smart Update Manager running on a
system with a supported Windows® operating system, and then configure the components before
deployment.
Command-line examples
The following command-line parameter examples can be executed within these environments:
•
Windows® PSPs: