File name: readme.txt ****************************************************************** | | | IBM(R) ServerGuide(TM) Scripting Toolkit, Version 1.0.02 | | | | Part number 90P2959 | | | | (C) Copyright International Business Machines Corporation | | 2003, 2004. All rights reserved. | | | | US Government Users Restricted Rights -- Use, duplication | | or disclosure restricted by GSA ADP Schedule Contract with | | IBM Corp. | | | | Notes: | | o Before using this information and the product it supports, | | read the general information under "NOTICES AND TRADEMARKS"| | in this document. | | o Check the ServerGuide Scripting Toolkit Web site for the | | latest version of this readme. See "SUPPORT WEB SITES" for | | more information. | | | | Updated 20 April 2004 | | | ****************************************************************** 1.0 Overview 2.0 Change history 2.1 ServerGuide Scripting Toolkit 1.0.02 2.2 ServerGuide Scripting Toolkit 1.0.01 2.3 ServerGuide Scripting Toolkit 1.0 3.0 Installation 4.0 Supported servers 4.1 Supported servers that might contain IBM ServeRAID(TM) controllers 4.2 Supported servers that contain an integrated SCSI controller with RAID capabilities 4.3 Supported servers that contain an IDE RAID controller 4.4 Supported servers that contain an IBM ServeRAID 7e (Adaptec(R) HostRAID(TM)) controller 5.0 Supported deployment scenarios 5.1 DOS-startable diskette with a data CD 5.2 DOS-startable CD 5.3 DOS-startable diskette with a network share 5.4 Remote Supervisor Adapter II virtual diskette 5.5 Microsoft(R) Automated Deployment Services (ADS) 6.0 Supported operating systems 6.1 Windows(R) 2000 (Server and Advanced Server) 6.2 Windows Server 2003 (Standard, Enterprise, and Web Editions) 6.3 Red Hat(R) Linux, Version 7.3 6.4 Red Hat Linux, Version 8.0 6.5 Red Hat Enterprise Linux AS, Version 2.1 7.0 Solving ServerGuide Scripting Toolkit problems 7.1 Preventing DOS menus from being displayed 7.1.1 Non-network-based deployment scenarios 7.1.2 Network-based deployment scenarios 7.2 Editing netvars.bat 7.3 Source system hangs during Linux deployment 7.4 Loadlin fails to start Linux installation 7.5 Microsoft ADS fails to process some INF files 7.6 Problems with CD-based scenarios 7.7 Network-based installation on an eServer(R) BladeCenter(TM) HS20, machine type 8832 with an IDE RAID controller 7.8 Unknown device in Windows Device Manager with xSeries 206, machine type 8482 or xSeries 306, machine type 8836 and a Remote Supervisor Adapter II installed 7.9 Microsoft ADS does not start with xSeries 206, machine type 8482, xSeries 306, machine type 8836, or eServer BladeCenter HS40, machine type 8839 7.10 Network not available after installation of Windows-based operating system to an eServer BladeCenter HS40, machine type 8839 8.0 Additional files, utilities, and information 8.1 dumpcfg.bat 8.2 sleep.exe 8.3 Using the ServerGuide Scripting Toolkit with an existing deployment process 8.4 Selecting a network interface card (NIC) device driver during a deployment scenario 8.5 Additional steps required for creating a Microsoft ADS job template 8.6 Limitations 9.0 Support Web sites 10.0 Notices and trademarks 1.0 OVERVIEW ------------- The ServerGuide Scripting Toolkit is a collection of system-configuration tools and installation scripts that you can use to deploy operating systems to your IBM eServer or xSeries(R) server in a repeatable, predictable manner. Translated versions of the licensing information and license agreement for ServerGuide Scripting Toolkit are available from the ServerGuide Scripting Toolkit Web site. See section 9.0, "Support Web sites," for more information. 2.0 CHANGE HISTORY ------------------- This section contains information about the ServerGuide Scripting Toolkit change history. 2.1 ServerGuide Scripting Toolkit 1.0.02 ----------------------------------------- ServerGuide Scripting Toolkit 1.0.02 includes the following changes: o Support for the following servers: - xSeries 206, machine type 8482 - xSeries 306, machine type 8836 - eServer BladeCenter HS40, machine type 8839 2.2 ServerGuide Scripting Toolkit 1.0.01 ----------------------------------------- ServerGuide Scripting Toolkit 1.0.01 includes the following changes: o Support for the following servers: - xSeries 225, machine type 8649 - eServer 325, machine type 8835 o Reduced DOS environment space usage 2.3 ServerGuide Scripting Toolkit 1.0 -------------------------------------- This was the first release of ServerGuide Scripting Toolkit. 3.0 INSTALLATION ----------------- Instructions for installing the ServerGuide Scripting Toolkit are provided in the "IBM ServerGuide Scripting Toolkit User's Reference." This guide is in Portable Document Format (PDF) and requires Adobe Acrobat Reader to view it. 4.0 SUPPORTED SERVERS ---------------------- You can use the ServerGuide Scripting Toolkit to deploy operating systems to the following IBM eServer and xSeries servers: o xSeries 205, machine type 8480 o xSeries 206, machine type 8482 o xSeries 225, machine type 8647 o xSeries 225, machine type 8649 o xSeries 235, machine type 8671 o xSeries 255, machine type 8685 o xSeries 305, machine type 8673 o xSeries 306, machine type 8836 o xSeries 335, machine type 8830 o xSeries 335, machine type 8676 o xSeries 345, machine type 8670 o xSeries 360, machine type 8686 o xSeries 365, machine type 8861 o xSeries 365, machine type 8862 o xSeries 440, machine type 8687 o xSeries 445, machine type 8870 o eServer 325, machine type 8835 o eServer BladeCenter HS20, machine type 8678 o eServer BladeCenter HS20, machine type 8832 o eServer BladeCenter HS40, machine type 8839 4.1 Supported servers that might contain IBM ServeRAID controllers ------------------------------------------------------- The following servers might contain ServeRAID controllers. You can use the ipssend utility to configure ServeRAID controllers as part of the ServerGuide Scripting Toolkit deployment process. o xSeries 205, machine type 8480 o xSeries 206, machine type 8482 o xSeries 225, machine type 8647 o xSeries 225, machine type 8649 o xSeries 235, machine type 8671 o xSeries 255, machine type 8685 o xSeries 305, machine type 8673 o xSeries 306, machine type 8836 o xSeries 335, machine type 8830 o xSeries 335, machine type 8676 o xSeries 345, machine type 8670 o xSeries 360, machine type 8686 o xSeries 365, machine type 8861 o xSeries 365, machine type 8862 o xSeries 440, machine type 8687 o xSeries 445, machine type 8870 o eServer 325, machine type 8835 Notes: o (IBM ServeRAID 6i+ Ultra 320 SCSI adapters only) The firmware level of this adapter is not supported by the current ServerGuide device driver set. A newer version of ServerGuide, when available, is required to support this adapter. o (IBM ServeRAID 7t adapters only) This adapter is not currently supported by the ServerGuide Scripting Toolkit. 4.2 Supported servers that contain an integrated SCSI controller with RAID capabilities ----------------------------------------------------------------- The following servers contain an integrated SCSI controller with RAID capabilities. You can use the cfg1030 utility to configure the integrated SCSI controllers with RAID capabilities as part of the the ServerGuide Scripting Toolkit deployment process. o xSeries 225, machine type 8647 o xSeries 225, machine type 8649 o xSeries 235, machine type 8671 o xSeries 335, machine type 8830 o xSeries 335, machine type 8676 o xSeries 345, machine type 8670 o xSeries 365, machine type 8861 o xSeries 365, machine type 8862 o xSeries 445, machine type 8870 o eServer 325, machine type 8835 o eServer Bladecenter HS20, machine type 8678 o eServer BladeCenter HS20, machine type 8832 o eServer BladeCenter HS40, machine type 8839 4.3 Supported servers that contain an IDE RAID controller ---------------------------------------------------------- The following server contains an IDE RAID controller. You can use the hypercfg utility to configure an IDE RAID controller as part of the the ServerGuide Scripting Toolkit deployment process: o eServer BladeCenter HS20, machine type 8832 4.4 Supported servers that contain an IBM ServeRAID 7e (Adaptec HostRAID) controller ---------------------------------------------------------------- You must disable the IBM ServeRAID 7e (Adaptec HostRAID) controller to use this version of the ServerGuide Scripting Toolkit. Go to the IBM Web site http://www.ibm.com/pc/support/ and search for installation instructions, when available, for your server. 5.0 SUPPORTED DEPLOYMENT SCENARIOS ----------------------------------- The ServerGuide Scripting Toolkit supports the following deployment scenarios: o DOS-startable diskette with a data CD o DOS-startable CD o DOS-startable diskette with a network share o Remote Supervisor Adapter II virtual diskette o Microsoft Automated Deployment Services (ADS) 5.1 DOS-startable diskette with a data CD ------------------------------------------ You can use a DOS-startable diskette with a data CD to deploy Microsoft Windows to all supported servers that have both a diskette drive and a CD drive. This includes all supported servers except the following: o eServer HS20, machine type 8678 o eServer HS20, machine type 8832 o eServer BladeCenter HS40, machine type 8839 5.2 DOS-startable CD --------------------- You can use a DOS-startable CD to deploy Microsoft Windows to all supported servers that have a CD drive. This includes all supported servers except the following: o eServer BladeCenter HS40, machine type 8839 Notes: o (eServer BladeCenter HS20, machine type 8832 server) You can use this deployment scenario to deploy Windows if the target server has one of the following BIOS code levels installed: - version 1.01 (part number 23K4695) - version 1.04 (part number 26K9227) If BIOS version 1.02 (part number 26K4905) is installed, the deployment scenario fails. o (eServer BladeCenter HS20, machine type 8678 server) You can use this deployment scenario to deploy Windows if the target server has one of the following BIOS code levels installed: - version 1.05 (part number 25K9216) - version 1.07 (part number 26K9217) If BIOS version 1.06 (part number 26K3278) is installed, the deployment scenario fails. 5.3 DOS-startable diskette with a network share ------------------------------------------------ You can use a DOS-startable diskette with a network share to deploy Microsoft Windows or Red Hat Linux to all supported servers that have a diskette drive and access to a network share. 5.4 Remote Supervisor Adapter II virtual diskette -------------------------------------------------- You can use a Remote Supervisor Adapter II virtual diskette to deploy Microsoft Windows to all supported servers that contain a Remote Supervisor Adapter II. This includes the following servers: o xSeries 205, machine type 8480 o xSeries 206, machine type 8482 o xSeries 225, machine type 8649 o xSeries 235, machine type 8671 o xSeries 255, machine type 8685 o xSeries 305, machine type 8673 o xSeries 306, machine type 8836 o xSeries 345, machine type 8670 o xSeries 365, machine type 8861 o xSeries 365, machine type 8862 o xSeries 445, machine type 8870 Note: The xSeries 445, machine type 8870 is only supported when a Remote Supervisor Adapter II-EXA is installed. 5.5 Microsoft Automated Deployment Services (ADS) -------------------------------------------------- You can use Microsoft ADS to deploy Microsoft Windows to all supported servers. 6.0 SUPPORTED OPERATING SYSTEMS -------------------------------- You can use the ServerGuide Scripting Toolkit to deploy the following operating systems to supported servers: o Windows 2000 (Server and Advanced Server) o Windows Server 2003 (Standard, Enterprise, and Web Editions) o Red Hat Linux, Versions 7.3 and 8.0 o Red Hat Enterprise Linux AS, Version 2.1 You can use the ServerGuide Scripting Toolkit to deploy the English, French, German, Italian, Spanish, and Swedish language versions of Microsoft Windows. 6.1 Windows 2000 (Server and Advanced Server) ---------------------------------------------- You can deploy Windows 2000 (Server and Advanced Server) to all supported servers, except the eServer 325, machine type 8835. 6.2 Windows Server 2003 (Standard, Enterprise, and Web Editions) ----------------------------------------------------------------- You can deploy Windows Server 2003 (Standard, Enterprise, and Web Editions) to all supported servers. Note: The eServer 325, machine type 8835 supports only the 32-bit version of Windows Server 2003, Enterprise Edition. 6.3 Red Hat Linux, Version 7.3 ------------------------------- You can deploy Red Hat Linux, Version 7.3 to the following supported servers: o xSeries 205, machine type 8480* o xSeries 225, machine type 8647* o xSeries 225, machine type 8649* o xSeries 235, machine type 8671* o xSeries 255, machine type 8685 o xSeries 305, machine type 8673* o xSeries 335, machine type 8830* o xSeries 335, machine type 8676* o xSeries 360, machine type 8686* o eServer BladeCenter HS20, machine type 8678 The operating system is certified by the vendor for the servers marked with an asterisk (*). It is not formally supported by IBM. 6.4 Red Hat Linux, Version 8.0 ------------------------------- You can deploy Red Hat Linux, version 8.0 to the following supported servers: o xSeries 205, machine type 8480* o xSeries 225, machine type 8647* o xSeries 225, machine type 8649* o xSeries 235, machine type 8671* o xSeries 255, machine type 8685* o xSeries 305, machine type 8673 o xSeries 335, machine type 8676 o xSeries 345, machine type 8670* o xSeries 360, machine type 8686 o eServer Bladecenter HS20, machine type 8678 The operating system is certified by the vendor for the servers marked with an asterisk (*). It is not formally supported by IBM. 6.5 Red Hat Enterprise Linux AS, Version 2.1 --------------------------------------------- You can deploy Red Hat Enterprise Linux AS, Version 2.1 to all supported servers except the following: o xSeries 206, machine type 8482 o xSeries 306, machine type 8836 o xSeries 365, machine type 8861 o xSeries 365, machine type 8862 7.0 SOLVING SERVERGUIDE SCRIPTING TOOLKIT PROBLEMS --------------------------------------------------- This section contains information about solving problems that might occur as you use ServerGuide Scripting Toolkit. 7.1 Preventing DOS menus from being displayed ---------------------------------------------- You can prevent DOS menus from being displayed during the deployment scenarios. 7.1.1 Non-network-based deployment scenarios --------------------------------------------- Use this procedure for the following deployment scenarios: o DOS-startable diskette with a data CD o DOS-startable CD Complete the following steps to prevent the DOS menus from being displayed: 1. In an ASCII text editor, open the config.sys file on the DOS-startable diskette. 2. Locate the line that contains the word "MENUDEFAULT" and uncomment it. (To uncomment the line, remove "rem" from the beginning of the line.) 3. Save the modified config.sys file. 7.1.2 Network-based deployment scenarios ----------------------------------------- Use this procedure for the following deployment scenarios: o DOS-startable diskette with a network share o Remote Supervisor Adapter II virtual diskette Complete the following steps to prevent the DOS menus from being displayed: 1. In an ASCII text editor, open the config.sys file on the DOS-startable diskette. 2. Locate the line that contains the word "MENUDEFAULT" and refers to the network interface card (NIC) device driver that you want to be loaded automatically; then, uncomment the line. (To uncomment the line, remove "rem" from the beginning of the line.) 3. In the line that you uncommented, identify the DOS label. It is located between the word "MENUDEFAULT" and the numeral 0. 4. Locate the menu block section that is associated with the DOS label; then, uncomment the line that contains the word "MENUDEFAULT". 5. Save the modified config.sys file. 7.2 Editing netvars.bat ------------------------ If you edit the netvars.bat file without using the CustomizeNetworkVariables.bat file, the following INI files on the DOS startable diskette are not updated automatically: o \net\network.ini o \bcom\protocol.ini o \e1000\protocol.ini o \e100b\protocol.ini To solve this problem, complete one of the following actions: o Run the CustomizeNetworkVariable.bat file. Do not make any changes to the netvars.bat file. When you close Notepad, all the INI files are updated automatically. o With the DOS-startable diskette in the diskette drive, run the UpdateNetworkFiles.bat file. This file is in the \sg_stk\boot directory of the source tree. 7.3 Source system hangs during Linux deployment ------------------------------------------------ When you are deploying Red Hat Enterprise Linux AS, Version 2.1 from a source system running Microsoft Internet Information Services (IIS), the source system might appear to hang. To solve this problem, disable the IIS HTTP Keep-Alive feature. 7.4 Loadlin fails to start Linux installation ---------------------------------------------- Loadlin might fail to start the Linux installation if the parameter file contains more than 256 characters. By default, the maximum command-line length that can be passed to the kernel is 256 characters. See the Loadlin documentation for information about changing the Linux kernel command-line length. 7.5 Microsoft ADS fails to process some INF files ------------------------------------------------- Microsoft ADS, Version 1.0 might fail to process some device-driver INF files. This is a known Microsoft ADS problem and might prevent the ADS Deployment Agent Builder from starting. See Microsoft Knowledge Base articles 829053 and 830413 for more information and to obtain the latest Hotfixes related to this problem. A future Microsoft Windows Server 2003 Service Pack might include these Hotfixes. Alternatively, you can change the device-driver INF files to solve this problem for specific devices. The following steps are examples of specific device-driver INF files and the required changes to solve this problem. 1. Open the nfrd960.inf file in an ASCII text editor. This file is in the :\Program Files\Microsoft ADS\nbs\repository\User\Presystem directory, where is the drive letter of the hard disk drive where Microsoft ADS is installed. 2. Modify the [Manufacturer] section of the file so that it contains the following text: [Manufacturer] %IBM%=IBMNTx86.5.1.0x1 ; models section [IBMNTx86.5.1.0x1] ; Section for XP Professional ; [IBM] Note: Make sure that the value of the %IBM% keyword matches the text contained in the section heading that follows. In addition, be sure to comment out the [IBM] section heading by preceding it with a semicolon (;). 3. Save the modified nfrd960.inf file. 4. Open the b57xp32.inf file in an ASCII text editor. This file is in the :\Program Files\Microsoft ADS\nbs\repository\User\Presystem directory, where is the drive letter of the hard disk drive where Microsoft ADS is installed. 5. Modify the [Manufacturer] section of the file so that it contains the following text: [Manufacturer] %BRCM% = Broadcom.NTx86.5.1 [ControlFlags] ExcludeFromSelect = * [Broadcom.NTx86.5.1] Note: Make sure that the value of the %BRCM% keyword matches the text contained in the section heading that follows. 6. Save the modified b57xp32.inf file. 7. Shut down and restart the ADS Deployment Builder before using the nfrd960.inf or b57xp32.inf file. 7.6 Problems with CD-based scenarios ------------------------------------- When you create a CD for a deployment scenario, be sure to enable all DOS 8.3 character file names in the ISO image. Otherwise, file names that contain characters such as the tilde (~), dollar sign ($), and number sign (#) might be renamed and cause the CD-based deployment scenario to fail. 7.7 Network-based installation on an eServer BladeCenter HS20, machine type 8832 with an IDE RAID controller --------------------------------------------------------------- You must use hypercfg version 3.6 when performing a network-based installation on an eServer BladeCenter HS20, machine type 8832 with an IDE RAID controller. To obtain the latest version of this utility, go to the IBM Support Page and search for "LSI Hyper Configuration Utility" for the eServer BladeCenter HS20, machine type 8832. Note: You can search specifically for hypercfg version 3.6, by the part number 26K9152. 7.8 Unknown device in Windows Device Manager with xSeries 206, machine type 8482 or xSeries 306, machine type 8836 and a Remote Supervisor Adapter II installed --------------------------------------------------------------- When an IBM Remote Supervisor Adapter II is installed in either an xSeries 206, machine type 8482 or xSeries 306, machine type 8836, the list of devices in the Windows Device Manager might contain an unknown device. This is expected, and a future Automatic Server Restart driver will remove this item from the list of devices. 7.9 Microsoft ADS does not start with xSeries 206, machine type 8482, xSeries 306, machine type 8836, or eServer BladeCenter HS40, machine type 8839 ----------------------------------------------------------------- The Intel(R) Ethernet device drivers that come with Windows Server 2003 do not support the following servers: o xSeries 206, machine type 8482 o xSeries 306, machine type 8836 o eServer BladeCenter HS40, machine type 8839 To solve this problem, you must complete the following steps to update the Ethernet device drivers in the Microsoft ADS device driver repository. 1. Copy the contents of the following directories on a ServerGuide CD 7.2.02 or later to the Microsoft ADS\nbs\repository\User\PreSystem directory on the server: o sguide\w2003drv\$oem$\textmode o sguide\w2003drv\$oem$\$1\drv\bc o sguide\w2003drv\$oem$\$1\drv\e2 2. Open the e1000325.inf file and find the section that contains the following text: [Manufacturer] %Intel%=Intel,NTx86,NTIA64 3. Change the information you found in step 2 to the following: [Manufacturer] %Intel%=Intel.NTx86 4. Save and close the e1000325.inf file. 7.10 Network not available after installation of Windows-based operating system to an eServer BladeCenter HS40, machine type 8839 -------------------------------------------------------------- After using ServerGuide Scripting Toolkit to install to an eServer BladeCenter HS40, machine type 8839, the Ethernet connections display as "unplugged". To solve this problem, you must obtain version 8.30 or later of the Intel-based Gigabit and 10/100 Ethernet adapters for Windows 2000 and Windows Server 2003. The ServerGuide CD 7.2.02 does not contain the latest drivers. After you obtain the latest drivers from the IBM Web site, see the "IBM ServerGuide Scripting Toolkit User's Reference, Version 1.0" documentation for information on how to update the device drivers used by ServerGuide Scripting Toolkit. Note: If you already used ServerGuide Scripting Toolkit to install a Windows-based operating system to an eServer BladeCenter HS40, machine type 8839, you can use the new Ethernet device drivers to update that system without re-installing the operating system. 8.0 ADDITIONAL FILES, UTILITIES, AND INFORMATION ------------------------------------------------- This section contains information that is not documented in the "IBM ServerGuide Scripting Toolkit User's Reference." 8.1 dumpcfg.bat ---------------- You can use the dumpcfg.bat file to list information about a ServeRAID controller or an integrated SCSI controller with RAID capabilities. Complete the following steps to use the dumpcfg.bat file: 1. Change to the \stkfiles\sg_stk\examples directory. 2. From a command prompt, type the following command and press Enter: dumpcfg where is either SRVD (ServeRAID) or SCSI (integrated SCSI controller with RAID capabilities), and is the controller number. The controller information is written to either the svrd.out file (ServerRAID) or the scsi.out file (integrated SCSI controller with RAID capabilities). The file is in the root of the RAM drive. You can use the controller information to configure the RAID variables in the usrvars.bat file. 3. After you modify the usrvars.bat file, restart (reboot) the server to restart the ServerGuide Scripting Toolkit process. 8.2 sleep.exe -------------- You can use the sleep command to stop a system for a specified time interval. After the time interval elapses, the system resumes operation automatically. The sleep command has the following syntax: sleep where is the number of seconds that the system stops. 8.3 Using the ServerGuide Scripting Toolkit with an existing deployment process ------------------------------------------------------------- You can incorporate ServerGuide Scripting Toolkit procedures into an existing deployment process. You can use the hwdetect command to determine whether a server is an IBM eServer or xSeries server. You then can add applicable branches in the batch file. For example, the following command sequence runs the hwdetect utility and returns information indicating whether the server is an IBM eServer or xSeries server. hwdetect.exe /s if errorlevel 1 goto NONIBM echo This is an IBM eServer or xSeries server goto FINISH :NONIBM echo This is not an IBM eServer or xSeries server :FINISH 8.4 Selecting a network interface card (NIC) device driver during a deployment scenario ----------------------------------------------------------- If you use one of the following deployment scenarios, you must select the device driver for the NIC when you start the target server from the DOS-startable (bootable) diskette: o Using a DOS-startable diskette and network share o Using a Remote Supervisor Adapter II and network share If the target server is an xSeries 440, machine type 8687, be sure to select "Broadcom NDIS network driver (xSeries 440 only)". If the target server is an eServer BladeCenter HS20, machine type 8832, be sure to select "Broadcom NDIS network driver (B57)". If the target server requires a Broadcom device driver and is neither an xSeries 440, machine type 8687 server nor an eServer BladeCenter HS20, machine type 8832 server, you can select either of the two Broadcom device drivers. 8.5 Additional steps required for creating a Microsoft ADS job template --------------------------------------------------------------- The following text replaces step 2 and step 3 of the "Creating a Microsoft ADS job template" section on page 32 of the "IBM ServerGuide Scripting Toolkit User's Reference, Version 1.0" documentation. 2. From the Microsoft ADS Console, expand the "Automated Deployment Services" tree. 3. Right-click Job Templates -> New Job Template. The "New Job Template" wizard starts, and the "Welcome to the New Job Template Wizard" window opens. 8.6 Limitations ---------------- The following limitations are applicable to this version of the ServerGuide Scripting Toolkit: o The "altboot /b" command does not work on the following servers: - xSeries 225, machine type 8647 - xSeries 225, machine type 8649 o The emm386.exe expanded memory device driver is not supported by the ServerGuide Scripting Toolkit. The following utilities and functions are incompatible with this device driver: - hwdetect.exe - savestat.exe - BIOS code updates - Firmware code updates o You cannot use this version of the ServerGuide Scripting Toolkit to configure automated BIOS code flash or firmware updates for the following systems: - xSeries 206, machine type 8482 - xSeries 306, machine type 8836 - eServer BladeCenter HS40, machine type 8839 o Linux operating systems are case-sensitive. Make sure that the case of the file and directory names matches the corresponding reference in any command sequence that refers to them, such as command sequences in usrvars.bat and netvars.bat files. ex. The default installation directory for ServerGuide Scripting Toolkit files is "sg_stk", so the TKDIR variable in usrvars.bat must be set to "sg_stk" and not "SG_STK". 9.0 SUPPORT WEB SITES ---------------------- The following Web pages provide resources for understanding, using, and troubleshooting IBM deployment and systems-management software: o IBM Remote Deployment Manager page http://www.ibm.com/servers/eserver/xseries/systems_management/ sys_migration/rdm.html This Web page provides an overview of IBM Remote Deployment Manager. o IBM ServerGuide http://www.ibm.com/pc/ww/eserver/xseries/serverguide/index.html This Web page provides an overview of ServerGuide. o IBM ServerGuide Scripting Toolkit page http://www.ibm.com/pc/support/site.wss/ document.do?lndocid=MIGR-53564 This Web page provides an overview of the ServerGuide Scripting Toolkit. You can download the latest version of the ServerGuide Scripting Toolkit readme.txt file here. o IBM ServerProven(R) page http://www.ibm.com/pc/us/compat/index.html This Web page provides compatibility information about hardware, software, and middleware. o IBM Support page http://www.ibm.com/pc/support/ This is the IBM Support Web site for IBM hardware and systems-management software. o IBM Systems Management Software: Download/Electronic Support page http://www.ibm.com/pc/us/eserver/xseries/systems_management/ dwnl.html Use this Web page to download IBM systems-management software, including the ServerGuide Scripting Toolkit. o IBM UpdateXpress http://www-1.ibm.com/servers/eserver/xseries/ systems_management/sys_migration/xpress.html This Web page provides an overview of UpdateXpress. It also contains links to pages from which you can download UpdateXpress, order an UpdateXpress CD, or purchase a subscription from a vendor other than IBM. o IBM xSeries Systems Management page http://www.ibm.com/pc/ww/eserver/xseries/systems_management/ index.html This Web page provides an overview of IBM systems-management software. 10.0 NOTICES AND TRADEMARKS ---------------------------- INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. The following terms are trademarks of the IBM Corporation in the United States, other countries, or both: BladeCenter eServer IBM ServerGuide ServerProven ServeRAID xSeries Adaptec and HostRAID are trademarks of Adaptec, Incorporated, in the United States, other countries, or both. Intel, Intel Inside (logos), MMX and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Red Hat, the Red Hat "Shadow Man" logo, and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc., in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others.