2 Deploying PSPs
PSPs are deployed using HP SUM. In the PSP for Linux, HP SUM enables support for native RPM files. Users can now deploy firmware and software components simultaneously. PSPs can be deployed using graphical or
For more information about PSP deployment with HP SUM, see the HP Smart Update Manager User Guide at http://www.hp.com/support/HP_Smart_Update_Manager_UG_en.
PSP deployment scenarios
Operating system environment | Scenario |
|
|
Microsoft Windows | • Graphical deployment on a |
| • Graphical deployment remotely on a |
| • |
| • |
| • |
|
|
Linux | • Graphical deployment on a |
| • Graphical deployment remotely on a |
| • |
| • |
|
|
|
|
NOTE: If you install a PSP and then install an operating system Service Pack, a Support Pack, or other operating system updates, HP recommends reinstalling the PSP.
Deployment for Microsoft Windows
This section discusses deploying PSPs on Windows operating systems. The PSPs support
For a current list of supported operating systems, see the HP PSP website at http://www.hp.com/ servers/psp.
Minimum requirements for Microsoft Windows PSP
IMPORTANT: Before deploying software updates on a host server, be sure that a recent backup of the host server is available in case the deployment procedure fails.
For successful component deployments on Microsoft Windows hosts, the following minimum requirements must be met:
•A local administrative system with 512 MB of memory and running a supported Windows operating system must be used.
•One or more remote host servers that run a supported Windows operating system and need a software upgrade must be available. If the local administrative system (local host) is the only server that requires an upgrade, then remote host servers are not necessary.
•Sufficient
•WMI must be enabled.
8Deploying PSPs