1. Manuals
  2. Brands
  3. HP Manuals
  4. Desktop
  5. ProLiant xw2x220c - Blade Workstation
  6. Administrator's manual

HP ProLiant xw2x220c - Blade Workstation Administrator's Manual

Administrator's guide for microsoft windows on hp proliant blade workstations
Hide thumbs Also See for ProLiant xw2x220c - Blade Workstation:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual
Administrator's Guide for Microsoft Windows
on HP ProLiant Blade Workstations
January 2009
Part number: 443069-004
Fourth edition: January 2009

Advertisement

Table of Contents
loading

Related Manuals for HP ProLiant xw2x220c - Blade Workstation

Summary of Contents for HP ProLiant xw2x220c - Blade Workstation

  • Page 1 Administrator’s Guide for Microsoft Windows on HP ProLiant Blade Workstations January 2009 Part number: 443069-004 Fourth edition: January 2009...
  • Page 2 © Copyright 2009 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.

  • Page 3: Table Of Contents

    Contents 1 Introduction Nomenclature........................8 Administrator’s Guide organization ..................10 Blade workstation solution documents ................... 11 Obtaining HP technical support ................... 12 Customer Self Repair ......................12 Ordering Windows recovery media ..................12 Microsoft Windows licensing....................12 2 Blade workstation video subsystem Setting Remote Console Mode .....................
  • Page 4 Windows XP-64 processes ....................49 7 Using Windows Vista on the blade workstation Acquiring Windows Vista ....................50 Installing Windows Vista ..................... 50 7-2-1 Hardware configuration...................... 50 7-2-2 Windows Vista installation steps ..................51 Viewing the Windows Vista desktop..................51 8 Capturing a blade workstation image using HP RDP 9 Deploying a blade workstation image using HP RDP Performing an unattended installation of Windows XP-32 and Windows XP-64...
  • Page 5 12-7-7 Log tab ........................92 12-7-8 Help tab........................92 12-7-9 Saving and printing information in HP Insight Diagnostics..........92 12-7-10 Downloading the latest version of HP Insight Diagnostics ..........93 12-8 ROM-Based Setup Utility ..................... 93 12-9 Power-on Self Test ......................93 12-10 BIOS Serial Console ......................
  • Page 6 Figures Figure 1-1 Simplified HP Blade Workstation Solution documentation hierarchy ..........11 Figure 2-1 Video subsystem architecture and operating modes ................ 14 Figure 2-2 Viewing and setting Remote Console Mode ................... 16 Figure 2-3 Admin Mode ..........................17 Figure 2-4 Setup Mode..........................18 Figure 2-5 User Mode ..........................
  • Page 7 Figure A-2 Broadcom network driver SoftPaq....................98 Figure A-3 SoftPaq file download window..................... 99 Figure A-4 Softpaq startup window ......................99 Figure A-5 Specifying the unpacking location of the SoftPaq files ..............100 Figure A-6 Unpacked SoftPaq files ......................100 Figure A-7 Downloading and initiating installation of Smart Components ............

  • Page 8: Introduction

    1 Introduction For an overview of the HP Blade Workstation Solution, including its architecture, HP recommends that you read the following document—it is the Read-Me-First document for the HP Blade Workstation Solution: HP Blade Workstation Solution Planning Guide This document is available at www.hp.com/support/xw460c_manuals www.hp.com/support/xw2x220c_manuals.
  • Page 9 NOTE: References to “Windows XP” or “Windows Vista” without a numeric suffix apply to both the 32-bit and 64-bit versions of the operating system. The following nomenclature, shown in bold, is used to reference each blade workstation: HP ProLiant xw460c Blade Workstation—xw460c blade workstation HP ProLiant xw2x220c Blade Workstation—xw2x220c blade workstation The phrase “blade workstation”...

  • Page 10: Administrator's Guide Organization

    1-2 Administrator’s Guide organization This document is organized as follows: Chapter 1—Introduction This chapter describes where to find the blade workstation solution documentation, and how to obtain HP technical support. The chapter also describes Windows licensing on blade workstations. Chapter 2—Blade workstation video subsystem This chapter describes the blade workstation video subsystem, covering the two video controllers.

  • Page 11: Blade Workstation Solution Documents

    1-3 Blade workstation solution documents Figure 1-1 provides a simplified documentation hierarchy of the HP Blade Workstation Solution. The HP Blade Workstation Solution Planning Guide is the top-most document in the documentation hierarchy, and, as noted previously, is the recommended document to begin with. At the next level in the hierarchy are the documents describing the following three building blocks of the blade workstation solution: HP ProLiant Blade Workstations HP Remote Graphics Software (HP RGS)

  • Page 12: Obtaining Hp Technical Support

    1-4 Obtaining HP technical support If you encounter an issue that requires technical support, please do the following prior to contacting HP for assistance: Be near your blade workstation • Have available your blade workstation serial number, product number, and model name •...
  • Page 13 Another difference between the Blade PC Editions and the standard Microsoft Windows OS versions is that the Blade PC Editions includes a single Remote Desktop License (RDL). Ensure that you review and adhere to the RDL. For more information, refer to the Microsoft Windows XP Professional Blade PC Edition End User License Agreement (EULA) or the Windows Vista Business Blade PC Edition Licensing Terms, as appropriate.

  • Page 14: Blade Workstation Video Subsystem

    2 Blade workstation video subsystem This chapter describes the blade workstation video subsystem. Because the blade workstation contains two types of video controllers, it is important to understand their functionality and operating modes. The two types of video controllers are: •...
  • Page 15 The key features of the video subsystem are: • The blade workstation boot console is always generated by the ATI video controller. The boot console can be viewed either by connecting a monitor to the video output of the Local I/O Connector, or can be viewed over the network using the iLO 2 Ethernet port, as shown in Figure 2-1.

  • Page 16: Setting Remote Console Mode

    2-1 Setting Remote Console Mode Remote Console Mode can be viewed or changed during the Power-On Self Test (POST) phase. During POST, the boot console is generated by the ATI video controller in all three Remote Console Modes, as shown in Figure 2-1.

  • Page 17: Admin Mode

    2-2 Admin Mode When Remote Console Mode is set to Admin Mode, the ATI video controller first generates the boot console during Power-on Self Test (POST), and then generates the Windows desktop (see Table 2-1 and Figure 2-3). In this mode, the NVIDIA graphics adapter is not visible to Windows, and is not used. Table 2-1 Use of the video controllers in Admin Mode Usage during POST...

  • Page 18: Setup Mode

    2-3 Setup Mode Setup Mode is very similar to Admin Mode—the ATI video controller first generates the boot console and then generates the Windows desktop (see Table 2-2 and Figure 2-4). In Setup Mode, however, the NVIDIA graphics adapter, although it isn’t used, is visible to Windows. Table 2-2 Use of the video controllers in Setup Mode Usage during POST...

  • Page 19: User Mode

    2-4 User Mode When Remote Console Mode is set to User Mode, the boot console is, as usual, generated by the ATI video controller. Following the booting of Windows, the NVIDIA graphics adapter generates the Windows desktop (see Table 2-3 and Figure 2-5). Table 2-3 Use of the video controllers in User Mode Usage during POST...

  • Page 20: Summary Of Remote Console Modes

    2-5 Summary of Remote Console Modes Table 2-4 summarizes the use of the video controllers in the three Remote Console Modes—Admin Mode, Setup Mode, and User Mode. The video controller used during booting is highlighted in green, showing that the ATI video controller is used in all three Remote Console Modes to display the boot console during Power-on Self Test (POST).

  • Page 21: Installing, Powering On, Booting, And Validating The Blade Workstation Solution

    3 Installing, powering on, booting, and validating the blade workstation solution This chapter describes the process to install, power on, boot and validate the HP Blade Workstation Solution. A building block approach is followed, starting with a single blade workstation and a single client computer. After validating their operation, other blade workstations and client computers can be integrated into the solution.

  • Page 22: Setting Up The Client Computer

    3-1 Setting up the client computer If you are using one of the client computers in the HP Blade Workstation Client series, refer to the documentation specific to your client computer, as described in Section 1-3, “Blade workstation solution documents.” RGS is factory-installed on these client computers.

  • Page 23: Configuring The Blade Workstation Hardware

    3-2-2 Configuring the blade workstation hardware The blade workstation hardware listed below is configured before installing the blade in the enclosure. Unless otherwise noted, the hardware listed below can be configured on both the xw460c and xw2x220c blade workstations. IMPORTANT: Refer to the document Hardware and Software Supported by HP ProLiant Blade Workstations for more details on hardware configuration, as well as the latest information on supported hardware and software.

  • Page 24: Connecting Media To The Blade Workstation

    3-2-3 Connecting media to the blade workstation The blade workstation architecture supports three primary methods of connecting media to the blade (such as a CD/DVD drive). Figure 3-2 shows media connection in Admin Mode. Figure 3-2 Connecting media to the blade workstation NVIDIA graphics NVIDIA Quadro adapter is not visible...

  • Page 25: Powering On The Blade Workstation

    3-2-4 Powering on the blade workstation This section describes how to power on the blade workstation using the factory-installed Microsoft Windows XP- 32 operating system. NOTE: The blade power on process can be performed using either the Local I/O Cable or iLO 2 Remote Console.

  • Page 26: Blade Workstation Sleep States

    3-2-5 Blade workstation sleep states The blade workstation supports two sleep states: S0 (fully on) and S5 (off but connected to power). No other power management states (such as Hibernate or Standby) should be used. From sleep state S5, Wake-on-LAN (WOL) is supported by both NIC1 and NIC2.

  • Page 27: Verifying Networking

    3-4 Verifying networking The next step is to verify that the blade workstation is accessible over the network using NIC1, NIC2, and iLO 2. By default, the NIC1, NIC2, and iLO 2 IP addresses are set by DHCP. Therefore, ensure that the blade workstation can connect to a DHCP server.

  • Page 28: Ilo 2 Network Verification

    3-4-2 iLO 2 network verification To validate iLO 2 network access, you first need to know the iLO 2 IP address. There are several ways to determine this: Reboot the blade. During the reboot, the boot console displays the iLO 2 IP address, as shown in Figure 3-6 •...

  • Page 29: Installing, Configuring, And Verifying Rgs

    3-5 Installing, configuring, and verifying RGS 3-5-1 Installing RGS RGS (specifically, the RGS Sender) is not factory-installed on the blade workstation. RGS needs to be obtained from HP, and installed on your blade workstation. A paper License Agreement Certificate is shipped with your blade workstation that allows you to download RGS 5.1.5 at no cost from HP—see the certificate for downloading instructions.

  • Page 30: Figure 3-9 Nic Ip Addresses

    Double-click each LAN icon and the Support tab, which displays the IP address of each NIC (see Figure 3-9). While this provides the IP address of each NIC, it does not indicate which NIC is considered the “first” NIC. Figure 3-9 NIC IP addresses To determine which NIC is the first NIC, click Advanced >...

  • Page 31: Setting User Mode

    3-5-3 Setting User Mode Before verifying RGS operation, set Remote Console Mode to User Mode. This is necessary because the RGS Sender can operate only with the NVIDIA graphics adapter (which is active in User Mode). To set Remote Console Mode to User Mode, reboot the blade workstation, and select User Mode as described in Section 2-1, “Setting Remote Console Mode.”...

  • Page 32: Validating The Solution

    Each installation method has advantages and limitations: Local installation using USB devices connected to the Local I/O Cable—This is generally the most reliable • method, particularly for installations requiring multiple media. However, this method requires that you be physically present at the blade, which can be difficult in data centers not designed to accommodate local personnel.
  • Page 33 Link aggregation (trunking)—This team type provides redundancy and increased network bandwidth by using multiple network adapters as a single virtual adapter. The link partner (usually a switch) for these network adapters must include support for this type of team. There are two different types of link aggregation teams supported by BACS: 802.3ad (using Link Aggregation Control Protocol, or LACP)—Multiple network adapters are teamed •...

  • Page 34: Creating A Custom Windows Xp-32 Image 34

    4 Creating a custom Windows XP-32 image This chapter describes how to create a custom Windows XP Professional SP2 image for the blade workstation. First, as reference, the components included in the factory-installed Windows XP-32 operating system are listed. In most cases, you’ll want to include these components in your custom Windows XP-32 image. 4-1 Components in the factory-installed Windows XP-32 image The Windows XP-32 operating system that is factory-installed on your blade workstation contains a number of drivers and agents.

  • Page 35: Creating A Custom Windows Xp-32 Image

    Modified local security policy—The network access sharing and security model for local accounts is set to • Classic, meaning, local users authenticate as themselves. This setting is necessary to permit RGS connections when the blade workstation is not part of a Microsoft Windows domain. The Windows power options are set to never turn off any component, and never sleep or hibernate.

  • Page 36: Optional Software Components

    4-2-2 Optional software components The following software components are optional, and can be downloaded from the blade workstation software and drivers website: CD containing System Management Homepage (SMH)—SMH allows the status of the blade to be remotely • monitored (see Section 12-4, “System Management Homepage“).

  • Page 37: Figure 4-2 Mass Storage Setup Screen

    When prompted, press the S key (see Figure 4-2) to indicate the availability of a diskette with the E200i SAS drive. Press Enter to continue. Figure 4-2 Mass storage setup screen When prompted for the driver diskette (see Figure 4-3), insert the diskette containing the HP Smart Array E200i SAS controller drivers, and press Enter to continue.

  • Page 38: Figure 4-4 Scsi Adapter Selection Screen

    Select the Windows 2000 Driver for Smart Array E200 (see Figure 4-4). Press Enter to install the driver. Figure 4-4 SCSI adapter selection screen When prompted, press Enter to begin the Windows XP installation (see Figure 4-5). Figure 4-5 Windows XP Pro setup screen Creating a custom Windows XP-32 image 38...

  • Page 39: Figure 4-6 Windows Xp Eula

    When prompted, select the manual installation option. When prompted, press F8 to accept the Microsoft End-User License Agreement (see Figure 4-6). Figure 4-6 Windows XP EULA Partition the hard drive as desired. Install Windows XP Pro in a fresh partition. Creating a custom Windows XP-32 image 39...

  • Page 40: Figure 4-7 Windows Setup Manual Installation Screen

    Enter C to proceed with manual installation (see Figure 4-7). Figure 4-7 Windows setup manual installation screen If the Windows setup GUI prompts you for unsigned drivers, click Yes to install drivers that have not passed Windows Logo testing (see Figure 4-8). Figure 4-8 Windows logo testing screen Creating a custom Windows XP-32 image 40...

  • Page 41: Figure 4-9 Product Key Screen

    Customize Windows XP Pro by answering the Microsoft Out Of Box Experience (OOBE) questions, such as the time zone and computer name. Enter the 25-character product key that identifies your copy of Windows XP Professional (see Figure 4-9). Figure 4-9 Product key screen Set the regional and language options.

  • Page 42: Figure 4-10 Computer Name And Administrator Password Screen

    From the Computer Name and Administrator Password screen (see Figure 4-10), enter an Administrator password (required for the blade workstation). Both RGS and Windows Remote Desktop Connection require access to a password-protected account. The password enables most of the remaining system configuration and application installation tasks to be performed over the network using RGS or Remote Desktop Connection.

  • Page 43: Figure 4-11 Installation Of Snmp

    If you are installing the management agents (recommended), two additional components are required, which must be installed in the following order: SNMP (Simple Network Management Protocol)—This component is installed as follows: Open the Windows Components Wizard (see Figure 4-11). Select Management and Monitoring •...

  • Page 44: Figure 4-12 Snmp Service Properties

    Next verify that SNMP Service in the Windows Component Services box shows “Started”. Right • click SNMP Service, select Properties, and then click the Security tab. Ensure that the properties appear as shown in Figure 4-12. If not, modify the Accepted community names as shown. Other community names may be used.

  • Page 45: Configuring The Operating System

    Windows File and Print Sharing (required for Rapid Deployment Pack)—“File and Printer Sharing” • program exception • HP Remote Graphics Software—Add “C:\Program Files\Hewlett-Packard\ Remote Graphics Sender\rgsender.exe” program exception System Management Homepage (SMH)—Add the port exceptions listed in Table 4-1. •...

  • Page 46: Table 4-3 Hp Rdp Port Exceptions

    If HP Rapid Deployment Pack (HP RDP) is used, enable the “File and Print Sharing” program exception. • Also add the port exceptions listed in Table 4-3 to enable HP RDP access to the blade workstation. Table 4-3 HP RDP port exceptions Port Type Description...

  • Page 47: Verifying The Network Connections

    4-2-5 Verifying the network connections Verify network connections to the blade workstation as described in Section 3-4, “Verifying networking.” 4-2-6 Installing and verifying RGS Install and verify RGS as described in Section 3-5, “Installing and verifying RGS.” 4-2-7 Installing the applications It is recommended that you install the following applications before installing user applications: •...

  • Page 48: Restoring Windows

    5 Restoring Windows XP-32 This chapter describes how to restore Windows XP-32 using the RestorePlus! CD and the Windows XP operating system CD. The restored operating system differs slightly from the factory-installed operating system. For example, several applications are not included on the RestorePlus! CD because of space limitations. The restore process repartitions and reformats the blade workstation hard drive.

  • Page 49: Using Windows Xp-64 On The Blade Workstation

    6 Using Windows XP-64 on the blade workstation While Windows XP-64 is supported on the blade workstation, this OS is not available factory-installed. Windows XP-64 needs to be acquired, installed, and configured by your IT department. Because so many of the Windows XP-64 processes are similar to the processes for Windows XP-32 (as described in Chapters 4 and 5), this chapter focuses on those processes that are different or unique for Windows XP-64.

  • Page 50: Using Windows Vista On The Blade Workstation

    7 Using Windows Vista on the blade workstation IMPORTANT: The Windows Vista-32 and Windows Vista-64 recovery media is available to allow you to begin evaluating Windows Vista in your environment. It is important to understand, however, that the RGS Sender is not yet supported on Windows Vista-32 and Windows Vista-64.

  • Page 51: Windows Vista Installation Steps

    7-2-2 Windows Vista installation steps Perform the following steps to install Windows Vista-32 or Windows Vista-64 on the blade workstation: Insert the Windows Vista RestorePlus! DVD into the CD/DVD drive. Boot the blade workstation from the DVD. When the GUI Language selection screen appears, select a language (for the installation process, not for localization of the operating system), and click Next.

  • Page 52: Capturing A Blade Workstation Image Using Hp Rdp

    8 Capturing a blade workstation image using HP RDP HP Rapid Deployment Pack (HP RDP) can be used to capture the OS image of the blade workstation for both Windows XP-32 and Windows XP-64. This chapter assumes you are familiar with HP RDP—for detailed information on HP RDP, visit www.hp.com/go/rdp.
  • Page 53 To capture an OS image and deploy it to multiple other computers, the Sysprep tool needs to be run to set a new SID and to apply new system settings, such as the computer name. If you plan to use Altiris Deployment Server to run Sysprep, continue with STEP 2 below.
  • Page 54 STEP 5: Run Sysprep manually To run Sysprep manually, refer to the article How to use the Sysprep tool to automate successful deployment of Windows XP, available at www.microsoft.com/kb/302577. If you run Sysprep manually, you’ll need to run it, shut down the computer, and boot directly to PXE manually (F12 on POST) to run the image process without booting to the OS first.

  • Page 55: Deploying A Blade Workstation Image Using Hp Rdp

    9 Deploying a blade workstation image using HP RDP HP Rapid Deployment Pack (HP RDP) can be used to deploy an OS image to the blade workstation for both Windows XP-32 and Windows XP-64. This chapter assumes you are familiar with HP RDP—for detailed information on HP RDP, visit www.hp.com/go/rdp.
  • Page 56 STEP 2: If required, configure the Deployment Server to run Sysprep Depending on your HP RDP configuration, this step may have already been completed. To configure the Altiris Deployment Server to run Sysprep, refer to the Deployment Solution documentation available from Altiris at www.altiris.com.
  • Page 57 STEP 6: Create a new job (that doesn’t use Altiris to run Sysprep) to deploy the image Perform the following steps to create a new job that deploys the OS; but doesn’t use Altiris to run Sysprep: Under the jobs pane, right-click in the white area and select “New Job”. Enter a name for the job that is unique.

  • Page 58: Assumptions

    10 Performing an unattended installation of Windows XP-32 and Windows XP-64 This chapter provides an overview of the steps to perform an unattended installation of Windows XP-32 and Windows XP-64. This chapter does not detail all steps needed to create and configure an unattended installation environment;...

  • Page 59: Unattended Installation Procedure

    10-2 Unattended installation procedure This section describes the steps to perform an unattended installation of Windows XP-32 and Windows XP-64. Create and update the remote install distribution share. In the distribution share, create a directory structure to store the OS installation files as well as the HP- specific drivers and software for the blade workstation.

  • Page 60: Figure 10-2 Softpaq That Provides Support Files For Unattended Installation Of Windows

    In this step, the software and drivers required for unattended installation are downloaded. Refer to “APPENDIX A: Downloading and installing SoftPaqs and Smart Components,” for information on downloading and unpacking SoftPaqs and Smart Components. Download the SoftPaq shown in Figure 10-2—This SoftPaq contains the “conrep” folder and the files used to change Remote Console Mode.

  • Page 61: Table 10-2 Rgs And Utilities

    Copy RGS and additional utilities in various distribution sub-folders Table 10-2 RGS and utilities Windows XP Pro SP2 Windows XP Pro x64 example directory example directory ROOT : $OEM$\$1\HP_Install\ ROOT : $OEM$\$1\HP_Install\... conrep conrep Conrep (BIOS setting utility) unsignok unsignok unsignOK Firewall Firewall 'punching script'...
  • Page 62 Next, add blade workstation-specific entries to the different sections of the unattended answer file, either unattend.txt or ristndrd.sif (for RIS installation). The following entries are based on the example directories created in step 2, and will need to be adapted to your configuration if it differs from the directories shown in step 2.
  • Page 63 Windows XP Pro x64 • Add to the [Unattended] section Plug and Play driver location: OemPNPDriversPath="\\%SERVERNAME%\RemInst\%INSTALLPATH%\$OEM$\text mode;Drivers\HP_NULL_IPMI;Drivers\HP_SmartArray_E200i_SAS;Drivers\ Intel_chipset;Drivers\ " IMPORTANT: For both Windows XP-32 and Windows XP-64, the path for the NVIDIA driver is intentionally omitted. Because the blade workstation contains two video controllers, the workstation will make the NVIDIA driver primary during the install and the screens will go black if Remote Console Mode is in Setup Mode.

  • Page 64: Performing An Unattended Installation Of Windows Xp-32 And Windows Xp

    Add to the [WindowsFirewall] section • [WindowsFirewall] Profiles = WindowsFirewall.TurnOffFirewall [WindowsFirewall.TurnOffFirewall] Mode = 0 In the above firewall example, the Windows firewall is disabled (refer to Windows documentation on firewall settings). In practice, it is not recommended to disable the Windows firewall unless another firewall is in use.
  • Page 65 Example Windows XP Pro GuiRunOnce script The GuiRunOnce script installs the needed software and drivers in the proper order, and runs after the first boot. A sample version of this script is included in the “HP Blade Workstation Unattended install support Files” downloaded earlier in step 3a.
  • Page 66 Example Windows XP Pro 64 GuiRunOnce script rem @echo off title HP Driver and Software Install Script rem Starting XPUnsignOK2.exe to automatically push accept button for Unsigned ATI driver echo. echo Starting XPUnsignOK2.exe start %systemdrive%\HP_Install\unsignok\XPUnsignOK2.exe echo XPUnsignOK2.exe Started rem Complete XPUnsignOK2.exe to automatically push accept button for Unsigned ATI driver rem Starting ATI driver install echo.
  • Page 67 Example firewall punch holes script (firewall.cmd) netsh firewall add portopening TCP 2381 "HP SMH Secure Web Server (TCP 2381)" netsh firewall add portopening TCP 5988 "WBEM/WMI Mapper (TCP 5988)" netsh firewall add portopening TCP 5989 "WBEM/WMI Mapper Secure (TCP 5989)" netsh firewall add portopening TCP 22 "SSH port (TCP 22)"...

  • Page 68: User Information

    11 User Information 11-1 Introduction This chapter is intended for the user of the HP Blade Workstation Solution and describes how to interact with the blade workstation from the client computer. The following topics are included in this chapter: Powering on the blade workstation client •...

  • Page 69: Connecting From The Client To The Blade

    11-4 Connecting from the client to the blade RGS connects the client computer to the blade workstation. Under typical circumstances, connecting to your blade from the client computer is as simple as clicking the Connect button, or entering an IP address and clicking Connect.

  • Page 70: Using A Local Directory File

    11-4-2 Using a local directory file Setting up the Enterprise Directory may not be practical for smaller installations. Instead, it may be more efficient to use a directory file that resides on the client. The directory file contains a list of systems assigned to authorized users on that client.

  • Page 71: Sending Ctrl+Alt+Delete To The Blade Workstation

    Variation: If your organization has implemented Single Sign-on, the only authentication prompt (username and password) displayed is from the RGS Receiver on the client. After authentication by the RGS Receiver, the blade Windows desktop of the blade is displayed, logged-in and ready to use. 11-5 Sending Ctrl+Alt+Delete to the blade workstation Microsoft Windows requires that you enter Ctrl+Alt+Delete to log in, to access the Windows Task Manager, or to lock the desktop.

  • Page 72: Moving Desktop Windows Between Monitors

    11-7 Moving desktop windows between monitors RGS allows you to move desktop windows to any part of the client screen space. If the desktop windows sent from the blade workstation have borders, click the top border and drag the desktop to the desired location. If the desktop windows do not have borders, perform the following steps to move a window: Enter RGS Setup Mode.

  • Page 73: Supported Usb Devices

    11-10 Supported USB devices RGS supports remote USB, which allows USB devices connected to the client computer to be remotely attached to the blade workstation. Remote USB is described in the HP RGS User Guide available at www.hp.com/support/rgs_manuals. This document also lists the client-attached USB devices which can be attached to the RGS Sender (in this case, the blade workstation).

  • Page 74: Disconnecting The Client From The Blade Workstations

    11-13 Disconnecting the client from the blade workstations To disconnect a client from all blades, open the RGS Control Panel as described in Section 11-3 (Setup Mode + M), and click the Disconnect button. To disconnect a client from an individual blade, open the Remote Display Window Toolbar (Setup Mode + H), and click the Disconnect button shown below.

  • Page 75: Managing The Blade Workstation

    12 Managing the blade workstation This chapter describes how to manage blade workstations, and includes information on the following topics: Onboard Administrator • Integrated Lights-Out 2 (iLO 2) • • Remote Desktop Connection System Management Homepage • HP System Insight Manager (HP SIM) •...

  • Page 76: Onboard Administrator

    12-1 Onboard Administrator The Onboard Administrator (OA) allows you to use a web browser to remotely log into OA and obtain detailed information about the contents of each c7000 enclosure (see Figure 12-1). Figure 12-1 Enclosure front and rear views Using Figure 12-1, you can determine the following: A blade workstation is installed in each device bay.

  • Page 77: Figure 12-2 Detailed Blade Information

    The OA also provides detailed information about each blade in the enclosure. In Figure 12-2, OA is providing status information for blade 9. Figure 12-2 Detailed blade information As shown in Figure 12-3, OA enables remote management of the blades, including power management. Figure 12-3 Blade power management Managing the blade workstation 77...

  • Page 78: Integrated Lights-Out 2 (Ilo 2)

    NOTE: The iLO 2 management processor also supports blade power management. However, using iLO 2 power management requires a separate login to iLO 2 on each blade. With OA, you can manage power for all blades from a single OA login session. All OA modules in the rack are linked together with Ethernet cables, allowing administrators to view and control the blades in every enclosure by logging into the OA module in any enclosure.

  • Page 79: Ilo 2 Remote Console

    12-2-2 iLO 2 Remote Console The iLO 2 Remote Console allows you to remotely view and interact with the boot console and the Windows desktop (in Admin Mode and Setup Mode). To view the Remote Console types, select the Remote Console tab (see Figure 12-5).

  • Page 80: Figure 12-6 Boot Console

    In Figure 12-6, the Integrated Remote Console is displaying the boot console. This enables you to remotely interact with the boot process in the same manner as when a monitor, keyboard, and mouse are connected directly to the blade. Figure 12-6 Boot console Managing the blade workstation 80...

  • Page 81: Viewing The Windows Desktop

    12-2-3 Viewing the Windows desktop If Remote Console Mode is set to Admin Mode or Setup Mode, the Windows desktop is generated by the ATI video controller and is viewable through the iLO 2 Remote Console (see Figure 12-7). Figure 12-7 Windows desktop During normal use, Remote Console Mode is set to User Mode, which means that the Windows desktop is generated by the NVIDIA graphics adapter.

  • Page 82: Ilo 2 Virtual Media

    12-2-4 iLO 2 virtual media The iLO 2 Virtual Media screen allows you to connect a floppy drive, USB key, or CD/DVD drive to the blade workstation from your local PC. To create this connection, perform the following steps: Click the iLO 2 Virtual Devices tab. Click the Virtual Media link.

  • Page 83: Figure 12-10 Pc Files Accessible From The Blade Workstation Windows Desktop

    To verify that the virtual media is connected to the blade, you can use RGS to run Windows Explorer on the blade. Figure 12-10 shows that the USB key files are now accessible from the blade workstation. Note that the E: drive on the PC is mapped to the D: drive on the blade workstation.

  • Page 84: Remote Desktop Connection

    12-3 Remote Desktop Connection Microsoft Remote Desktop Connection (RDC) provides a convenient way to remotely administer the blade workstation because it allows the administrator to use the familiar Windows interface. IMPORTANT: RDC and RGS are not interoperable. If an RDC connection is made while an RGS session is established, the blade RGS Sender disconnects and the RGS session terminates.

  • Page 85: Figure 12-14 Rdc Windows Desktop

    Click Connect. The Remote Desktop window appears with the Log On to Microsoft Windows screen. After logging in, the Windows desktop is displayed (Figure 12-14 shows the Windows desktop, reduced in size). Figure 12-14 RDC Windows desktop Managing the blade workstation 85...

  • Page 86: System Management Homepage

    12-4 System Management Homepage This section describes how to view the blade System Management Homepage (SMH). SMH allow you to view information generated by the four blade management agents—NIC, server, storage, and foundation. To access SMH, point your browser to either of the blade IP addresses (NIC1 or NIC 2) using HTTPS and port number 2381.

  • Page 87: Local Access To Smh

    12-4-1 Local access to SMH If you have a monitor, keyboard, and mouse connected to the Local I/O Cable, you can view SMH using either of these URLs: https://127.0.0.1:2381 or https://localhost:2381. Or, you can access SMH from the Start menu by clicking Start >...

  • Page 88: Hp Rapid Deployment Pack

    12-6 HP Rapid Deployment Pack 12-6-1 Introduction The HP ProLiant Essentials Rapid Deployment Pack (HP RDP) is a software deployment solution that facilitates the installation, configuration, and deployment of high volumes of blade workstations through either a GUI-based or web-based console. HP RDP is designed to automate repetitive tasks such as configuring and deploying operating system images, configuring network switches, and configuring BIOS settings.

  • Page 89: Use Rip-N-Replace And Virtual Bay Features To Replace Failed Systems

    Windows XP uses Microsoft Windows Activation technologies—Microsoft Windows Activation requires • either that users activate their Windows license on each machine at first boot or that the administrator take specific steps during image creation to ensure that activation is not needed. Microsoft Windows Activation is not required on the server blade.

  • Page 90: Hp Insight Diagnostics

    12-7 HP Insight Diagnostics The HP Insight Diagnostics utility enables you to perform and view critical computer hardware and software configuration information from various sources. This utility enables you to run diagnostics and view the hardware configuration of the system. NOTE: As noted below, the HP Insight Diagnostics are available on the Documentation and Diagnostics CD that is included with your blade workstation.

  • Page 91: Survey Tab

    12-7-4 Survey tab The Survey tab displays important system configuration information. In the View section on the left side of the screen, you can select the Summary view to see limited configuration data or select the Advanced view to see all the data in the selected category.

  • Page 92: Status Tab

    12-7-6 Status tab The Status tab displays the status of selected tests. The type of test executed (Quick, Complete, or Custom) is also displayed. The main progress bar displays the percent complete of the current set of tests. While testing is in progress, a Cancel Testing button is available if you want to cancel the test.

  • Page 93: Rom-Based Setup Utility

    12-7-10 Downloading the latest version of HP Insight Diagnostics Go to www.hp.com. Click the Support & Drivers link. Select the Download driver and software radio button. Enter your product number (for example, “xw460c”) in the text box, and press the Enter key. Select your operating system.

  • Page 94: Troubleshooting The Blade Workstation Solution

    13 Troubleshooting the blade workstation solution This chapter describes several possible problems you might encounter during installation and operation of the blade workstation solution. Included with each problem is the likely cause, and the suggested solution. For additional troubleshooting information, see: Section 12-9, “Power-on Self Test”...

  • Page 95: Troubleshooting Rgs Problems

    13-3 Troubleshooting RGS problems Also see the Chapter “Troubleshooting” in the HP Remote Graphics User’s Guide for additional information on possible RGS problems and suggested solutions. Table 13-3 Troubleshooting RGS problems Problem Cause Suggestions Unable to connect using RGS Receiver A connection cannot be established The proper DNS suffixes for your On the client, ensure that the...

  • Page 96: Troubleshooting Windows Problems

    13-4 Troubleshooting Windows problems Table 13-4 Troubleshooting Windows problems Problem Cause Suggestions RAM discrepancies Blade workstation configurations A portion of the total RAM will be None using 4 GB of RAM report only utilized by various system devices, 3,456 MB during the system BIOS most notably the graphics card.

  • Page 97: Appendix A: Downloading And Installing Softpaqs And Smart Components

    APPENDIX A: Downloading and installing SoftPaqs and Smart Components This appendix describes how to find, download, and unpack SoftPaqs and Smart Components for the blade workstations. IMPORTANT: HP supports two types of software packages for downloadable software and drivers: SoftPaqs Smart Components Until recently, blade workstation downloads were based on SoftPaqs.

  • Page 98: Figure A-1 Operating System Selection Options

    Select your operating system (see Figure A-1). For this example, Microsoft Windows XP Professional is selected. Figure A-1 Operating system selection options On the next page, scroll down to the driver of interest, and click the Download button. The Broadcom network driver is used in this example.

  • Page 99: Figure A-3 Softpaq File Download Window

    In the file download window shown in Figure A-3, select Save, and save the SoftPaq file sp35518.exe to a temporary location on the blade workstation. Figure A-3 SoftPaq file download window           When the download window indicates the download is complete, click Run. This brings up the SoftPaq start window shown in Figure A-4.

  • Page 100: Figure A-5 Specifying The Unpacking Location Of The Softpaq Files

    For this particular SoftPaq, you are given the option of unpacking the SoftPaq files to a temporary location (followed by their post-installation removal) or to a user-settable location (which leaves the files intact). In Figure A-5, the user-settable location option is selected, and the default location C:\swsetup\SP35518 is used.

  • Page 101: Downloading And Installing Smart Components

    A-2 Downloading and installing Smart Components This section discusses the downloading and installation of Smart Components. Smart Components can either be installed using their built-in graphical user interface or they can be installed from the command line. The command line installation capability permits the use of scripted installs. Smart Component have the file naming convention “cpXXXXXX.exe”, where: “cpXXXXXX”...

  • Page 102: Figure A-8 Initial Smart Component Installation Gui

    Next, a screen similar to that shown in Figure A-8 will be displayed. Click Install to initiate a default installation, or click Extract to extract the files in the Smart Component. Figure A-8 Initial Smart Component installation GUI After clicking Install, a window similar to that shown in Figure A-9 will appear. This screen indicates if the update is needed on this particular computer, and if the Smart Component is supported on this computer.

  • Page 103: A-2-2 Command Line Installation Of Smart Components

    A-2-2 Command line installation of Smart Components Once a Smart Component has been downloaded, it can be installed from the command line. The general command line syntax for single-component installation is: cpXXXXXX.exe [/h[elp]] [/?] [/s[ilent]] [/f[orce]] [/r[eboot]] All arguments and information enclosed in brackets are optional. If no command line arguments are passed on the command line, the installation GUI appears, as shown in Figure A-8.
  • Page 104 Return codes for components When each Smart Component has finished running, the component reports a return code to the operating system or the calling application. These return codes communicate the status of the component installation. You can also use the return codes in a script to control the execution of the script and determine any branching that is required.

  • Page 105: Index

    Index RBSU, 93 RDC, 75, 84 RDP, 88 re-attaching disconnected sessions, accessing blade workstation desktop, HP Blade Workstation Solution, 8 HP Insight Diagnostics, 90; Remote Console Mode: setting, 16 accessing HP Insight Diagnostics, 90 downloading, 93; saving, 92 Remote Console, iLO 2, 79, 81 accessing the SMH, 87 HP RGS: changing behavior, 68;...

This manual is also suitable for:

Xw460c - proliant - blade workstation

Table of Contents