HP Integrity Servers with Microsoft® Windows Server™ 2003 Smart Setup Guide HP Part Number: 5992-0964 Published: October 2007
© Copyright 2007 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About This Document.......................................................................................................11 Intended Audience................................................................................................................................11 New and Changed Information in This Edition...................................................................................11 Document Organization.......................................................................
Run Windows Setup........................................................................................................................42 Specify server settings.....................................................................................................................42 Installing from PXE...............................................................................................................................43 Reinstalling from a headless console............................................
4 Performing hot-plug operations...................................................................................71 Before you begin...................................................................................................................................71 Adding a PCI card................................................................................................................................72 Hardware interface for all HP Integrity servers except Superdome................................
List of Figures 1-1 1-2 1-3 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 2-11 2-12 2-13 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 3-13 B-1 Headless console configurations...................................................................................................22 GUI console configuration............................................................................................................24 PXE/RIS configuration.............................................................................
List of Tables 1-1 1-2 1-3 1-4 2-1 4-1 B-1 C-1 Installation matrix.........................................................................................................................17 Locating the Microsoft COA.........................................................................................................19 Graphics support on server models..............................................................................................24 EFI device mapping fields................................
About This Document This document describes how to install and configure the operating system and HP software on HP Integrity servers running Windows Server 2003. The document printing date and part number indicate the document’s current edition. The printing date changes when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The document part number changes when extensive changes are made.
WARNING CAUTION IMPORTANT NOTE KeyCap Computer output User input Command Ctrl+x [] {} ... | A warning calls attention to important information that if not understood or followed will result in personal injury or nonrecoverable system problems. A caution calls attention to important information that if not understood or followed will result in data loss, data corruption, or damage to hardware or software.
Publishing History The publishing history below identifies the edition dates of this manual. Updates are made to this publication on an unscheduled, as needed, basis. The updates will consist of a complete replacement manual and pertinent online or CD documentation. Manufacturing Part Number Supported Operating Systems Supported SmartSetup Supported Products Version (Servers) Publication Date 5992-0926 Microsoft Windows Server 2003 for Itanium-based Systems, 64–bit Version 5.
1 Preparing for the installation Installing Microsoft® Windows® Server 2003 for Itanium®-based systems on an HP Integrity server involves preparing the hardware for operating system (OS) installation, loading the OS, and updating the system with the latest OS patches. This chapter helps you plan the installation based on the server model, the OS edition, the source of the OS media, and your network environment. Subsequent chapters guide you through the installation process.
the latest firmware, drivers, and Microsoft patches and fixes (QFEs) available in the latest HP Integrity Essentials Foundation Pack or from the HP Integrity servers support website: http://www.hp.
3. Verify storage compatibility by reviewing the HP Integrity Server-Storage support matrices at http://www.hp.com/products1/serverconnectivity/support_matrices.html. This list is not exhaustive because storage vendors can support more configurations than those indicated at the site. As a general rule, check with your storage vendor and an HP sales representative for a definitive statement on server and storage compatibility.
Choosing the Installation media The HP Integrity Essentials Foundation Pack for Windows includes the HP Smart Setup media. You can use the HP Smart Setup media both before and after you install the OS. • • Before installing the OS, boot the server with the Smart Setup media in the CD/DVD drive. The server boots to the EFI-Based Setup Utility (EBSU). EBSU provides an easy-to-use interface for offline setup and configuration tasks, such as creating hard disk partitions and updating the firmware.
Table 1-2 Locating the Microsoft COA Integrity Server Location rx1620 The COA is on the underside of the pullout strip located near the power switch, as shown here (server is upside down in the image): rx2620 The COA is on a pullout strip located on the front of the system, adjacent to the hard drives, as shown here: rx2660 The COA is located on the left side panel, in the middle, as shown here: Locating the Microsoft Certificate of Authenticity 19
Table 1-2 Locating the Microsoft COA (continued) 20 Integrity Server Location rx3600 The COA is located on the left side panel, as shown here: rx4640 The COA is located on the left side panel, as shown here: rx6600 The COA is located on the left side panel. It as shown here: BL860c and BL870c The COA is located on the left side panel.
Table 1-2 Locating the Microsoft COA (continued) Integrity Server Location rx7620 and rx7640 The COA is located on the front of the system, above the light panel, next to the UUID label, as shown in the first illustration that follows. Additional COAs are shown in the second illustration. rx8620 and rx8640 The COA is located in the front of the system, at the bottom, near the power supply as shown in the first illustration that follows.
Setting up a console If you are installing locally, you must set up your server with either a headless console or a GUI console. Set up a headless console A headless console is a PC running terminal emulation software such as PuTTY (available on the Smart Setup media or from the web) or HyperTerminal, that connects to the server through its management processor (MP) serial port or LAN port.
2. Install PuTTY on the client PC and specify these port settings: • Bits per second: 9600 • Data bits: 8 • Parity: none • Stop bits: 1 • Flow control: Xon/Xoff 3. 4. 5. 6. 7. Use the Keyboard Configuration Panel to map the backspace key to Control + H. Boot the server. Run PuTTY and press Enter. The MP login prompt appears. Enter your user name and password, and the MP command prompt appears. Enter the CO command to access the headless console.
Figure 1-2 GUI console configuration A GUI console provides complete access to all the installation and administration tasks that you can perform on the server. You can use the GUI console to prepare the server for installation, install the OS, and check server status after installation. On servers configured with an internal graphics card, you can connect a monitor, keyboard, and mouse directly to the appropriate ports.
6. 7. Select Select Output Console. Select the graphics card PCI device and press Enter. The video display is now directed to the GUI console. Set up an Integrated Remote Console (rx2660, rx3600, rx6600, BL860c, and BL870c only) The Integrated Remote Console (IRC) lets you use Windows clients running Internet Explorer to remotely view and manage HP Integrity servers featuring the iLO 2 management processor. This functionality is supported on rx2660, rx3600, rx6600, BL860c, and BL870c servers only.
Booting from the iLO 2 MP CD/DVD enables you to upgrade the host system ROM, upgrade device drivers, deploy an OS from network drives, and perform disaster recovery of failed operating systems, among other tasks. The iLO 2 MP device uses a client/server model to perform the vMedia functions. The iLO 2 MP device streams the vMedia data across a live network connection between the remote management console and the host server. The vMedia Java™ applet provides data to the iLO 2 MP as required.
Figure 1-3 PXE/RIS configuration NOTE: When you perform a PXE/RIS headless installation, note the following: • Headless installations using PXE/RIS are not supported with Windows Server 2003, Datacenter Edition. Use the HP Reinstallation media instead. • Do not connect the RIS server to the Integrity server using your intranet during initial Windows OS installation. Set up a small private network, populated with the RIS server, a hub, and the system LAN NIC of the HP Integrity server.
• • Install the RIS component on the RIS server. Run the RIS Setup Wizard. See Also For detailed descriptions of the concepts, tasks, best practices, and troubleshooting tips for setting up a RIS server, see the Microsoft Windows Server 2003 Technical Reference website: http://www.microsoft.com/windowsserver2003/proddoc/default.mspx. Install RIS You can install RIS either using the Control Panel or through an unattended Setup answer file.
appropriate for their account privileges. By default, when an operating system image is added to a RIS server, the image is available to all users serviced by that RIS server. To configure settings for new clients for RIS, complete the following steps: 1. 2. 3. 4. 5. 6. 7. Open Active Directory Users and Computers.
• • be created. Help desk or administrators can use this option to preinstall a client computer for someone else within the enterprise. Restart a Previous Setup Attempt—This option automatically restarts the operating system installation process when an installation attempt fails before completion. This option does not copy files from where the previous installation attempt failed; however, you are not required to answer any questions answered within the CIW from the previous setup attempt.
Locate the DVD/CD drive When hardware (for example, HDD, a USB device, or a DVD-ROM drive) is added to a system after it has booted to EFI, the EFI Shell environment does not automatically detect the new device. You must reconnect the device driver for the EFI Shell to recognize the device. The EFI Shell environment creates default mappings for all the device handles that support a recognized file system. After you change the system configuration or add a new device, you must regenerate these mappings.
Set ACPI flag to windows (cell-based servers only) On cell-based servers, you must set the Advanced Configuration and Power Interface (ACPI) flag to the value appropriate for the operating system it boots. For the server to boot to Windows Server 2003, set the ACPI flag to windows. If you purchased your server with a Windows operating system option, this flag is set to windows in the factory. If you purchased the server with a different OS or no OS, you must set this flag to windows.
You can specify the network interface card (NIC) for PXE to use to communicate with the RIS server. When the HP Integrity server boots from this NIC, it effectively boots from the remote RIS server. Working in conjunction with the RIS server, PXE installs a new image of the Windows Server 2003 on the HP Integrity server. To enable PXE on the HP Integrity server from the EFI Shell, complete the following steps: 1. 2. 3. 4. From the EFI Boot Manager, select EFI Shell. The device mapping table appears.
2 Installing the OS This chapter provides instructions for installing the operating system (OS) using a headless console, a GUI console, or a PXE-enabled NIC. This chapter also provides reinstallation instructions for Windows Server 2003. Each method comprises a series of tasks, concluding with two tasks that verify that the OS was installed correctly. You must install the HP Support Pack after installing the OS. You must also install any operating system and security updates using the Smart Update media.
Run EBSU The EFI-Based Setup Utility (EBSU) provides an easy-to-use interface to flash the firmware, partition the hard disk, install diagnostic tools, configure storage controllers, and run other EFI utilities. NOTE: If you are installing an HP Virtual Machines (HPVM) Windows guest, you do not need to run EBSU as part of your setup. Skip this section and go directly to the next section (Run Windows Setup). To run EBSU, complete the following steps: 1. Power on the server. The server boots to EFI.
7. EBSU displays the firmware update screen, listing each device, its installed firmware version, and the firmware version on the Smart Setup media. Select the devices whose firmware you want to update. To continue, select Next and press Enter. Figure 2-3 Update firmware NOTE: You might be able to use EBSU to flash the firmware of some devices. You cannot flash the firmware if the installed version is the same or higher than the version on the Smart Setup media.
Figure 2-5 Install diagnostic tools 11. EBSU displays the partition confirmation window. Select Continue and press Enter. 12. EBSU prompts you to insert the Microsoft Windows Server 2003 with SP2 CD in the DVD drive. Insert the CD and press Enter. Figure 2-6 Insert the Microsoft Windows Server 2003 CD Run Windows Setup Windows Setup prompts you to create a system partition on the boot disk if needed, copies the OS files on to that partition, and attempts to reboot from the boot disk.
3. 4. 5. If Windows Setup cannot find a system partition, it prompts you to create one. Press Enter to continue. Windows creates a partition and then prompts you to format it. Select the partition in which you want to install the OS and press Enter. Windows formats the partition if necessary, checks the partition for errors, and begins to copy the OS files. Monitor the copy process until it completes. You can monitor installation progress from the SAC command prompt by using these three channels: setuplog.
6. EBSU displays the Express Setup introduction. Press Enter to continue. Figure 2-8 Select Express Setup 7. EBSU displays the firmware update screen, listing each device, its installed firmware version, and the firmware version on the Smart Setup media. Select the devices whose firmware you want to update. To continue, select Next and press Enter. Figure 2-9 Update firmware NOTE: You might not be able to use EBSU to flash the firmware of some devices.
Figure 2-10 Partition disk 9. Specify the option to install offline diagnostic tools (from the HP Itanium Processor Family offline diagnostics and utilities CD). 10. Also, specify the option to launch the Windows OS installer. Select Setup and press Enter. Figure 2-11 Install diagnostic tools 11. EBSU displays the partition confirmation window. Select Continue and press Enter.
12. EBSU prompts you to insert the Microsoft Windows Server 2003 with SP2 CD in the DVD drive. Insert the CD and press Enter. Figure 2-12 Insert the Microsoft Windows Server 2003 CD Run Windows Setup Windows Setup prompts you to create a system partition on the boot disk if needed, copies the OS files on to that partition, and attempts to reboot from the boot disk. To run Windows Setup, complete the following steps: 1.
2. In the Windows Setup Wizard, enter the following setup information: a. In the License Agreement window, click Accept and then Next. b. In the Regional and Language Options window, click Next. c. In the Your Product Key window, enter the product key. The product key is located on the label attached to the server. d. In the Licensing Modes window, select the license you purchased. e. In the Administrator Password window, enter the server name and a password. f.
Reinstalling the operating system involves loading the image from the Reinstallation media onto the boot disk and, after Windows Server 2003 is loaded, specifying the server settings. CAUTION: Reinstallation overwrites all files on the boot disk. The boot disk is determined by bus search order and might not be the disk you expect it to be. HP recommends disconnecting or unplugging all drives from the server except the boot disk. This includes all SAN storage, too.
12. Select the desired partition size (33 GB is recommended). The maximum partition size is limited to the size of the drive. Select Y to continue. NOTE: The installation process copies files to the hard disk. Do not power off the server during the installation. 13. When the installation process completes, press any key to reboot the server. 14. The local console displays a screen indicating that the EMS was detected. When prompted to use the local console, do not click OK. 15.
NOTE: If you select No, you should inspect the system and proceed to update the drivers and install the utilities before bringing the system online. 11. At the system reboot prompt, click Yes to reboot the system and implement your changes. After the reboot, your system is ready to go online.
7. Select the desired partition size (33 GB is recommended). The maximum partition size is limited to the size of the drive. Click OK to continue. NOTE: The installation process copies files to the hard disk. The progress bar may increase or decrease throughout this process. Do not power off the server during the installation. 8. 9. When the installation process displays a dialog box, click OK to continue. Click Exit. The server reboots to the Windows Server 2003 operating system.
3. To install all operating system updates, click Install... in the Operating System Updates section. The HP Package Setup screen appears. 4. Click Install. The HP Setup screen appears. Click Install to continue with the installation or click Close to exit setup. When you click Install, a command window appears, listing each update as it installs. Sometimes these are very large updates and can take several minutes each to install. 5. When prompted, click Reboot to complete the installation.
4. 5. 6. 7. In the Windows Component wizard, clear all components except Management and Monitoring Tools, then click Next. From the Management and Monitoring Tools window, select Simple Network Management Protocol, then click OK. The Component Wizard page appears. Click OK to start the installation. Monitor the installation and click Finish to complete it. Configure SNMP To configure SNMP, complete the following steps: 1. 2. 3. 4.
To set up a remote desktop connection from a headless server, complete the following steps: 1. 2. 3. 4. Go to the SAC console. At the SAC> prompt, enter cmd. Press Esc+Tab to enter the Command Prompt console (this requires logging in as Administrator). Enter the following command from the Windows command prompt: reg add "HKLM\System\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f 5.
2. 3. 4. 5. 6. Select m(Modify) to modify the OS boot loader. At the prompt, enter the OS boot option to modify. For example, select the first boot option by entering 1. At the prompt, select the second variable to modify, OsLoadOptions, by entering 2. Retype the OsLoadOptions variable, adding /EXTINTVEC to it, and press Enter. Exit and reboot. Update firmware To check the system firmware versionand boot the server to EFI, complete the following steps: 1. 2. Use the arrow key to select EFI Shell.
1. 2. 3. 4. 5. 6. From Windows, right-click the My Computer icon. Click the Properties button, displaying the System Properties window. Go to the Hardware tab. Click Device Manager to display the Device Manager window. Select View > Devices by Type to list the system devices. Expand the Other Devices entry. Scan the listed devices, verifying that no device displays a yellow bang (!) or a question mark (?). • A yellow bang (exclamation mark) indicates a hardware problem, a device driver problem, a missing .
screen appears and the Integrity Support Pack found on the Smart Setup CD is listed there, with a check mark next to it. Click OK to proceed. 10. The Select Items to be Installed screen appears next. This screen lists all of the individual component updates contained in that Integrity Support Pack, with a check mark next to each. Click Install to proceed. The installation begins. 11. When the installation finishes, the Installation Results screen appears.
channel is detected. and click OK to continue. Symptoms of the failure include rapid resizing of the installation window, partial data display, and mouse input failure. To recover and finish the installation, you must create a new boot entry that includes the/NOVESAoption. To do this, complete the following steps: 1. From the EFI Shell, go to the MSUTIL directory: fs1: cd msutil 2. Run the nvrboot.
It is beyond the scope of this document to describe the installation and use of HPVM on Integrity servers. These topics are already covered in detail in another document — HP Integrity Virtual Machines Installation, Configuration, and Administration — found here: http://docs.hp.com/en/hplex.html#HP%20Integrity%20Virtual%20Machines If you are interested in implementing HPVM, see this document first. It explains how to install and configure the host operating system, the HPVM software, and guests.
4. Verify success by rebooting to the EFI Shell again and issuing another cpuconfig threads command, which should indicate ON. Enable hyperthreading using Partition Manager Another way to enable hyperthreading (on partitionable servers only), is to use the Partition Manager partitioning tool. Partition Manager is a Web-based application for system administrators that provides a convenient GUI for creating, configuring, and managing the hard partitions (nPartitions) on an HP Integrity server.
3 Installing the Management Tools This chapter describes the installation of tools and applications used to manage your Integrity server. Installing System Management Homepage This section describes the installation of System Management Homepage (SMH) on Integrity servers. Configure SMH after Support Pack installation When you install SMH using the Support Pack it, is configured using the default security settings. Use the SMH online help for information on the security settings. To access the help: 1.
11. To add HP SMH group names: a. In the Group Name field, enter a name for the operating system group. b. Select an operating level to include: Administrator, Operator, or User. 12. Click Add. The group name is added. You can add a maximum of five entries for each group level. 13. Click Next to continue. The User Access dialog box appears. Use it to configure HP SMH for the following access types: • Select Anonymous Access to enable anonymous access to unsecured pages.
17. Select IP Binding to enable the subnet IP address and netmask. The IP Binding dialog box enables you to bind to specific IP addresses that match a specific subnet IP address or netmask. It restricts the subnet you want to manage. a. Enter the subnet IP address in the designated field. b. Enter the netmask in the designated field. c. Click Add, and the subnet IP address or netmask appears in the dialog box. d. To delete a subnet IP address or netmask from the dialog box, select it and click Delete.
NOTE: Do not install any HP management agents until you have installed and configured the TCP/IP and SNMP protocols. Configure management agents after Support Pack installation Agents are automatically activated when they are installed (except for the Clustering Information agents). Inactive agents remain installed but are dormant until you activate them again. For instructions on configuring an agent or making it inactive, see “Activating and configuring agents” (page 60).
NOTE: You must have Administrator rights to access the management agents from the Windows Control Panel. 1. Open the Windows Control Panel and select HP Management Agents for Integrity Servers. The installed agents are listed in the window. All agents except clustering information are activated at time of installation. 2. Click the Services tab. Figure 3-3 Services tab screen 3. 4. 5. Select an agent from either column to change the active or inactive status.
2. Click Next to access the SMTP information window. Figure 3-5 Mail (SMTP) server information 3. 4. Enter a valid email address in the From address field or leave it blank. Enter the name of the SMTP mail server you are using in the Mail server field. You must enter a valid server address to continue with the setup process. The wizard checks the SMTP mail server address you entered to see if it can be accessed.
8. 9. Click OK to return to the recipient information window. Select a user name and click Edit to edit user properties, or select a user name and click Delete to remove a user. 10. Click Events to display the Event Selection window. Figure 3-8 Event selection window 11. Use the severity and source filter fields to view selected events only. The event severity levels, source, and message are not user-configurable. 12. Click the check box to enable an event or disable email notification for an event. 13.
Figure 3-9 SNMP Settings tab 3. 4. 5. 6. Select a time interval for SNMP data collection from the Data Collection Interval list box. Click the Send Test Trap button (available only if the HP host agent is active) to send a test trap. Click Clear All Thresholds to clear all current SNMP trap threshold values. Click OK.
This tab displays all currently active (running) server processes. The Monitor Option column displays the current monitoring status for each process listed. 3. 4. Select the process you want to change the monitoring status for. Change monitoring status by clicking one of these radio buttons: • None — No SNMP traps are generated for this process. • Start — An SNMP trap is generated when this process starts. • Stop — An SNMP trap is generated when this process stops.
3. 4. 5. From the list of services, double-click SNMP Service. The SNMP Service Properties (Local Computer) window appears. Click the Security tab. Click the Traps tab. Figure 3-12 SNMP traps tab 6. In the Community name field, if a community name already exists, select it. If one does not exist, enter a community name and click Add to List. NOTE: The default community string for HP Insight Manager is public.
nPartition Manager Bundle. For more information about installing and using Partition Manager, see the nPartition Guide, located on the HP Smart Setup media at: \contents\doc\en_us\npartition.pdf Install nPartition Commands Bundle from the Smart Setup media This section describes the tasks you need to complete before you install the nPartition Commands Bundle from the Smart Setup media. 1. 2. Install all the OS fixes and security fixes on the Smart Update media.
11. Through the next several screens, configure SMH administrator and security settings as prompted, and the SMH installation begins. 12. When the SMH installation finishes, click Next in the HP Servlet Container for SMH wizard screen. Then click Next two more times to begin the servlet container installation. 13. Click Finish to complete the servlet container installation. 14. The HP Partition Manager installation starts next. When it finishes, press any key in the command window to exit. 15.
• • The host name and IP address and the login/password for a remote nPartition (for remote WBEM connections) The host name and IP address and the IPMI password of an MP (for remote IPMI connections) If you are running Partition Manager on an nPartition, skip steps 3 and 4 and go directly to the step 5 where you verify correct operation of the Partition Manager. 3. In order to test remote WBEM connections, do the following: a.
4 Performing hot-plug operations This chapter describes adding and removing PCI cards on HP Integrity servers. Adding a card to your system is called a “hot-plug addition,” and removing a card is called a “hot-plug deletion.” IMPORTANT: HP Integrity rx1620, rx2620, rx2660, BL860c, and BL870c servers do not support PCI card hot-plug addition or deletion.
NOTE: You cannot perform a hot-plug addition for some cards unless they replace the same type card in the slot. You cannot hot-add them in a new installation. Although no damage to the server occurs if you attempt a hot-plug addition with these cards, they will not function until the next reboot. The following table lists the PCI cards that do not support hot-plug addition.
NOTE: HP Integrity rx7620, rx7640, rx8620, and rx8640 servers have a white bell-shaped image button located at the top rear of the PCI slot. To access, remove the button cover. HP Integrity rx3600, rx4640, and rx6600 servers have a maroon-colored button on the top of the PCI slot separator, just below the manual retention latch (MRL). HP Integrity Superdome servers do not have attention buttons. 3. 4. Wait for the slot to power off (green power LED will turn off). Open the MRL.
Activate PCI card in Cabinet w, IO Bay x, IO Chassis y, PCI Slot z? (Y/[N]) y Request to Activate PCI card sent to system. Check slot power LED. MP:CM> 4. 5. Check that the slot power LED (found by looking down through top of chassis) is not blinking, indicating that the slot is powered. If the green LED is not on, the power to the slot is not on and the addition of the card failed. Check the Windows Device Manager for the device just installed. If the device is not present, the addition failed.
1. 2. Locate the slot of PCI card to delete. Press the attention button for the slot. The power LED will begin flashing. During the 5 seconds that the power LED is flashing, you can abort the request by pressing the attention button. When the green LED stops blinking and goes off, it is safe to remove the card. NOTE: Do not remove the card before the LED stops blinking or a fatal machine check alert (MCA) error occurs. 3. 4. 5. Open the manual retention latch (MRL). Remove the card. Close the MRL.
A Preparing the server for Microsoft SQL Server 2005 This appendix describes the server configuration tasks needed to install Microsoft SQL Server 2005. SQL Server 2005 installation This section is an overview of the steps needed to install SQL Server 2005. For further installation and configuration information, see the SQL Server 2005 documentation. 1. Configure the server • Set the system ACPI Config Flag to Windows.
INSTALLVS=SQL_Engine INSTANCENAME= ADDLOCAL=SQL_Engine,Client_Components ADDNODE= GROUP= IP= ADMINPASSWORD= SAPWD= INSTALLSQLDIR= INSTALLSQLDATADIR= SQLACCOUNT= SQLPASSWORD= AGTACCOUNT= AGTPASSWORD= Installing SQL Server from the GUI To install SQL Server from the GUI, complete the following steps: 1.
15. 16. 17. 18. 19. 20. 21. For more information about this page, click Help at the bottom of the page. When you are finished, click Next. If you selected SQL Server Authentication, you must provide a user name and password with administrative privileges for that instance. Confirm the Report Server Database Name. Click Next. If you selected Reporting Services as a feature, the Report Server Delivery Settings page displays.
B EFI Utilities This appendix provides an overview of the EFI Extensible Firmware Interface (EFI) and the EFI-Based Setup Utility (EBSU). The EFI provides access to the server at a pre-operating system , which enables you to flash the firmware, partition the hard disk, install diagnostic tools, configure storage controllers, and run other EFI utilities. Introduction to EFI The Extensible Firmware Interface (EFI) is an interface between the operating system, the firmware, and the hardware.
Common EFI Shell commands The following table lists some commonly used EFI commands. Table B-1 EFI Shell Commands and Descriptions Command Description Boot Commands autoboot Set and view autoboot timeout variable. bcfg Display and modify the driver and boot configuration. boottest Set and view BootTest bits. dbprofile Display and modify direct boot profiles for use by lanboot. lanboot Boot over the LAN.
Table B-1 EFI Shell Commands and Descriptions (continued) Command Description connect Bind a driver to a device. dblk Hex dump – BlkIo devices. devices Display devices managed by EFI drivers. devtree Display tree of devices. dh Dump handle information. disconnect Disconnect drivers from devices. drivers Display list of drivers. drvcfg Invoke the Driver Configuration Protocol. drvdiag Invoke the Driver Diagnostics Protocol. guid Dump known GUID IDs. lanaddress Display MAC address.
Table B-1 EFI Shell Commands and Descriptions (continued) Command Description Memory Commands Commands for listing and managing memory, EFI variables, and NVRAM details. default Set the default NVRAM values. dmem Dump memory or memory-mapped I/O. dmpstore Display all EFI variables. memmap Display the memory map. mm Display and modify MEM/IO/PCI. pdt View and clear nPartition or cell memory page deallocation table (PDT).
EFI-Based Setup Utility The EFI-Based Setup Utility (EBSU) provides an easy-to-use interface to flash the firmware, partition the hard disk, install diagnostic tools, configure storage controllers, and run other EFI utilities. The EBSU provides the following functions: • Express Setup — Guides you through Windows installation and setup. See “Run EBSU” (page 39) for detailed information on using Express Setup.
5. Enter the following: load vfloppy.efi 6. Enter the following: map -r You cannot unload or change the virtual floppy file system unless you reset the computer. CAUTION: When Windows installation begins, you are prompted to press F6 to install a third-party SCSI or RAID driver. Do not press F6. Pressing F6 forces Windows to look for the driver on a physical floppy drive, which does not exist. The driver is loaded in memory and installed automatically.
8. At the prompt, enter the following path: EFI\Microsoft\Winnt50\boot0001 This creates the Windows boot file boot0001. Verify successful boot file creation To verify that the boot file was created successfully, use the following procedure: 1. Select EFI Shell[Built-in] from the EFI Boot Manager. 2. Enter fs0: at the EFI Shell prompt. 3. Enter cd MSUTIL at the fs0:> prompt. 4. Execute the NVRBOOT.EFI boot utility at the fs0:\MSUTIL> prompt. 5. Enter I to Import. 6.
C Management processor and Special Administration Console This appendix describes the management processor (MP) and Special Administration Console (SAC), which you can use to monitor Windows installations and administer the system using a headless console. Management processor This section describes the management processor (MP).
• MODEM PROTOCOL: Bell or CCITT. CCITT is a European standard; RTS/CTS signaling is used as well as the Ring signal. Bell is a U.S. or simple mode. • BAUD RATES: Input and output data rates are the same — 300, 1200, 2400, 4800, 9600, 38400, 115200 bit/sec. • FLOW CONTROL: Hardware uses RTS/CTS; software uses Xon/Xoff. • TRANSMIT CONFIGURATION STRINGS: Disable this setting whenever the modem being used is not compatible with the supported modem (MT5634ZBA).
DI — Disconnects remote/modem or LAN/WEB console. This command disconnects (hangs up) the remote/modem or LAN/WEB users from the MP. It does not disable the ports. The remote console is no longer mirrored. FW — Activates MP firmware upgrade mode. This command is available from either the LAN or a local serial port. This command activates firmware upgrade mode, which loads new firmware through the MP LAN by FTP (which must be operational). An MP reset is generated after the upgrade is complete.
command displays the current state of the DCD, CTS, DSR, and RI status signals and the last state of the DTR and RTS control signals set by the firmware. PC — Power Control. Turns system power on and off. For proper system shut down, shutdown the OS before issuing this command or use the graceful shutdown option. Use this command to switch the system power on or off. You can have the action take place immediately or after a specified delay. PG — Paging parameter setup. Configures pagers.
• V — View mode configuration (text, keyword, hex) • ? — Display this help menu • Q — Quit SMCLP — Server Management Command Line Protocol (rx2660, rx3600, rx6600, BL860c, and BL870c only). This command switches the console terminal from the MP Main Menu to the Server Management Command Line Protocol (SMASH) SM CLP interface.
XD — Diagnostics or Reset of MP. Use this command to perform some simple checks to confirm the health and connectivity status of the MP. The following tests are available: • MP Parameter Checksum • Verify I2C connection (get BMC Device ID) • LAN connectivity test using ping • Modem self-tests Also, you can reset the MP safely using this command, without affecting the operation of the server.
GUI console are also available using the headless console. This includes starting the system and performing system-recovery tasks. Emergency Management Services consists of components that are standard features of Windows Server 2003, and to which console redirection functionality has been added. Emergency Management Services also includes a management console that is unique to it: Special Administration Console (SAC).
Services, you can see which portions have completed and whether any errors have occurred. This is a useful way to check the progress of your setup and to diagnose setup failures. The setup log channels are as follows: • setuplog.txt: Monitors setup progress. • setupact.log: Displays any warnings during setup. • setuperr.log: Displays any errors that might occur during setup. SAC Channel Management Commands The following table lists the channel management commands.
