Service Reference Guide

HP BladeSystem bc2000/bc2500 Blade PC and HP BladeSystem bc2200/bc2800 Blade PC
Copyright 2008, 2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Microsoft and Windows are trademarks of Microsoft Corporation in the U.S. and other countries. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. This document contains proprietary information that is protected by copyright. No part of this document may be photocopied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard Company. Service Reference Guide Business PCs Fourth Edition (July 2009) Document Part Number: 453486-004

Table of contents

1 Spare Parts bc2000/bc2500..... 1 bc2200/bc2800..... Removal and Replacement Returning the HP BladeSystem Blade PC... 3 Removal and Replacement.... 3 Powering Down the BladeSystem PC... 3 Removing a Blade PC.... 4 Replacing the Memory.... 5 Installing a Diagnostic Adapter.... 6 Removing the Air Baffle from the bc2500... 8 Removing the Hard Drive from the bc2200/bc2800... 8 Replacing the PC Battery.... Connectors and Passwords Connectors and Jumpers.... 11 Passwords..... 12 Remove a Setup Password.... 12 Establish a Setup Password.... Diagnostics Diagnostic Indicator Lights..... 13 POST (Power On Self Test) Error Messages... 15 Index..... 18

Spare Parts

The following sections provide spare part information for the bc2000/bc2500 and the bc2200/bc2800.

bc2000/bc2500

Item 1 2* 2* 2* **
Description RTC battery (CR2032) Memory module, PC2-5300, 512 MB Memory module, PC2-5300, 1 GB Memory module, PC2-5300, 2 GB BladeSystem bc2000 PC complete with hard drive (4) and RTC battery (1) For assembly number 445833-008 For assembly number 445933-010 For use in Korea only
Spare Part Number N/A 445934-001 445935-001 445936-001
445938-001 501104-001 445938-003
BladeSystem bc2500 PC complete with hard drive and RTC battery For assembly number 447457-001 For assembly number 447457-010 For use in Korea only 447694-001 501105-001 447694-003 445937-001
80-GB hard drive without mounting bracket
Parts available after expiration of advance exchange warranty. *Memory does not ship with the blade PC. **Not shown

bc2200/bc2800

Item 1 2
Description RTC battery (CR2032) BladeSystem bc2200 PC complete with hard drive and RTC battery For use in the rest of the world For use in Korea only FreeDos version

Spare Part Number N/A

509615-001 509616-001 509619-001
BladeSystem bc2800 PC complete with hard drive and RTC battery For use in the rest of the world For use in Korea only FreeDos version 509617-001 509618-001 509620-001 510451-001 578986-001 510357-001
System board, bc2200/bc2800 160-GB hard drive without mounting bracket 80-GB hard drive without mounting bracket

Chapter 1 Spare Parts

Removal and Replacement
NOTE: The BladeSystem PC may be covered under an advance exchange warranty provision. Check the warranty documentation that came with your BladeSystem PC for more information.
Returning the HP BladeSystem Blade PC
Before returning the HP BladeSystem Blade PC for repairs: 1. 2. Reinstall the image on the hard drive before calling for a replacement unit. A faulty image can act like a component failure. Remove all memory installed on the BladeSystem PC. No memory will be shipped on the replacement unit.
Powering Down the BladeSystem PC
1. Ensure the blade PC is not active by verifying that the Health LED (2) is off.

Item 1

LED Unit Identification
Status Off Blue Blue blinking
Description Off Identification of blade PC Being remotely accessed Blade PC off Blade PC on and good health Blade PC degraded or power-up prohibited by the Integrated Administrator. Blade PC critical Blade PC critical No connection Linked to network Linked and activity on the network No connection Linked to network Linked and activity on the network No drive activity Drive activity No AC power to enclosure or blade PC Enclosure on and health good Blade PC power turned on

Health

Off Green Amber Red Red blinking

Off Green Green blinking

Drive activity

Off Green blinking

Off Amber Green

2. 3. 4.

If the blade PC is active, notify the users and stop applications as necessary. Shut down the operating system. This may shut off blade PC power. If the blade PC still has power, power down the blade PC by either: Using the Integrated Administrator, or Pressing the power button (6) on the front of the blade PC.

To perform an emergency shut down of the blade PC, press and hold the blade PC power button for four seconds. CAUTION: Performing an emergency shutdown on a blade PC may result in the loss of any unsaved data.

Removing a Blade PC

To remove a blade PC: 1. 2. Power down the blade PC (Powering Down the BladeSystem PC on page 3). Press the release latch (1).
Chapter 2 Removal and Replacement
Pull down the ejector lever (2). Remove the blade PC from the enclosure.
To install a new blade PC, reverse the removal procedures.

Replacing the Memory

1. 2. 3. 4. Power down the blade PC (Powering Down the BladeSystem PC on page 3). Remove the blade PC from the enclosure (Removing a Blade PC on page 4). Release the latches on each side of the DIMM slot (1). This allows the module to rotate upward. Remove the DIMM from the slot (2).

bc2800 shown

To replace the module: 1. Insert the DIMM at a 15 degree angle (1), making sure that the notch on the bottom of the DIMM aligns with the notch in the socket.
Press the DIMM down toward the board (2), ensuring that it is fully seated and the two latches snap into place.
Installing a Diagnostic Adapter
1. 2. Power down the blade PC (Powering Down the BladeSystem PC on page 3). Insert the adapter into the diagnostic connector on the front of the blade PC (1).
Tighten the thumbscrews that secure the adapter in place (2). Figure 2-1 Attaching the USB 1.1 diagnostic adapter
Figure 2-2 Attaching the USB 2.0 diagnostic adapter
To remove the diagnostic adapter, reverse the removal procedures.
Removing the Air Baffle from the bc2500
The blade bc2500 PC ships with an air baffle installed, as shown in the following image. You must remove this baffle (3 screws) to access the RTC battery.
Removing the Hard Drive from the bc2200/bc2800
To remove the hard drive from the bc2200/bc2800 blade PC, follow these steps: 1. 2. Remove the three screws (1) that secure the hard drive cage to the blade PC. Slide the hard drive cage to the right (2), and then lift it off the blade PC.

Remove the hard drive from the cage by removing the four screws (circled in the following image) that secure the hard drive in the cage.
Remove the hard drive from the cage.
To replace the hard drive, reverse the removal procedures.

Replacing the PC Battery

When your blade PC no longer automatically displays the correct date and time, you may need to replace the battery that provides power to the real-time clock. Under normal use, battery life is usually about 5 to 10 years. Use an CR2032 replacement battery. To install a new battery: 1. 2. 3. Power down the blade PC (Powering Down the BladeSystem PC on page 3). Remove the blade PC from the enclosure (Removing a Blade PC on page 4). If you are replacing the battery on a bc2800 Blade PC, remove the four screws securing the heatsink assembly, then lift off the heatsink assembly.
Locate the battery holder on the blade PC.
Remove the existing battery.

Install the new battery.

If you are replacing the battery on a bc2800 Blade PC, reinstall the heatsink assembly. a. b. Spread thermal grease on the heatsink to provide good contact between the heatsink and the processor. Place the heatsink assembly in position and fasten the four screws to secure the assembly to the blade. Tighten the CPU heatsink screws to 8 inch-lbs of tension.
Install the blade PC in the enclosure and power up the blade PC. Run the Computer Setup (F10) Utility to reconfigure the blade PC with the new battery.

Connectors and Passwords

Connectors and Jumpers

Item E14 E49 P60

Description Boot block enable jumper. Install to enable flashing the boot block. Password jumper. Right angle mobile SATA connector.
SW50 XBT1 XMM1 or DIMM1 XMM2 or DIMM2 XU1
CMOS reset button. RTC battery. Memory module socket 1. Memory module socket 2. Processor socket.

Passwords

Remove a Setup Password
1. 2. 3. 4. Power down the blade PC (Powering Down the BladeSystem PC on page 3). Remove the blade PC (Removing a Blade PC on page 4). Remove a jumper on the E49 header. Power up the unit. The password is removed.

Establish a Setup Password
The blade PC ships from the factory with the jumper installed on the E49 header. If the jumper is installed, you can establish a Setup Password by powering up the blade PC and using F10. If the jumper has been removed, use the following steps: 1. 2. 3. 4. Power down the blade PC (Powering Down the BladeSystem PC on page 3). Remove the blade PC (Removing a Blade PC on page 4). Install the jumper from the E49 header. Power up and use F10 Setup to establish the Setup Password.
Chapter 3 Connectors and Passwords

Diagnostics

Diagnostic Indicator Lights
Health LED Red Red Red Red Activity Solid, Power LED is off. Solid, Power LED is on. 1 Blink 2 Blinks Problem Blade BMC fault BIOS critical fault after video Blade PC on-board Voltage Regulator Module (VRM) Fault Processor thermal protection is activated Corrective Action Replace blade PC. Look for the POST error message at F1 prompt. Replace blade PC. Red Red 3 Blinks 4 Blinks CPU (blade PC system board) failure The enclosure power connector for the blade PC has failed or the enclosure power supply has failed. System board (hot swap circuitry) has failed. Red 5 Blinks SODIMM(s) may not be seated correctly, SODIMM(s) may be bad, or blade PC system board may be bad. Ensure enclosure fans functioning properly and enclosure has adequate ventilation. Check heatsink. Replace system board if condition exists after taking corrective actions.
Replace blade PC. Move blade PC to different bay to see if blade PC functions properly. If this corrects issue, there is problem with enclosure backplane. If the solution above did not resolve the problem, replace the blade PC. Check if memory is present. If so, try reseating memory and rebooting. Replace memory Replace blade PC.

Red Red Red

6 Blinks 7 Blinks 8 Blinks
The blade PC graphics subsystem has failed. Blade PC system board failure Enclosure communications fault
Replace blade PC. Replace blade PC. Swap blade PC to a different bay in enclosure and retest. Put blade PC into a different enclosure. If blade PC works in a different enclosure, troubleshoot original enclosure. Replace blade PC.

Red Amber

9 Blinks Solid
NIC A or NIC B has failed Computer may have stopped at F1
Reboot enclosure, and then remove and reinsert blade PC into enclosure. Check POST error message or remote console log in Integrated Administrator to see what POST messages were in the log last. Ensure enclosure fans functioning properly and enclosure has adequate ventilation. Check heatsink. Replace system board. Ensure enclosure health LED is green and health status is ok. If LED not green, troubleshoot enclosure. If enclosure health LED is green, check heatsink installation and operating ambient. Make sure every enclosure slot is filled with a blank or a blade PC. Remove blade PC and check if heatsink is loose or not present. Tighten CPU heatsink screws to 8 inch-lbs of tension. Replace blade PC if messages persist. Check event logs in operating system to ensure no software lockup. Disable Automated System Recovery in F10 Setup. Follow standard operating system debugging procedure. Reinstall system image. Reflash BMC. Replace blade PC. Reflash BIOS. Replace blade PC.

1 Blink

If the power LED is off or yellow, the blade PC experienced a Tcaution graceful shutdown due to a thermal trip point being crossed. (bc2500 only) Processor throttling

2 Blinks

Heatsink is loose
Amber 3 Blinks Automated System Recovery Amber 4 Blinks BMC Flash Fault Amber 5 Blinks BIOS Flash Fault Amber 6 Blinks Cold temperature fault
The blade PC is operating at temperatures below specification. Operate the blade PC within environmental specifications. If enclosure Health is okay, move blade PC to different bay. If: problem follows the move, replace blade PC. problem is solved - enclosure backplane problem.
Enclosure or blade PC system board power failure

Chapter 4 Diagnostics

POST (Power On Self Test) Error Messages
The Integrated Administrator (IA) has details containing new information it receives from the Blade Management Controller (BMC). You can use the IA syslog to determine when a fault occurred.
Message 101-Option ROM Checksum Error Health LED Red Corrective Action 102/103-System Board error Red 162-System Options Not Set Amber 163-Time & Date Not Set Amber 164-Memory Size Error Amber 201-Memory Error Red 301-Keyboard Error 303-Keyboard Controller Error Amber 304-Keyboard or System Unit Error Amber 1780-Disk 0 Failure Amber 1792-No IDE fixed disk present Amber Clear CMOS. Flash ROM if necessary. Replace blade PC. Clear CMOS. Replace blade PC. Set time and date in Computer Setup. Replace RTC battery. Set time and date in Computer Setup. Replace RTC battery. Ensure DIMMs properly installed. Verify proper DIMM type. Remove and replace modules one at a time to isolate faulty module. Replace blade PC. Ensure DIMMs properly installed. Verify proper DIMM type. Remove and replace modules one at a time to isolate faulty module. Replace blade PC. Reconnect keyboard with blade PC turned off. Try different keyboard. Replace blade PC. Reconnect keyboard with blade PC turned off. Replace keyboard. Replace blade PC. Run Computer Setup DPS Self Test from Computer Setup. Replace hard drive. Check if hard drive is present. If so, run Computer Setup DPS Self Test from Computer Setup. Replace hard drive.
Invalid Electronic Serial Number
Run Computer Setup. If data is loaded/will not allow changes, download SP5572.EXE (SNZERO.EXE) from http://www.hp.com. Run Computer Setup, enter serial number under Security, System ID, then save changes. Ensure that system fans functioning properly and enclosure has adequate ventilation. Check processor heatsink. Replace blade PC.
6901-System was gracefully shutdown due to CPU overheating. Amber 6904-System experienced an unexpected shutdown on previous boot. 6906-Embedded Network Controller B Hardware Failure Detected 6907-Embedded Network Controller Hardware Failure Detected 6908-System Board Hardware Failure Detected 6909-System Board Graphics Subsystem Failure Detected 6911-System Board CPU Subsystem Failure Detected 6912-System Board Voltage Regulator Failure Detected Green

This may be due to forced enclosure shutdown or improper diagnostic adaptor insertion. If problem persists, replace blade PC. Clear CMOS. Replace blade PC. Clear CMOS. Replace blade PC.

Red Red

Replace blade PC. Clear CMOS. Replace blade PC. Clear CMOS. Replace blade PC. Swap blade PC to a different bay in enclosure and retest. Put blade PC into a different enclosure. If blade PC works indifferent enclosure, troubleshoot original enclosure. Replace blade PC. Swap blade PC to a different bay in enclosure and retest. Put blade PC into a different enclosure. If blade PC works in a different enclosure, troubleshoot original enclosure. Replace blade PC. Ensure system fans are functioning properly and enclosure has adequate ventilation. Check heatsink. Replace blade PC.
6913-System Board Voltage Failure Detected Red
6914-Forced System Shutdown from an over-temp fault condition on previous boot Green 6915-CPU not present on previous attempt to boot. Green
A blade PC without a processor was inserted on previous attempt to boot.
6916-CPU Heatsink not properly attached
Remove blade PC and check if heatsink is loose or not present. Tighten CPU heatsink screws to 8 inch-lbs of tension. Replace blade PC if message persists. Check event logs in operating system to ensure no software lockup. Disable Automated System Recovery in F10 Setup. Follow standard operating system debugging procedure. Reinstall system image. Replace CMOS battery. If the problem persists, replace blade PC.
6917-System was rebooted due to a potential lock up. Amber 6918-System Real Time Clock Oscillator not running within tolerance 6919-Temperature and Power Monitoring Hardware failure 6920-Processor in Force-Throttle Mode Amber Red Amber
Replace blade PC. Ensure enclosure health LED is green and health status OK. If LED not green, troubleshoot enclosure. If enclosure health LED is green, check heatsink installation and operating ambient. Make sure every enclosure slot is filled with a blank or a blade PC.
6921-Blase System Management Controller firmware update failed. 6922-Blade temperature detected to be below 0 degrees Celsius 6923-CPU Temperature Monitoring Hardware failure 6924-Graphics Temperature Monitoring Hardware failure 6925-Blade/Enclosure Communication error

Amber Amber Red Red Red

Reflash BMC firmware image. Check operating ambient. Operate the blade PC within environmental specifications. Replace blade PC. Replace blade PC. Swap blade PC to a different bay in enclosure and retest. Put blade PC into a different enclosure. If blade PC works in a different enclosure, troubleshoot original enclosure. Check for faulty Integrated Administrator module. Replace blade PC.
6927-Previous POST under Recovery BIOS 6928-POST under Recovery BIOS image Green Amber
Informational Reflash BIOS If message persists, replace blade PC.
6929-Blade performance is reduced due to insufficient enclosure power and/or cooling NOTE: For bc2800 in a PC Blade Enclosure only
Remove the blade PC and insert it into a PC Blade Enclosure G2 or upgrade your enclosure with a PC Blade Enclosure G2 upgrade kit.
A air baffle 8 Automated System Recovery 14 B baffle 8 battery 9, 12 bc2000 spare part number 1 bc2200 PC spare part number 2 bc2500 spare part number 1 bc2800 PC spare part number 2 blade BMC fault 13 blade PC LEDs 3 powering down 3 removing 4 replacing the memory 5 returning 3 VRM fault 13 BMC flash fault 14 boot block enable jumper 11 C CMOS button 12 connectors and jumpers 11 D Diagnostic Adapter 6 diagnostic indicator lights 13 drive activity LED 4 E EE49 11, 12 emergency shutdown 4 error messages, POST 15 establishing a Setup Password 12
H hard drive removing 8 spare part number 1, 2 health LED 3, 4, 13 heatsink torque 14 I installing a Diagnostic Adapter 6 J jumpers 11 K Korean blade PC bc2000 spare part number 1 bc2200 spare part number 2 bc2800 spare part number 2 L LEDs 3, 13 lights 13 M memory module replacing 5 socket 12 spare part number 1 messages, error 15 N NIC A LED 4 NIC B LED 4 P Ppassword jumper 11 passwords 12 performing an emergency shutdown 4
POST error messages 15 power button 4 power LED 4 powering down the blade PC 3 processor socket 12 R removal and replacement procedures 3 removing a blade PC 4 removing a Setup Password 12 removing the hard drive 8 replacing the battery 9 replacing the memory in the blade PC 5 returning the blade PC 3 RTC battery 12 S SATA connector 11 Setup Password establishing 12 removing 12 shutdown 4 spare parts bc2000/bcbc2200/bcSWsystem board battery replacement 9 spare part number, bc2200/ bcT Tcaution 14 thermal protection 13 torque 14 U unit identification LED
USB 1.1 Diagnostic Adapter 7 USB 2.0 Diagnostic Adapter 7 X XBTXMM1 & XU1 12

HP Blade PC Software Components
All blade PC software components delivered with the factory image and restore kit can also be downloaded from the HP Web site at http://hp.com/support. In addition, the Web site contains software components that neither the factory image nor the restore kit contain. The following sections describe the software components provided for the bc1500 Blade PC and bc2000 and bc2500 Blade PCs. They are organized by blade PC model and their delivery method (preinstall, restore, Web).
HP bc1500 Blade PC Software Components
This section provides a list and description of each bc1500 software component. Some of these components are included with the preinstall image and Restore Plus! kit. Some are delivered only on the Web. HP bc1500 Blade PC Factory (preinstalled) Image Components Every bc1500 ships with Windows XP Professional Service Pack 2 Blade PC Edition preinstalled on the hard drive. The following table lists the software components unique to the blade PC that are included with the factory image.
Table 2. HP bc1500 Blade PC Pre-installed Software Components Deliverable Altiris Deployment Solution Agent (AClient) Version 6.10 Description Enables the blade PC to be managed by Altiris Deployment Server. It enables the blade PC to receive jobs from the Deployment Server, and it reports client status to the Server. This version is specific to Windows XP and does not work with Windows Vista. Provides HP-recommended operating system settings for the blade PC environment. Note: this version is being replaced by version 1.5, which supports the bc1500/bc2000/bc2500. See Blade PC Specific CustomizationsOperating System Settings for a list of settings. Network Interface Controller hardware enabling drivers Also known as: HP Blade PC Automated System Recovery (ASR-2). This service monitors the hardware WatchDog Timer on the blade PC. The service enables a countdown timer in the hardware that automatically reboots the blade PC, if not reset. The service then resets the timer at an interval that prevents automatic reboot. Any hang or lockup on the blade PC that prevents the service from resetting the timer causes the blade PC to reboot automatically and be available for use. This package contains a fix for an audio redirect issue with Windows XP Service Pack 2 (SP2) that occurs when more than one user connects through Remote Desktop Connection (RDC). For more information, see Microsoft Knowledge Base article 886199, You cannot redirect audio to a client computer when you are running a Remote Desktop Connection in Windows XP at http://support.microsoft.com/kb/886199/en-us.

Blade PC Specific Tweaks (Operating System Settings)
Broadcom NIC Drivers for Windows XP HP WatchDog Timer Service

8.27.1 1.00

Q886199Windows Fix_for RDC Audio redirect failure
Deliverable Q890859Vulnerabilities in Windows XP SP2 Kernel

Version 1.00

Description For more information, see Microsoft Knowledge Base article 890859, ''MS05018: Vulnerabilities in Windows kernel could allow elevation of privilege and denial of service.'' http://support.microsoft.com/kb/890859/en-us. For more information about this issue, refer to Microsoft Knowledge Base article 895246, The DhcpRequestParams function does not work correctly on a computer that is running Windows XP Service Pack 2. http://support.microsoft.com/kb/895246/en-us.
Q895246Windows Fix_for DhcpRequestParams function broken on SP2
HP bc1500 Blade PC Restore Kit Components Every bc1500 10-pack ships with a restore kit. As stated previously, the restore kit consists of a Restore Plus! disc and a Windows XP Professional Service Pack 2 disc. With the exception of the Q890859, Vulnerabilities in Windows XP Service Pack 2 Kernel QFE, all components listed in Table 2 are also included in the restore kit and are installed during a restore of the Windows XP image. In addition to driving the restore process, the Restore Plus! disc contains the following software components, in user-installable SoftPaq format. They are located in the <disc drive>:\SoftPaqs folder.
Table 3. Restore Plus! User Installable SoftPaq components Deliverable Blade PC Specific Tweaks aka HP Blade PC Optimization (Operating System Settings) Version 1.00 Description Provides HP-recommended operating system settings for the blade PC environment. Note: this version is being replaced by version 1.5, which supports the bc1500/bc2000/bc2500. See Blade PC Specific CustomizationsOperating System Settings for a list of settings. Network Interface Controller hardware enabling drivers Also known as: HP Blade PC Automated System Recovery (ASR2). This service monitors the hardware WatchDog Timer on the blade PC. The service enables a countdown timer in the hardware that automatically reboots the blade PC, if not reset. The service then resets the timer to an interval that prevents automatic reboot. Any hang or lockup on the blade PC that prevents the service from resetting the timer causes the blade PC to reboot automatically and be available for use. This package contains a fix for an audio redirect issue with Windows XP Service Pack 2 (SP2) that occurs when more than one user connects through Remote Desktop Connection (RDC). For more information, see Microsoft Knowledge Base article 886199, You cannot redirect audio to a client computer when you are running a Remote Desktop Connection in Windows XP at http://support.microsoft.com/kb/886199/en-us.

HP bc1500 Blade PC Windows XP Web Deliverables All preinstalled/restore software components described above are also downloadable from the HP Web site at http://hp.com/support. The Web site also contains additional software that is not included in either the preinstall or restore kit. Table 4 lists these additional components.
Table 4. HP bc1500 Blade PC Windows XP Web software not included with the preinstall or restore Deliverable HP CCI Remote Personalized Time Zone Utility HP Consolidated Client Infrastructure Heart Beat Software Version 1.1.0.9 Description The HP CCI Remote Personalized Time Zone utility gives endusers residing in separate time zones the ability to adjust the blade PC time zone setting. The HPCCISHB software enables a blade PC within the Consolidated Client Infrastructure (CCI) environment to work with software that can dynamically assign a client to a blade PC, such as BIGIP from F5 Networks, Inc. If you have HP Session Allocation Manager installed, this software is not necessary. HP Consolidated Client Infrastructure Session Timers Software 1.3.0.9 The HPCCIST software emulates the Terminal Services session timers found in the Windows 2003 Server Operating System. These timers may allow more efficient allocation of blade PCs in environments where there is not a one-to-one ratio between clients and blade PCs. Changes the time zone data to account for the DST change for the United States. For more information, see Microsoft Knowledge Base article 931836 February 2007 cumulative time zone update for Windows operating systems.

1.0.6.1

Q928388Windows Global Time Zone Update For Windows XP SP2
HP bc1500 Blade PC Windows Vista Web Deliverables Although the bc1500 ships with an OEM Windows XP Professional Service Pack 2 image, it has been tested to ensure compatibility with Windows Vista Business 32-Bit Edition. The chipset, graphics, and NIC subsystems are supported by Windows Vista; therefore, no additional hardware-enabling drivers are required to be added to the Windows Vista image. The following bc1500 Windows Vista software components will be available on the bc1500 driver download Web site by June 2007.

Table 6. HP bc2000 and bc2500 Blade PCs Pre-installed Software Components Deliverable Altiris Deployment Solution Agent for Windows Vista (DAgent) AMD Dual Core Optimizer Version 6.8.282 Description Enables the blade PC to be managed by Altiris Deployment Server. It enables the blade PC to receive jobs from the Deployment Server, and it reports client status to the Server. This version is specific to Windows Vista. Helps improve some application video performance by compensating for those applications that bypass the Windows API for timing by directly using the RDTSC (Read Time Stamp Counter) instruction. Graphics hardware enabling driver This driver is needed to ensure PCI compliance while running the Microsoft Device Windows Vista Test Manager (DTM). Provides HP-recommended operating system settings for the blade PC environment. Note: this version supports the bc1500/bc2000/bc2500. See Blade PC Specific CustomizationsOperating System Settings for a list of settings. Network Interface Controller hardware enabling driver This version supports bc1500 Blade PC & bc2000/bc2500 Blade PCs. For bc1500 Blade PCs, this service monitors the hardware WatchDog Timer. The service enables a countdown timer in the hardware that reboots the blade PC, if not reset. The service then resets the timer to an interval that prevents automatic reboot. Any hang or lockup on the blade PC that prevents the service from resetting the timer causes the blade PC to reboot automatically and be available for use. It also provides the OS name and computer/blade PC name to the enclosure IA. For bc2x00 Blade PCs, it only provides the computer/blade PC name to the system BIOS. The other functions described above are now performed by bc2x00 BIOS.

1.1.1.0135

ATI Graphics Driver for Windows Vista ATI PCI Express North Bridge Filter Driver for Windows Vista Blade PC Specific Customizations

8.351 1.0.0.2 1.5.0.3

Broadcom NIC Drivers for Windows Vista Health ServiceBlade PC Automated System Recovery (ASR2)

10.10.0.0 2.00

Deliverable Q929685_X32 HD Audio Disappears After Sleep On Windows Vista
Description Fixes a problem in which a high definition audio device may no longer work after waking Windows Vista from sleep or from hibernation and then restarting the computer. For more information, see Microsoft Knowledge Base article 929685 at http://support.microsoft.com/kb/929685/en-us. Note: this QFE is available on Windows Update; therefore, it is not posted to the HP support download Web site.

ATI PCI Express North Bridge Filter Driver for Windows Vista ATI Graphics Driver for Windows Vista Blade PC Specific Customizations

1.0.0.2 8.351 1.5.0.3

HP bc2000 and bc2500 Blade PCs Windows Vista Web Deliverables Except where indicated in the description notes, all preinstalled/restore software components described previously are also downloadable from the HP Web site at http://hp.com/support. The Web site also contains an additional software application that is not included in either the preinstall or restore kit.
Table 8. HP bc2000 and bc2500 Blade PCs Windows Vista Web not included with the preinstall or restore Deliverable HP CCI Remote Personalized Time Zone Setting Version 1.1.0.9 Description The HP CCI Remote Personalized Time Zone utility gives endusers residing in separate time zones the ability to adjust the blade PC time zone setting.
HP bc2000 and bc2500 Blade PCs Windows XP Web Deliverables Although the bc2000 and bc2500 ship with OEM Windows Vista Business 32-Bit, it has been tested to ensure compatibility with Windows XP Professional Service Pack 2.
Table 9. HP bc2000 and bc2500 Blade PCs Windows XP Professional Service Pack 2 Software components available on Web Deliverable AMD Dual Core Optimizer Version 1.1.1.0135 Description Helps improve some application video performance by compensating for those applications that bypass the Windows API for timing by directly using the RDTSC (Read Time Stamp Counter) instruction Enables the computer to automatically adjust the processor (CPU) speed, voltage, and power combination to match the user's performance needs Hardware enabling drivers for the ATI RS690 graphics controller Windows XP Chipset driver for ATi RS690T/SB600 Chipset
AMD Cool and Quiet CPU Driver ATI Graphics driver for Windows XP ATI SMBus Chipset Driver for Windows XP and Windows 2000 Blade PC Specific Customizations

1.3.2.0

8.62+ 5.10.1000.6

1.5.0.3

Provides HP-recommended operating system settings for the blade PC environment. Note: this version supports the bc1500/bc2000/bc2500. See Blade PC Specific CustomizationsOperating System Settings for a list of settings. Hardware enabling driver for the Broadcom 5906m network interface controller
Broadcom Drivers for Windows XP

10.26.0.0

Deliverable Health ServiceBlade PC Automated System Recovery (ASR2)

Version 2.00

Description For bc1500 Blade PCs, this service monitors the hardware WatchDog Timer. The service enables a countdown timer in the hardware that automatically reboots the blade PC, if not reset. The service then resets the timer to an interval that prevents automatic reboot. Any hang or lockup on the blade PC that prevents the service from resetting the timer causes the blade PC to reboot automatically and be available for use. It also provides the OS name and computer/blade PC name to the enclosure IA. For bc2x00 Blade PCs, it only provides the computer/blade PC name to the system BIOS. The other functions described above are now performed by bc2x00 BIOS.

Windows XP Only: Disables the parallel port service and prevents it from logging an entry in the Event Viewer. HP blade PCs do not have a parallel port. Windows Vista does not create an entry in the Event Viewer. bc1500 Blade PC only: Provides support for no video (headless) by modifying a registry key at every restart (reboot) in order to prevent compatibility issues with 16-bit applications. Since the bc2000 Blade PC has an integrated graphics controller, this setting is not modified.

Image Considerations

Each customer has unique image requirements based on software applications, user behavior, business practices, and CCI design and implementation, which causes each image to be different. When designing a blade PC image, each Operating System setting and software component should be reviewed and considered for inclusion into the software image. Refer to sections HP bc1500 Blade PC Software Components and HP bc2000 and bc2500 Blade PC Software Components in this white paper for a description of each of these components. Customers using Windows XP images and roaming profiles should consider implementing the Microsoft User Profile Hive Cleanup Service. Even after implementing the Delete cached copies of roaming profiles Group policy setting, some conditions can still cause a users profile to remain on the blade PC after the user logs off. Version 1.6d can be downloaded from User Profile Hive Cleanup Service v1.6d. Version 2.0 may be available in the near future. To ensure that you have the latest version of this service, search the Microsoft Web site for UPHclean. Windows Vista does not require the User Profile Hive Cleanup Service.

Image compatibility

Each customer image is different; therefore, this procedure is a guideline for the minimum of steps required to create an image compatible with bc1500 Blade PC and bc2000 and bc2500 Blade PCs. It is recommended that the resulting image be tested for functionality and compatibility prior to deployment into the production environment. Because of the hardware differences between the bc1500 Blade PC and bc2000 and bc2500 Blade PC hardware, the Microsoft Sysprep utility is required to create a common Windows XP image for the bc1500 Blade PC and bc2000 and bc2500 Blade PCs. To configure HP RDP 3.50 and 3.60, which contains Altiris Deployment Server 6.8 Service Pack 1, to use Sysprep for Windows XP, the Sysprep files must be added to the Deployment Server. Adding Microsoft Sysprep files to Altiris Deployment Server 6.8 Service Pack 1 can be accomplished during or after the installation of the Deployment Server software. To add the Sysprep files after the installation of the Deployment Server Software, perform the following steps:

1. Insert the HP RDP disc into the disc drive of the server hosting the HP RDP installation. 2. Close the autorun window. 3. Launch <disc drive>:\ds\setup.exe. 4. Select Components installation and click Install. 5. Check Add Microsoft Sysprep files and click Next. 6. When prompted, insert a Windows XP or Windows Server 2003 32-Bit operating system disc into

the disc drive.

7. Click the Browse button next to Windows XP/2003 and navigate to the location of the
deploy.cab file. Click Next.
8. Verify the location of Windows XP. The deploy.cab file is likely to be located at
<disc drive>:\SUPPORT\TOOLS\deploy.cab.
9. Click Install and Finish to complete the installation.
Deploying Windows XP and Windows Vista images prepared with Sysprep require that a Microsoft Product Key be supplied during the image deploy process. When using the bc1500 Windows XP factory image, prevent blade PC users from being prompted for a product key by configuring the Sysprep environment with the OEM Preservation Key. This key is included in the Microsoft TechNet Library article entitled Preserving OEM Pre-Activation when Re-installing Windows XP. Windows Vista requires activation, which can be accomplished by using a Key Management Service Key (KMS) or Multiple Activation Key (MAK). More information is available at Windows Vista Volume Activation Technical Guidance Home Page and Knowledge Base 929712: Volume Activation information for Windows Vista.
HP bc1500 Blade PC Windows XP Professional Service Pack 2 compatibility with the HP bc2000 and bc2500 Blade PCsbased on the bc1500 Blade PC PreInstall Image.
A bc1500 Blade PC Windows XP image can be configured to be compatible with bc2000 and bc2500 Blade PCs by adding the bc2000 Blade PC chipset, graphics, and NIC drivers and by using HP RDP 3.50 and 3.60 and Sysprep to capture the image. Using the existing bc1500 Blade PC Windows XP image, perform the following steps:
1. If the image contains Blade PC Automated System Recovery (ASR2) version less than 2.0,
uninstall using the command hpwdt.exe -remove. Download and install Blade PC Automated System Recovery (ASR2) version 2.0 or newer.
2. C:\Compaq is the default upper level folder for the bc1500 Blade PC Windows XP PreInstall
image. If this folder does not exist, create it. You may substitute a different name for Compaq. If you do this, make sure you change all references below from Compaq to the name you choose. In the C:\Compaq folder, create individual folders for each Windows XP driver for the bc2000 Blade PC. a. C:\Compaq\bc2000Chipset b. C:\Compaq\bc2000NIC c. C:\Compaq\Graphics

3. Copy the bc2000 Blade PC Windows XP drivers into the appropriate folders. Drivers can be found at http://welcome.hp.com/country/us/en/support.html?pageDisplay=drivers by searching for
bc2000. a. ATI SMBus Chipset Driver for Windows XP and Windows 2000 b. Broadcom Drivers for Windows XP c. ATI Graphics driver for Windows XP
4. Edit the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\DevicePath
Registry KEY, and add a path for each folder created in step 3, separating each path with a semicolon (;). Example: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\DevicePath = %SystemRoot%\inf;%SystemDrive%\Compaq\bc2000Chipset;%SystemDrive%\Compaq\bc2000 NIC;%SystemDrive%\Compaq\bc2000Graphics
5. Add a path for each folder created in step 3 for OemPnPDriversPath variable in the [Unattended]
section of the Sysprep.inf file.
Example: OemPnPDriversPath="Compaq\bc2000Chipset;Compaq\bc2000NIC;Compaq\bbc2000Graphi cs"
6. Use HP RDP with Sysprep options mini quiet reseal to capture the common image. 7. Configure the deploy job to use the modified Sysprep.inf file.
Note: If the ATI Catalyst Control center software is installed in the base OS image, users of the bc1500 are prompted with an error, because the bc1500 does not have ATI graphics.
HP bc1500 Blade PC Windows Vista image compatibility with the HP bc2000 and bc2500 Blade PCsbased on a Windows Vista Business Volume License Kit disc installation
A bc1500 Blade PC Windows Vista image can be configured to be compatible with bc2000 and bc2500 Blade PCs by adding the bc2000 Northbridge Filter, graphics, and NIC drivers and by using HP RDP 3.50 and 3.60 and Sysprep to capture the image. Follow the steps below to create the common image. Using the existing bc1500 Windows Vista image, perform the following steps:
1. The unattend.xml file created by Altiris Deployment Server uses C:\Drivers as the default upper
level folder for the driver files. Create the C:\Drivers folder with individual folders for each Windows Vista driver for the bc2000. a. C:\Drivers\bc2000NIC b. C:\Drivers\bc2000Graphics c. C:\Drivers\bc2000NBFilter
2. Copy the bc2000 Windows Vista drivers into the appropriate folders. Drivers can be found at http://welcome.hp.com/country/us/en/support.html?pageDisplay=drivers by searching for bc2000.
a. Broadcom Drivers for Windows Vista b. ATI Graphics driver for Windows Vista c. ATI PCI Express North Bridge Filter Driver for Windows Vista

3. Execute PNPUTIL.exe A C:\Drivers\
Some situations require that PnPUtil.exe be executed on each.inf file to be included in the Plug and Play portion of the Windows Vista OS unbundle processing.
4. Create image capture job.
Configure the HP RDP with Sysprep Advanced options as follows: a. Uncheck Persist all PnP devices installed. b. Set PnP drivers Path to C:\Drivers
5. Configure the deploy job to use Sysprep.
HP bc2000 and bc2500 Blade PCs Windows Vista Business 32-Bit compatibility with HP bc1500 Blade PCbased on the HP bc2000 Blade PC PreInstall Image
The Windows Vista image preinstalled for the bc2000 is compatible with the bc1500. No additional drivers are required to be added to the image. Using the existing bc2000 Windows Vista image, perform the following steps:
1. Create image capture job using the default Sysprep Advanced Options. 2. Configure the deploy job to use Sysprep.
Note: HP and Microsoft recommend carefully planning and testing such changes in security infrastructure before implementing them in a production environment.
Imaging Considerations Using HP Rapid Deployment Pack
New for CCI: Rapid Deployment Pack 3.50 and 3.60
One feature of CCI is the use of the HP Rapid Deployment Pack (RDP) for software management on the HP blade PCs. This section provides an overview of changes included in the HP RDP 3.50 and 3.60 releases. For more information on any of these items, please refer to the appropriate HP RDP documentation. HP RDP 3.50 and v 3.60 releases contain Altiris Deployment Server 6.8 Service Pack 1. Support for Windows Vista Image Management Added support for image management of target systems running Windows Vista. Windows Vista target systems use DAgent, which is a new Deployment Agent. DAgent, included in Altiris Deployment Server 6.8 Service Pack 1, does not place an icon in the operating system notification area. All connection status and configuration of the Windows Vista Agent are accomplished in the Deployment Server. Windows XP clients continue to use the AClient deployment agent. Sysprep on Windows Vista Added support for Windows Vista image management requires Sysprep to generate unique security identifiers (SIDs) for each blade PC. SIDgen, an Altiris tool, is not supported for Windows Vista image management. Linux 2.6.16.20 Environment Pre-boot RDP 3.50 provides support for Linux 2.6.16.20 to be used for the Pre-boot eXecution Environment (PXE). Additional Hardware Support HP RDP 3.50 and 3.60 provides support for the bc2000, bc 2500, and a variety of new HP server hardware. The drivers required to support the bc2000 and bc2500 Blade PCs DOS PXE are included in the Deployment Solution.

Thin Client View Deployment console contains a new Thin Client View, which simplifies management of Thin Client Devices.
Considerations when using HP RDP 3.50 and 3.60
DAgent Connection to the Deployment Server The Altiris Deployment Agent (DAgent) used for Windows Vista does not automatically create the connection for the Deployment Server. DAgent, included in HP RDP 3.50 and 3.60, does not multicast to locate the Altiris Deployment Server. The IP address of the Deployment Server and port must be configured during the installation of the DAgent, which is the deployment agent for Windows Vista. The bc2000 and bc2500 factory image contains the installation files for DAgent, which are executed by selecting All Programs > Install Altiris DAgent. Another method to install DAgent is to log onto the blade PC. Then connect to the express share on the Deployment Server and execute the installer Agents\Aclient\dagent.msi. Reduce the Size of the Microsoft DOS and Windows PE PXE Boot Image One way to increase the speed of booting to the Microsoft DOS and Windows PE PXE environment is to reduce the size of PXE boot image by selecting only the NIC drivers required to support the target system during the process of creating the PXE boot images.

1. Microsoft WinPE

bc1500 HP RDP 3.50: Broadcom NetXtreme FEA; Device ID 166e Source Custom HP RDP 3.60: Broadcom 570x 10/100 Integrated Controller Device ID 166e; Source HP bc2000 and bc2500 HP RDP 3.50: requires the Windows XP Broadcom drivers to be downloaded from the HP driver download site then manually added to Deployment Server WinPE PXE image. HP RDP 3.60: Broadcom NetLink Fast Ethernet; Device ID 1713

2. Microsoft DOS

bc1500 HP RDP 3.50 and 3.60: Broadcom NetXtreme Ethernet (for bc1000 and bc1500) bc2000 and bc2500 HP RDP 3.50 and 3.60: Broadcom NetLink; Device ID 1713 Source Broadcom\530a2 Altiris Sidgen is Not Supported for Windows Vista Image Management The Altiris sidgen tool is not supported for Windows Vista image management. Deploying Windows Vista to a target system requires the use of Sysprep to create a unique Security Identifier. Windows Vista Sysprep Disables Built-in Administrator Accounts The Sysprep processing for Windows Vista disables the built-in Administrator account. If a local administrator account is required, one must be created before the image is captured. If the built-in Administrator account is required, use this new Administrator account to execute command net user administrator /active:yes. Reference Microsoft KB: HOW TO: Enable the built-in Administrator account in Windows Vista.

For more information

For more information on the technology mentioned in this document, please refer to the following Web sites:
Hewlett-Packard Software & Driver Downloads HP ProLiant Essentials Rapid Deployment Pack Windows Edition Windows Vista Migration Step-by-Step Guide Windows Automated Installation Kit (Windows AIK) Changes to Functionality in Windows XP Service Pack 2 Microsoft Plug and Play Device Driver Deployment in Windows Vista and Windows Server Longhorn Microsoft User Profile Hive Cleanup Service v1.6d
Preserving OEM Pre-Activation when Re-installing Windows XP Windows Vista Volume Activation Technical Guidance Home Page Knowledge Base 929712: Volume Activation information for Windows Vista Knowledge Base Article 555910: HOW TO: Enable the built-in Administrator account in Windows Vista Knowledge Base Article 314479: How to Add OEM Plug and Play Drivers to Windows XP Microsoft Security Bulletin 890859/MS05-018: Vulnerabilities in Windows Kernel Could Allow Elevation of Privilege and Denial of Service Knowledge Base Article 890859: MS05-018: Vulnerabilities in Windows kernel could allow elevation of privilege and denial of service Knowledge Base Article 886199: You cannot redirect audio to a client computer when you are running a Remote Desktop Connection in Windows XP Knowledge Base Article 928388: 2007 time zone update for Microsoft operating systems Knowledge Base Article 932814: You receive an error message that states a driver was not installed because of a file copy error in Windows Vista Knowledge Base Article 929685: A high definition audio device may no longer work after you resume Windows Vista from sleep or from hibernation and then restart the computer Knowledge Base Article 929913: An error is logged in the Setuperr.log file when you run the "sysprep -reseal" command on a Windows Vista-based computer Knowledge Base Article 930193: Error message when you run the Sysprep command on a Windows Vistabased computer: "A fatal error occurred" Knowledge Base Article 931573: You may be prompted to activate Windows Vista on a computer on which Windows Vista was already activated by a Volume License or OEM installation Knowledge Base Article 895246: The DhcpRequestParams function does not work correctly on a computer that is running Windows XP Service Pack 2 Overview of PNP enumeration and hard disk drive letter assignments in Windows Server 2003 and Windows XP Windows Preinstallation Environment Overview

For more information on HP Rapid Deployment Pack, please visit the HP ProLiant Essentials Rapid Deployment Pack Web page.
20052007 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Linux is a U.S. registered trademark of Linus Torvalds. Microsoft, Windows, Windows server, Windows Vista, and Windows XP are U.S. registered trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. 410920-003, June 2007