IBM(R) ServerGuide(TM) Scripting Toolkit, Windows Edition Version 9.20 (C) Copyright International Business Machines Corporation 2012. 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 for more information. o Check the ServerGuide Scripting Toolkit Web site for the latest version of this readme. See Support Web sites for more information. Updated February 14, 2012 |
System Enablement Packs add additional support to the ServerGuide Scripting Toolkit, Windows Edition. When a new System Enablement Pack is available for download consult the ServerGuide Scripting Toolkit, Windows Edition User Guide for information on how to download and install the System Enablement Pack into the ServerGuide Scripting Toolkit, Windows Edition.
ServerGuide Scripting Toolkit, Windows Edition 9.20 offers the following changes compared with the previous edition:
The ServerGuide Scripting Toolkit, Windows Edition supports the following deployment scenarios:
This section contains updates to information on solving ServerGuide Scripting Toolkit Problems developed since the publication of the IBM ServerGuide Scripting Toolkit Users Guide. Please consult the Users Guide for a full list of known solutions to ServerGuide Scripting Toolkit problems.
One final reboot is recommended after the Windows installation completes to finish the hardware installation. For instance, yellow exclamation marks may be present on the Intel(R) Ethernet Mezzanine Adapter due to the device driver being unable to start. This issue is resolved by a reboot.
The Toolkit uses the Microsoft Windows Imagex.exe utility during the generation of the Windows PE ISO. The Imagex.exe utility will fail during the creation of the deployment scenario if the Toolkit is installed to a mapped network drive or a USB device if it is formatted with anything other than the NTFS file system.
In order to install to a ServeRAID-8i or 8s adapter on a System x3800, you must perform the following steps:
After deploying Windows Server 2003 to an IBM BladeCenter LS21 or LS41, the system may be unable to connect to the network. This error can be caused by attempting to use a network device driver version prior to 3.7.19.0.
To avoid this problem, create your deployment image using ServerGuide 7.4.17 or higher. See "Adding Windows device drivers" in the Users Guide for information on adding device drivers to the source tree.
To correct the problem after deployment, you can update the device driver manually to 3.7.19.0 or higher.
PRAID is only supported for the IBM SAS HBA when it is connected to internal drives. This error is caused when the cfggen utility is unable to create a configuration.
To avoid this problem, update the firmware on the IBM SAS HBA controller to 1.25.10.07 or higher.
If the problem persists remove any logical volumes including RAID arrays on the adapters using the Ctrl+C menu on system POST before using ServerGuide Scripting Toolkit.
When using PRAID.exe to reset or configure a LSI 1064/1064e/1078 SAS controller or an IBM SAS HBA controller, you might receive error code 7 or 11. This error is caused when the cfggen utility is unable to remove or create a configuration.
To avoid this problem, remove any logical volumes including RAID arrays on the adapters using the Ctrl+C menu on system POST prior to using ServerGuide Scripting Toolkit.
When using a QLE2462 Fibre HBA on a System x3500, type 7977 and using ServerGuide to install the needed drivers for 32 and 64-bit Windows 2003 deployments, you must first add the type 7977 to the supported systems list included in the ServerGuide DrvInfo.ini file.
To modify this file, follow these steps:
On BladeCenter systems LS21 type 7971 and LS41 type 7972 with BIOS levels 1.05 and 1.06, local and network deployments will fail. This is a limitation of these BIOS levels.
To avoid this problem, use BIOS level 1.04, or a BIOS level higher than 1.06 on these systems.
This problem can occur when installing to a system with multiple storage adapters. Please see "Installing an operating system on a multi-adapter system" in Appendix D of the User's Guide for more information.
This problem can occur when installing to a system with multiple storage adapters. Please see "Installing an operating system on a multi-adapter system" in Appendix D of the User's Guide for more information.
When Emergency Management Services are enabled, an Administrator password is required for Windows 2003 installation IBM System x3610.
In order to complete an unattended installation of Windows 2003 on the x3610, you must include the Administrator password in the Windows 2003 answer file used for the installation.
System x3100 does not properly power on remotely using Altiris Deployment Solution because Wake-on-LAN is not supported.
The driver for network adapter 39Y6066 is not properly installed with any version of Windows Server 2003 on System x3610 type 7942. It will appear as a generic "Ethernet Controller" yellow bang in device manager.
Toolkit deployment tasks that include installation of UXSPs can return errors if the UXSPI attempts to install updates for hardware that is not present in the target system.
Look in the C:\IBM_Support\deployment\IBM_WinPEToolkit.log and C:\UXLOG\UX.LOG files on the target server. These files contain additional information on what updates the UXSP Installer attempted to apply to the target system. Return codes 171 and 172 in the file UX.LOG indicate an update that could not be installed because the applicable hardware was not present.
Altiris jobs might show an error after attempting to deploy UXSPs if the applicable hardware is not present in the target server. To determine whether this is the cause of the error, follow these steps:
If there is a line below
If the target server is accessible, check C:\UXLOG\UX.LOG on the target server. Return codes 171 and 172 in this file indicate an update that could not be installed because the applicable hardware was not present on the target server.
When installing Windows Server 2003 to a system with a fibre adapter, the installation can fail with the error message "QL2300.sys is corrupted. Press any key to continue."
To sucessfully install Windows Server 2003 to a system with a fibre adapter, you must use Windows Server 2003 with Service Pack 2.
Some system updates may result in boot issues, or may fail and require user intervention during automated Toolkit installs. Running the latest system updates acquired by UXSPI is not recommended on xSeries 206m or xSeries 226.
While performing a Windows installation you might encounter the following error message: "Windows cannot locate the disk and partition specified in the unattend answer file's <ImageInstall> setting". This error can occur for different reasons including the installation drive having previously been formatted as a GPT drive or having a different OS previously installed on the system.
To resolve this issue, first restart the system and retry the Windows installation. If this does not resolve the issue then delete all partitions and formatting on the drives in the system and retry the Windows installation. If this does not resolve the issue and the system has multiple storage adapters, please see "Installing an operating system on a multi-adapter system" in Appendix D of the User's Guide and the readme note for Windows Server 2008 Install with multiple RAID controllers for more information.
When performing a Windows installation, ServerGuide Scripting Toolkit attempts to install Windows on the first disk of the system presented by Microsoft's diskpart utility. Due to the limitations of the system, when multiple storage adapters are present on the system, the first disk presented by the diskpart utility is not always the the first disk on the system.
To avoid this problem, please remove all storage adapters and/or disks that are not required for the Windows installation.
While creating a deployment scenario with SGTKWinPE.cmd, the DISM utility may fail with a return code of 126. DISM fails if the path to the mounted Windows PE image is too long.
To resolve this issue, the path to the TK_Build_ScenarioOutputDirectory directory must be less then 120 characters. The TK_Build_ScenarioOutputDirectory directory is located at \sgdeploy\WinPE_ScenarioOutput\.
The computer name used for Windows installations must comply to Windows restrictions. If it does not, you will receive an error during unattended Windows 2008 installations saying: Windows could not parse or process the unattended answer file for pass (specialize). The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].
Clicking the broswe button when using the Scripting Toolkit Configuration Utility to copy files to the Toolkit source server may give a blank window without a folder browser. If this occurs, the source path of the files to copy must be typed directly into the source path input box.
If a deployment done through an IMM, AMM, or RSA-II remote module is left idle for an extended period of time, the remote system may hang after the next keyboard or mouse interaction. At this time unmount/remove the deployment media if instructed to do so in the command window. If the Toolkit deployment process is hung at a point where it is waiting for a key press to restart the system, reboot the remote system using the remote console and the install will proceed successfully. At any other point, the system must be rebooted via the remote console, and the deploymented restarted from the beginnning.
After the UpdateXpress System Pack Installer (UXSPI) runs on your system, the Toolkit log or UXSP log may reveal that UXSPI exited unexpectedly while installing an Intel chipset update. This is due to the package reporting completion while subprocesseses are still running. Those subprocess may utilize your system's resource at a level that causes other updates to fail. To avoid this issue, you may utilize the UXSPI exclude flag via the TK_UXSP_UXSPIUpdateFlags variable to remove any Intel packages by filename from the UXSP installation. To install the remaining hardware devices run your UXSP installation again without the exclusions, and the Intel package(s) will install successfully. If this error has already occurred, please re-run the UXSP installation, and the rest of the updates should complete successfully.
When installing to a drive that previously used GPT partitioning the operating system installation may fail. This failure is caused by an incomplete cleanup of the drive by Diskpart. To resolve this issue restart the system and retry the Windows installation or use Windows Preinstallation Environment 3.0, available in the Windows Automated Installation Kit for Windows 7, to perform the installation.
When performing an installation of Windows 2008 or Windows 2008 R2 using a non-English version of the OS, the unattended installation may be interrupted with a prompt to select the language and keyboard layout to use in the installed OS. To prevent this from happening set the TK_NOS_Win2008_UILanguage variable in your Scenario INI file to the correct setting for the installation. The value for TK_NOS_Win2008_UILanguage is used to populate the UILanguage node in the unattend.xml file. Possible values for this variable can be found in the 'culture' column at http://technet.microsoft.com/en-us/library/cc722435(WS.10).aspx
Windows Server 2003 Installs with a 49Y4220 or 42C1780 iSCSI adapter will fail without one of the following Microsoft hotfixes:
When specifying to include all the physical drives for a RAID level, you must ensure that the number of physical drives in the system is correct for the RAID level you are specifying.
When performing RAID configuration, a best practice is to ensure that all the disks connected to the RAID controller are the same size.
When installing Windows 2008 to a ServeRAID M5015, the installation may fail if the previous RAID level was RAID 5 or 60. To fix this issue, perform the installation again.
Installing any version of Windows Server 2003 64-bit with Service Pack 2 to
SATA drives connected to IBM SAS HBA on an IBM System x3455 or IBM System x3655 may fail.
To install any version of Windows Server 2003 64-bit with Service Pack 2
to SATA drive(s) connected to SAS HBA part number 25R8060 on an IBM System x3455,
or to an IBM System x3655 the planar SATA controller must be disabled in the BIOS.
To do this:
When installing Windows 2003 without Service Pack 2 included,
the "Everyone" group does not have the same permissions it would have if a retail install was performed.
To grant the "Everyone" group the same permissions as a retail install, perform the following steps:
A popup may be displayed while running a Toolkit scenario stating "You must restart your computer to apply these changes. Before restarting, save any open files and close all programs." If this occurs, click the button labeled "Restart Later" and continue the Toolkit scenario.
This is often indicated in the log or onscreen by a return code of 400 the first time the Toolkit attempts to launch the Director Agent, then a return code of 101 on the second attempt. To fix this issue please obtain and install the newer Windows Installer from the following link: http://support.microsoft.com/kb/942288.
After the installer is updated, either run the Director Agent installer manually on your system, or run the 'IBM Director Agent for Windows Install' job if your installation was performed via Altiris DS.
When using a USB Key to perform a deployment scenario, the USB Key might not boot in Legacy mode. This is usually
indicated by a black screen with a blinking cursor in the upper left corner of the screen.
To work around this issue, use one of the following alternatives:
DScan can hang if a driver is injected that has section names in the txtsetup.oem file that differ from eachother in case. To fix this condition, ensure that all the section names are identical, including in case.
A popup may be displayed while installing Windows 2008 with Director Agent 6 as "wscancfg.exe has stopped working". This error can occur when any service program needed by Director Agent 6 is not active. At that time, you can close the error message box directly to coutinue installing Windows 2008 & Director Agent 6.
A warning might be shown "administrator pwd needs to be modified" in the dash board after the Windows 2011 SBS deployment finished. It won't affect the usage because the Windows 2011 SNS will ask the user to create a new administrator account during the installation.
When deploying Windows OS in legacy boot mode to external storage device connected via Broadcade 16Gb Fibre Channel Mezz card, you might need to change the Lun discovery at Brocade bios (Ctrl+b or Alt+b) to "Flash Values" or "FirstLUN" first.
This section contains information that is not documented in the IBM ServerGuide Scripting Toolkit User's Reference.
The Electronic Service Agent is a no-charge software tool that resides on your IBM System xTM systems to monitor hardware events and transmit system inventory information to IBM. With these functions, this software can proactively monitor, track and capture system inventory and hardware errors. Follow this link to download the IBM xSeries Electronic Service Agent: http://www.ibm.com/support/electronic
The following Web pages provide resources for understanding, using, and troubleshooting IBM deployment and systems management software:
The ServerGuide Scripting Toolkit is a collection of system-configuration tools and installation scripts that you can use to deploy software to your IBM servers in a repeatable, predictable manner.
http://www.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=SERV-TOOLKIT&brandind=5000008
IBM ServerGuide is a tool that simplifies the process of installing and configuring IBM System x and BladeCenter servers.
The IBM System x® ToolsCenter is a collection of server management tools to help manage your IBM System x and BladeServer environment.
http://www-947.ibm.com/support/entry/portal/docdisplay?brandind=5000008&lndocid=TOOL-CENTER
The IBM ToolsCenter for System x and BladeCenter Information Center contains all the information that you need to deploy, configure, update, and diagnose your IBM System x and BladeCenter products.
The IBM ServerProven® program validates selected products for compatibility with IBM System x, BladeCenter, and xSeries servers.
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.
IBM UpdateXpress can help reduce your cost of computing by providing an effective and simple way to update device drivers, server firmware and firmware of supported options contained within the server on most of your System x and BladeCenter products.
http://www.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=SERV-XPRESS&brandind=5000008
The IBM Support Web site for IBM hardware and systems management software.
This Web page provides an overview of IBM systems management software.
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.
This Program is licensed under the terms of the agreement located in the directory named ...\sgdeploy\SGTKWinPE\Docs\license. By installing, copying, accessing, or using the Program, you agree to the terms of this agreement. If you do not agree to the terms, please uninstall the software and return it to IBM or the reseller from whom you acquired the software for a refund, if any.
Additional licenses are included with each System Enablement Pack located in the ...\sgdeploy\updates\uxsp\ibm_utl_tsep*.zip.
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
ServeRAID
ServerGuide
ServerProven
System x
TotalStorage
xSeries
IBM is a trademark of International Business Machines Corporation in the United States, other countries, or both.
Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.
Linux is a trademark of Linus Torvalds in the united states, other countries, or both.
Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.