HP ML350 HP ProLiant Firmware Maintenance CD User Guide - Page 51

Component configuration for Windows components only, Command line examples

Get HP ML350 - ProLiant - G6 PDF manuals and user guides View all HP ML350 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 51 highlights

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 once. 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: o ProLiant Support Pack for Microsoft® Windows Server™ 2003 v7.90 (BP000323.xml) o ProLiant Support Pack for Microsoft® Windows Server™ 2003 v7.80 (BP000315.xml) • Firmware: o System ROM o Smart Array controller o Hard drives o iLO • Software-later version of: o HP Insight Diagnostics Online Edition for Windows Server™ 2003 (cp008097.exe) o HP System Management Homepage for Windows® (cp008257.exe) • HP Smart Update Manager o Defined groups: Management Servers-Three servers (Management Server1, Management Server2, Management Server3) Example 1: This command line input deploys the latest PSP and firmware components: hpsum /use_latest /allow_non_bundle_components /silent Results: All the software components from the 7.90 PSP and firmware components, which HP Smart Update Manager determined needed to be installed, were installed. Example 2: Either of the following command line inputs can deploy the previous version of the PSP only and force all the components to be installed: • hpsum /f:bundle /softwareonly BP000315.xml Scripted deployment 51

  • 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 51
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 once. 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:
o
ProLiant Support Pack for Microsoft® Windows Server™ 2003 v7.90 (
BP000323.xml
)
o
ProLiant Support Pack for Microsoft® Windows Server™ 2003 v7.80 (
BP000315.xml
)
•
Firmware:
o
System ROM
o
Smart Array controller
o
Hard drives
o
iLO
•
Software—later version of:
o
HP Insight Diagnostics Online Edition for Windows Server™ 2003 (
cp008097.exe
)
o
HP System Management Homepage for Windows® (
cp008257.exe
)
•
HP Smart Update Manager
o
Defined groups: Management Servers—Three servers (Management Server1, Management
Server2, Management Server3)
Example 1:
This command line input deploys the latest PSP and firmware components:
hpsum /use_latest /allow_non_bundle_components /silent
Results: All the software components from the 7.90 PSP and firmware components, which HP Smart
Update Manager determined needed to be installed, were installed.
Example 2:
Either of the following command line inputs can deploy the previous version of the PSP only and force all
the components to be installed:
•
hpsum /f:bundle /softwareonly BP000315.xml