Summary of the content on the page No. 1
HP SmartStart Scripting Toolkit Win32 Edition
Best Practices
October 2005 (Fourth Edition)
Part Number 370971-004
Summary of the content on the page No. 2
© Copyright 2004, 2005 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from HP requi
Summary of the content on the page No. 3
Contents Introduction.................................................................................................................................. 4 Win32 Toolkit overview............................................................................................................................. 4 Toolkit changes......................................................................................................................................... 4 Minimum requirements...............
Summary of the content on the page No. 4
Introduction In this section Win32 Toolkit overview............................................................................................................................ 4 Toolkit changes........................................................................................................................................ 4 Minimum requirements.............................................................................................................................. 4 Win32 Tool
Summary of the content on the page No. 5
Microsoft Windows Preinstallation Environment In this section Overview of the Microsoft Windows Preinstallation Environment.................................................................... 5 Windows PE build process ........................................................................................................................ 5 Booting Windows PE from a USB drive key................................................................................................. 7 Overview o
Summary of the content on the page No. 6
The following table describes the directories and paths that you must define for the Windows® PE base image build procedure. Directory or path Description WinPEBuildTools Build location for the Windows® PE tools PathToWinPEFiles Path to the original Windows® PE files PathToOSFiles Path to the operating system CD or directory WinPE_Directory Target directory where the flat Windows® PE image will be created OptionalComponentsDirectory Target directory where the Windo
Summary of the content on the page No. 7
To simplify the process of customizing the Windows® PE image with the latest ProLiant drivers, the Win32 edition of the Toolkit provides a driver component that automatically registers and copies the drivers to the appropriate folders. User interaction is still required to set up the Windows® command prompt (CMD.EXE) environment. To extract the component: • Locate the compressed file, which is a self-extracting executable. • Double-click the self-extracting executable, and select Extract
Summary of the content on the page No. 8
Configuring HP ProLiant systems with Windows PE In this section Overview of configuring HP ProLiant systems with Windows PE.....................................................................8 Unattended configuration using startnet.cmd ............................................................................................... 8 Creating required data files with Windows PE............................................................................................. 9 Creating script
Summary of the content on the page No. 9
(http://www.microsoft.com/licensing/programs/sa/support/winpe.mspx). For more information about the net use command, enter net help use at the command prompt. Because startnet.cmd is stored in the WinPE_Directory\Platform\system32 directory, command files listed in startnet.cmd are relative to the directory. Use the default system variables SystemDrive and SystemRoot to specify paths to the utilities. Be sure that the contents of the file are accurate and tested before using it widely.
Summary of the content on the page No. 10
This command reads the current configuration on the source server and writes the hardware configuration data file to A:\HWCONFIG.XML. 2. Generate the array configuration data file with the following command: CPQACUXE /C A:\PL-RD.INI This command reads the array configuration on the source server and writes the array configuration data file to A:\PL-RD.INI. 3. Create the partition configuration data file. A sample DISKPART0.TXT file is provided with the Toolkit in the samples directory.
Summary of the content on the page No. 11
1. STARTDEPLOY.CMD is a script file that is executed by STARTNET.CMD in Windows PE. Edit the STARTDEPLOY.CMD file to modify the environment variables to match the locations of the utilities and data files specific to your deployment infrastructure. You must customize this file for your environment. In the following example, bold lines indicate information that must be modified for your environment. The STARTDEPLOY.CMD file is similar to the following: rem @echo off REM REM This is the
Summary of the content on the page No. 12
if errorlevel 0 goto State0 :State0 REM *** Configure the target server hardware by reading the configuration REM *** information in the script file echo Running Configuration Replication Utility... %Tools%\System\conrep -l -f%GlobalData%\HardwareSettings\hwconfig.xml - x%Tools%\System\conrep.xml echo Setting State Information... %Tools%\System\statemgr /w Phase 1 :State1 REM======================================================================== REM *** Configure the array
Summary of the content on the page No. 13
:NEXT5 %Tools%\System\ifhw .\hwdisc.xml %Tools%\System\allboards.xml PCI:"HP 6 Port SATA RAID Controller" if errorlevel 1 GOTO NEXT6 .\Adaptec\bin\arcconf.exe ***Fill in command options*** :NEXT6 pause REM======================================================================== REM *** Configure the iLO if iLo Present REM *** echo configuring iLO is present REM======================================================================== rem %Tools%\System\ifhw .\hwdisc.xml %Tool
Summary of the content on the page No. 14
REM *** Start installation of the operating system from the hard drive of REM *** the target system, reading unattended installation instructions from REM *** the C:\UNATTEND.TXT file REM======================================================================== %MSDistribution%\i386\winnt32 /s:%MSDistribution%\i386 /unattend:c:\unattend.txt /syspart:c %Tools%\System\reboot c: :State4 4. Modify the Windows Server 2003 SP1 UNATTEND.TXT sample file to fit your deployment requirements. In
Summary of the content on the page No. 15
MegaIDE.sys Symmpi.sys LsiCsb6.sys HPCISSs2.sys AAC.sys TXTSETUP.OEM [GuiUnattended] AdminPassword=password AutoLogon=Yes AutoLogonCount=1 OEMSkipRegional=1 OemSkipWelcome=1 TimeZone=20 [UserData] ComputerName=TEST FullName=HP OrgName=HPQ ProductID=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx [Proxy] Proxy_Enable=0 Use_Same_Proxy=0 [LicenseFilePrintData] AutoMode=PerServer AutoUsers=999 [GuiRunOnce] "c:\ntcsp\setupex.exe /smartstart" [RegionalSettings] Language=00000409
Summary of the content on the page No. 16
[SNMP] Community_Name=Public Traps=Localhost Accept_CommunityName=public Send_Authentication=yes [TerminalServices] ApplicationServer=0 PermissionsSetting=0 [Display] AutoConfirm=1 BitsPerPel=16 ConfigureAtLogon=0 VRefresh=60 Xresolution=800 Yresolution=600 [OEM_Ads] Logo=Compaq.bmp 5. Use the latest version of SmartStart to obtain supported drivers for new hardware devices. Also, add lines to copy the new devices and add the new devices to the UNATTEND.TXT and TXTSETUP
Summary of the content on the page No. 17
PXE-based Windows PE deployment This section describes how to use a PXE server to boot Windows® PE through a network. Review the server specification to determine whether PXE is supported on the target server. Currently, the Microsoft® RIS server is the only PXE server officially supported by Microsoft® with Windows® PE. Third-party PXE servers have not been validated with Windows® PE. Refer to RIS documentation for information about setting up and using RIS. NOTE: Using a PXE server
Summary of the content on the page No. 18
ISO image. If STARTDEPLOY.CMD is used to create a connection to a network resource, the file must exist on the CD. 4. Build an ISO image using the Windows® PE folder. 5. Create a Windows® PE CD using the ISO image. Configuring HP ProLiant systems with Windows PE 18
Summary of the content on the page No. 19
Technical support In this section Reference documentation ........................................................................................................................ 19 Toolkit support ....................................................................................................................................... 19 HP contact information............................................................................................................................ 19 Refe
Summary of the content on the page No. 20
Acronyms and abbreviations ADO ActiveX Data Objects API application program interface EA Enterprise Agreement HTA HTML applications iLO Integrated Lights-Out MBR master boot record OEM original equipment manufacturer PnP plug and play PXE Preboot Execution Environment RILOE II Remote Insight Lights-Out Edition II RIS Remote Installation Services SAM Software Assurance Membership Acronyms and abbreviations 20
