NIC Teaming driver
The PSP contains the NIC Teaming driver:
• RSS Teaming
• TOE Configuration
• Broadcom Multi-function Diagnostics
• Broadcom Multi-function offload properties exposed
• Intel driver support
• Broadcom Legacy support
For additional information, see the Using HP ProLiant Network Teaming Software with Microsoft
®
Windows
®
Server 2008 Hyper-V HOWTO at
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01663264/c01663264.pdf.
Installing the PSP
After downloading the PSP self-extracting executable, complete the following steps:
1. Go to the directory where the PSP executable is saved.
NOTE
When installing the PSP on a system running Server Core, you
must execute the executables rather than double-clicking on
them. Also, on Server Core systems, you will not be able to
specify the location for extracting the PSP files. The files will be
extracted to the same location as the PSP self-extracting
executable.
2. Double-click the executable and extract the PSP to a desired location.
3. Go to the directory where the extracted PSP is located.
4. Double-click setup.exe to start the PSP deployment.
NOTE
All PSP files must be present in the same directory as the
setup.exe program for the PSP to be properly installed.
5. As the PSP deployment starts, it performs an inventory of the available updates and checks the
local system to see what hardware and software is installed.
6. After the inventory and discovery processes finish, the “Select Installation Hosts” screen appears,
select either the local host or one (or more) remote hosts for PSP deployment.
7. After selecting the host(s), the “Select bundle filter” screen displays information about the PSP
bundle to be installed. Select the bundle and the appropriate filter options. For remote
deployments, additional screens allow users to update information on a per-host basis.
8. After selecting the bundle for all hosts being updated, open the “Select Items to be Installed”
screen to complete the following tasks:
1. Select the components to be installed.
2. If necessary, configure the components.
3. Review failed dependencies before installation.
4. Review the revision history of the components.
19
To Next Page
Loading...
