I have a PXE server for deploying Windows XP and Windows 7 to workstations. The process is as follows:. Boot the workstation from the NIC. Workstation sends a DHCP request. DHCP server responds with an IP address and the location of the PXE server. Workstation downloads WinPE image file from PXE server via TFTP.
Workstation stores WinPE image file in memory and executes it. Once booted into WinPE, I connect to a network share to gain access to either the Windows XP or Windows 7 installation files. A custom script is launched to guide you through the process of formatting and partitioning the hard drive(s) (using DISKPART and FORMAT).
Another custom script asks for details such as the hostname to assign to the workstation. The answers provided are used to build an unattended answer file (SIF Setup Information File for WinXP and XML for Win7). The Windows setup EXE is launched, passing the unattended answer file to it as a parameter. The Windows XP and Windows 7 installation sources have been customised to include the drivers for our Dell workstations. They also run a number of scripts upon first booting up to install software packages. This process works very well for our workstations and I would now like to use it for building our servers too.
Utility for Windows SmartStart Scripting Toolkit Win32 Edition SmartStart Scripting Toolkit Win64 Edition HP. HP SmartStart CD x32 HP SmartStart CD x64 HP.
Installing Windows on HP Proliant. Installs various HP Tools for Windows (HP Array. I’ve been reading through the SmartStart Scripting Toolkit. HP SmartStart Scripting Toolkit Windows Edition ユーザ ガイド 製品番号 415598-194 2007年5月（第4版）.
The vast majority of our servers are HP Proliant DL360 G6, DL380 G5 and DL380 G6. They’re running Windows Server 2003 (various editions) or 2008 (various editions).
To date, we have always built the HP Proliant servers using the SmartStart CD provided. SmartStart does three useful things for us:. Setup RAID with HP Array Configuration Utility (ACU).
Installs and configures SNMP. Installs various HP Tools for Windows (HP Array Configuration Utility, HP Array Diagnostic Utility, HP Proliant Integrated Management Log Viewer, etc) Using SmartStart I have never had to manually download and install Windows drivers for network, sound, video, etc. I'm not sure if this is because SmartStart copies drivers from the CD during setup, or whether Windows just has the drivers natively in its driver CAB. If I abandon the SmartStart CD in favour of my PXE server I would have to do the following:. As I wont have access to ACU, I'll configure the RAID (before booting to the PXE server) by pressing F8 (during the boot process) to access Option ROM Configuration for Arrays (ORCA). Installation of SNMP and the HP Tools will have to be installed once the Windows installation is complete using the Proliant Support Pack. Is this method OK?
Is there anything that the SmartStart CD does that I'll be unable to do by other means? Are there any disadvantages to not using the SmartStart CD?
UPDATE 05/01/12 I’ve been reading through the SmartStart Scripting Toolkit documentation. The scripting toolkit contains command line tools which work within WinPE and can such things as configure BIOS settings, configure an array and setup ILO. I’m personally not too bothered about configuring BIOS settings as I rarely deviate from the defaults (unless the server is to be a Hyper-V host). I’m not too fussed about being able to configure the array from within WinPE, as I’m happy to just press F8 and use Option ROM Configuration for Arrays (ORCA). Although, if it’s easy enough to do, I will explore this further, as it saves time if everything can be configured from within WinPE. One of the nice features all the tools possess is that you can pass input files to them. Configure one server to your requirements, capture its configuration to a file (using the appropriate tool), you can then use the tool on other servers passing the input file with the captured configuration.
Array controller drivers appear to be included with the toolkit along with example of how to incorporate them within a WinPE build. I suppose WinPE won’t be able to see logical volumes (I.E 2x physical disks in a RAID 1 configuration) without the array controller drivers? I mentioned in my post that SmartStart normally installs a bunch of Windows HP tools for you.
I’ve had a look today, and if you run the SmartStart CD from within Windows all the tools can be installed. Therefore I can do this after the Windows installation is complete. The SmartStart CD appears to contain a lot Windows drivers. I can customise my Windows 2008 source to incorporate these drivers. However, I understand that incorporating an array controller driver is a little different to most drivers.
I believe that you have to provide the driver during the very early stages of the Windows setup. I’m working through the Scripting Toolkit documentation to try and work this out. Just wanted to bring this post to rest. I am now successfully building HP Proliant servers without the SmartStart CD. I incorporated the drivers from the SmartStart Scripting Toolkit into my WinPE WIM file. I tested booting to WinPE before and after adding the drivers, the only difference seemed to be that WinPE couldnt see the NIC before adding the drivers.
Once Windows Server 2008 has finished installing, I have configured runonceex to launch the Proliant Support Pack to install tools and drivers upon first logging in. – Feb 23 '12 at 23:13. We have done this many times. You can look at HP RDP (HP remote deployement) wich come with many images to remote install via (PXE) i do not remember all the details. But i know it s doable. You can take the images from RDP and follow the tasks they do before/after the install image the end system is exactly the same as if you ve done the installation with smartstart ps. I ve found the smartstart scripting toolkit document hard to follow.
Copying the images and install setps from HP RDP was easier for me.
. HP SmartStart Scripting Toolkit Windows EditionUser GuidePart Number 415598-403June 2010 (Twelfth Edition). © Copyright 2005, 2010 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 expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HPshall not be liable for technical or editorial errors or omissions contained herein.Confidential computer software. ContentsIntroduction. 6SmartStart Scripting Toolkit. 6Microsoft Windows Preinstallation Environment. 6Minimum requirements.
RBSURESET return codes. 30Using HPDISCOVERY. 30HPDISCOVERY command-line syntax. 31HPDISCOVERY command line arguments.
LO100CFG return codes. 64LO100CFG command file contents. 66Troubleshooting table. IntroductionSmartStart Scripting ToolkitThe SmartStart Scripting Toolkit is a server deployment product that delivers an unattended automatedinstallation for high-volume server deployments.
This document describes how to best utilize the Toolkit toconfigure HP ProLiant servers. It also contains information about the Toolkit utilities and how to use them inan unattended environment. This document does not include information about installing the operatingsystem.Microsoft® Windows® Automated Installation Kit for Windows Vista® SP1 and Windows Server®2008 (for the creation of Windows® PE 2.1) or Microsoft® Windows® Automated Installation Kitfor Windows 7 and Server® 2008 R2 (for the creation of Windows® PE 3.0). Deployment using the SmartStart ScriptingToolkitDeployment overviewThe SmartStart Scripting Toolkit includes a set of utilities for configuring and deploying servers in acustomized, predictable, and unattended manner. These utilities enable you to duplicate the configurationof a source server on target servers with minimal user interaction.IMPORTANT: ProLiant 100-series servers do not support all toolkit commands, and those thatare supported might not work as expected. For information on automating deployments, see the 'Advanced topics (on page 13)' section ofthis document.Creating a network shareTo create a network share:1.Download the appropriate SmartStart Scripting Toolkit SoftPaq from the Toolkit website(The Windows® Toolkit is available in both 32- and 64-bitversions.2.Install the Toolkit SoftPaq on a common server that resides on the same network as the servers to bedeployed.3.
Adding drivers to Windows PE 2.1The SmartStart Scripting Toolkit contains HP drivers that are to be used with Windows® PE 2.1. Thedrivers are located in the hpDrivers directory of the SmartStart Scripting Toolkit. Run the executable file inthis directory, and then select the Extract button to extract the drivers to a location to be used in thefollowing steps.You can add drivers to WinPE either offline or online.To add drivers offline:1.Apply the base image (Winpe. For example:dism /image:C: SSSTK.TMP /Add-Driver/driver:C: ssstk hpDrivers example.inf3.For each additional device driver repeat steps 1 and 2.
When you finish customizing the image,prepare the image for deployment by using the peimg /prep command.NOTE: If the appropriate iLO driver is not installed some utilities do not work correctly.To add drivers online:1.Use the drvload tool, drvload.exe infpath, where infpath is the path to a device driver INF file.drvload x: hpDrivers example.inf2. You cannot capture and apply Lights-Out settings using HPONCFG in the same fashion as CONREP andHPACUSCRIPTING.
Hp Smartstart Iso
For more information, see 'Using HPONCFG.' IMPORTANT: Because the -w argument does not capture certain types of information, such asthe administrator password, data files created with HPONCFG using the -w argument cannotthen be used as input files for HPONCFG, unless they are modified first.Configuring the target server and installing the operating system1.
Advanced topicsOverviewThe advanced topics addressed in this section cover some of the most common deployment tasks that canbe automated using the Toolkit.IMPORTANT: The script files and script segments in this section are provided only asexamples. You must modify the scripts for your environment. When creating or modifyingyour own scripts, the pause command is a valuable tool to help you determine that eachstep of the script is functioning as desired. RAID 5 ADG setting.
The following example demonstrates how to use IFHW to detect a particular card ordevice:REM. Configure the array controllers by reading the configurationREM. information in the script file and stamping it onto the arrayREM. controllers of the target serverecho Configuring the Array Controllers.ifhw. Hpdiscovery.xml allboards.xml PCI:'Smart Array 5i Controller'if errorlevel 1 GOTO NEXT1. ACU bin hpacuscripting.exe -i.
ArraySettings SA5iArray.ini:NEXT1ifhw. See the operating system documentation for a complete description of the options that can be modified inthe unattended installation file to customize the installation. To perform an unattended operating systeminstallation and add mass-storage drivers:1.Using a standard text editor, create or modify the following additional Toolkit files for the unattendedinstallation:a. Edit the STARTDEPLOY.CMD file, which is executed by STARTNET. HPDISCOVERY utility to determine the server type, and then executes a typical deployment script(DEPLOYSERVER.CMD).REM @echo offcd%tools%%Tools% System hpdiscovery -f hpdiscovery.xml%Tools% System ifhw hpdiscovery.xml%Tools% System allboards.xmlHWL:SystemName eq 'ProLiant DL380 G2'if errorlevel 1 goto NEXT1call. Typical.cmdgoto end:NEXT1%Tools% System ifhw hpdiscovery.xml%Tools% System allboards.xmlHWL:SystemName eq 'ProLiant ML370'if errorlevel 1 goto NEXT2call. rem @echo offclsecho SCRIPT FOR REMOTE INSTALL OF W2K3 ON TYPICAL SERVER REM pauseecho Retrieving State Information.%Tools% System statemgr /r phaseif errorlevel 3 goto State3if errorlevel 2 goto State2if errorlevel 1 goto State1if errorlevel 0 goto State0:State0REM.
Configure the target server hardware by reading theREM. configuration information in the script fileecho Running Configuration Replication Utility.%Tools% System conrep -l f%GlobalData% HardwareSettings hwconfig. if errorlevel 1 GOTO NEXT2%Tools% ACU bin hpacuscripting.exe -i%GlobalData% ArraySettings pl-r1.iniGOTO NEXT5:NEXT2%Tools% System ifhw hpdiscovery.xml%Tools% System allboards.xmlPCI:'Smart Array 5312'if errorlevel 1 GOTO NEXT3%Tools% ACU bin hpacuscripting.exe -i%GlobalData% ArraySettings pl-r1.iniGOTO NEXT5:NEXT3%Tools% System ifhw hpdiscovery.xml%Tools% System allboards.xmlPCI:'Smart Array 640X Controller'if errorlevel 1 GOTO NEXT4%Tools% ACU bin hpacuscripting. REM. REBOOTif necessary%Tools% System reboot PXE:State2REMREM.
Create partition by reading content of the script file andREM. stamping the configuration onto the hard drive in theREM. target serverREMecho Creating Disk Partition.%MsTools% DiskPart /s%GlobalData% diskPart0.txtecho Formatting Disk Partition.
add mass-storage drivers, you must modify the MassStorageDrivers and the OEMBootFilessections.You can also use Microsoft® Setup Manager to help you create a custom UNATTEND.TXT file. Formore information on this process, see 'HOW TO: Use Setup Manager to Create an Answer File inWindows Server™ 2003 (on the Microsoft®website.
ADPU160M.SYSCPQARRY2.SYSCPQCISSM.SYSMegaIDE.sysSymmpi.sysLsiCsb6.sysHPCISSs2.sysAAC.sysTXTSETUP.OEMGuiUnattendedAdminPassword=passwordAutoLogon=YesAutoLogonCount=1OEMSkipRegional=1OemSkipWelcome=1TimeZone=20UserDataComputerName=TESTFullName=HPOrgName=HPQProductID=xxxxx-xxxxx-xxxxx-xxxxx-xxxxxProxyProxyEnable=0UseSameProxy=0LicenseFilePrintDataAutoMode=PerServerAutoUsers=999GuiRunOnce'c: ntcsp setupex. TSClients=OnTSEnable=OnNetworkingInstallDefaultComponents=YesIdentificationJoinWorkgroup=WORKGROUPNetOptionalComponentsSNMP=1WBEMSNMP=1SimpTCP=1SNMPCommunityName=PublicTraps=LocalhostAcceptCommunityName=publicSendAuthentication=yesTerminalServicesApplicationServer=0PermissionsSetting=0DisplayAutoConfirm=1BitsPerPel=16ConfigureAtLogon=0VRefresh=60Xresolution=800Yresolution=600OEMAdsLogo=Compaq.bmp3. NOTE: Booting from a USB drive key is supported only on certain ProLiant servers. For moreinformation, see the HP Insight Foundation suite for ProLiant website(boot Windows® PE from a USB drive key, see the Microsoft® Windows® PE documentation. REM -if errorlevel 3 goto HWNOTFOUNDif errorlevel 2 goto REBOOTREQUIREDif errorlevel 1 goto NEXT2goto endNEXT2:REM -REM Example of Option Rom Flash for a SmartArray 5i ControllerREM -System ifhw hpdiscovery.xml System allboards.xml PCI:'Smart Array 5i Controller'if errorlevel 1 goto NEXT3REM -REM This section performs the Option ROM Flash.
Hp Smartstart Download X64
Online Flash componentsREM are kept in a directory called RomsREM -Roms cp002238. 2.Use ACU to erase the array configurations:hpacuscripting -i erase.iniThe erase.ini file is provided in the Toolkit sample files. Toolkit utilitiesSyntax conventionsSyntax refers to the way a command and parameters must be entered. Unless specified otherwise, entercommands, parameters, and switches in all uppercase or all lowercase letters.Sample syntax line:SAMPLE/R -RDRIVE:PATHFILENAME.Command elementMeaningSAMPLESpecifies the name of the command. Indicates a component of the command line. Enter onlythe information within the brackets, not the bracketsthemselves. Utility online helpMost Toolkit utilities include usage instructions.
To obtain help with the syntax, parameters, and switchesof a particular Toolkit utility, enter the file name followed by /? In the command line. For example, forusage instructions on the CONREP utility, enter the following command:CONREP /?The utility displays information about its command line syntax, argument, and switches.
Command line argumentDescriptionthe next reboot, and the system is restarted. If no argument is provided,then the system is set to boot using the defined boot order./?This argument displays help information.REBOOT return codesThere are no return codes for the REBOOT utility.REBOOT command-line examplesCommand-line argumentDescriptionREBOOT A:This command reboots the system to the A: drive.REBOOT PXEThis command reboots the system by itself to the PXE NIC. SETBOOTORDER return codesValueMeaning0The boot order was set successfully.SETBOOTORDER command-line examplesCommand-line argumentDescriptionSETBOOTORDER cdrom hd pxe usb floppyThis command sets the system devices to boot inthis order: CD-ROM drive, hard drive, PXE,USB, diskette drive.SETBOOTORDER defaultThis command sets the boot order to the factorydefault.Using STATEMGRThe STATEMGR utility enables the user to keep track of the execution state during system reboots.