HP 370971-004 manual Rem

Page 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 first Script called from Startnet.cmd stub in the WinPE

REM

REM Make sure that the network is fully started...

REM Sometimes it requires a bit of time ipconfig

REM Map a drive to the share you are working from.

REM If none ignore this step and set the drive letter in REM the following statements to appropriate drive REM============================================================ set Tools=s:\tkdemoarea\HP\Tools

set MSTools=X:\i386\system32

set GlobalData=s:\tkdemoarea\HP\DeploymentScripts\datafiles set MSDistribution=s:\tkdemoarea\w2k3entsp1

set HPQFlatFiles=s:\tkdemoarea\hpqflatfiles set HPQComponents=s:\tkdemoarea\ntcsp

set SystemScripts=s:\tkdemoarea\HP\DeploymentScripts REM============================================================ net start sysmgmt

REM Call the first Script

call %SystemScripts%\ServerDetect.cmd

echo Done!

2.If needed, modify the SERVERDETECT.CMD file for your specific environment. This file is provided in the samples subdirectory. SERVERDETECT.CMD does not accept any arguments. It runs the HWDISCOVERY utility to determine the server type and then executes a typical deployment script (DEPLOYSERVER.CMD).

3.Edit the DEPLOYSERVER.CMD file for your specific environment.

NOTE: The IFHW and HWQUERY utilities can be used to assist in customizing the DEPLOYSERVER.CMD script for your environment. For more information about these utilities, refer to the HP SmartStart Scripting Toolkit Linux and Win32 Editions User Guide.

The DEPLOYSERVER.CMD file is similar to the following:

rem @echo off cls

echo [ SCRIPT FOR REMOTE INSTALL OF W2K3 ON TYPICAL SERVER ]

pause

echo Retrieving State Information...

%Tools%\System\statemgr /r phase

if errorlevel 3 goto State3 if errorlevel 2 goto State2 if errorlevel 1 goto State1

Configuring HP ProLiant systems with Windows PE 11

Image 11
Contents HP SmartStart Scripting Toolkit Win32 Edition Best Practices Page Contents Minimum requirements IntroductionWin32 Toolkit overview Toolkit changesWindows PE build process Microsoft Windows Preinstallation EnvironmentXcopy /s /e PathToWinPEFiles\WinPE\*.* WinPEBuildTools Booting Windows PE from a USB drive key Unattended configuration using startnet.cmd Configuring HP ProLiant systems with WindowsOverview of configuring HP ProLiant systems with Windows PE Creating required data files with Windows PE Conrep /S A\HWCONFIG.XMLCpqacuxe /C A\PL-RD.INI Creating script filesREM Goto NEXT6 NEXT4 Goto NEXT6 NEXT1Goto NEXT6 NEXT2 Goto NEXT6 NEXT3NEXT5 ADPU160M.SYS CPQARRY2.SYS CPQCISSM.SYS State4SNMP=1 WBEMSNMP=1 TXTSETUP.OEMStartdeploy.cmd CD-based Windows PE deploymentNetwork-based Windows PE deployment PXE-based Windows PE deploymentConfiguring HP ProLiant systems with Windows PE HP contact information Technical supportReference documentation Toolkit supportAcronyms and abbreviations WDM Index