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

Firmware Maintenance CD powered by HP Smart Update Manager, Deployment scenarios

Get HP BL680c - ProLiant - G5 PDF manuals and user guides
UPC - 884420396314
View all HP BL680c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 15 highlights

Firmware Maintenance CD powered by HP Smart Update Manager Deployment scenarios HP Smart Update Manager deploys smart firmware components on a local host or one or more remote hosts. The remote hosts must be online and running the same operating system as the system running HP Smart Update Manager. For example, when the remote hosts are running Linux, the HP Smart Update Manager must also be running on a Linux operating system. HP Smart Update Manager supports the following operating systems: • Windows Server® 2003 • Windows Server® 2003 x64 • Windows Server® 2008 • Windows Server® 2008 x64 • Windows Server® 2008 R2 x64 • Red Hat Enterprise Linux 4 • Red Hat Enterprise Linux 5 • SUSE Linux Enterprise Server 10 • SUSE Linux Enterprise Server 11 The following table describes typical HP Smart Update Manager deployment scenarios. Scenario Description Graphical deployment on a local host Scripted deployment on a local host Graphical deployment to a remote host Scripted deployment to a remote host Use this scenario when you: • Are not familiar with command line tools. • Are deploying components on a local, single host. • Do not require scripting. Use this scenario when you: • Are familiar with command line tools. • Are deploying components on a local, single host. • Must perform a customized, scripted deployment. Use this scenario when you: • Are not familiar with command line tools. • Are deploying components on one or more remote hosts. • Do not require scripting. Use this scenario when you: • Are familiar with command line tools. • Are deploying components on one or more hosts. • Must perform a customized, scripted deployment to one or Firmware Maintenance CD powered by HP Smart Update Manager 15

  • 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
Firmware Maintenance CD powered by HP Smart Update Manager
15
Firmware Maintenance CD powered by HP
Smart Update Manager
Deployment scenarios
HP Smart Update Manager deploys smart firmware components on a local host or one or more remote
hosts. The remote hosts must be online and running the same operating system as the system running HP
Smart Update Manager. For example, when the remote hosts are running Linux, the HP Smart Update
Manager must also be running on a Linux operating system. HP Smart Update Manager supports the
following operating systems:
•
Windows Server® 2003
•
Windows Server® 2003 x64
•
Windows Server® 2008
•
Windows Server® 2008 x64
•
Windows Server® 2008 R2 x64
•
Red Hat Enterprise Linux 4
•
Red Hat Enterprise Linux 5
•
SUSE Linux Enterprise Server 10
•
SUSE Linux Enterprise Server 11
The following table describes typical HP Smart Update Manager deployment scenarios.
Scenario
Description
Graphical deployment on a local
host
Use this scenario when you:
•
Are not familiar with command line tools.
•
Are deploying components on a local, single host.
•
Do not require scripting.
Scripted deployment on a local
host
Use this scenario when you:
•
Are familiar with command line tools.
•
Are deploying components on a local, single host.
•
Must perform a customized, scripted deployment.
Graphical deployment to a remote
host
Use this scenario when you:
•
Are not familiar with command line tools.
•
Are deploying components on one or more remote hosts.
•
Do not require scripting.
Scripted deployment to a remote
host
Use this scenario when you:
•
Are familiar with command line tools.
•
Are deploying components on one or more hosts.
•
Must perform a customized, scripted deployment to one or