SmartSetup Scripting Toolkit Deployment Guide for HP Integrity Servers with Microsoft Windows Server 2003 for Itanium-based Systems
Table Of Contents
- SmartSetup Scripting Toolkit Deployment Guide
- Table of Contents
- About This Document
- 1 Overview
- 2 Creating a server profile
- 3 Setting up the toolkit environment
- 4 Setting up the boot mechanism
- Using a bootable CD/DVD
- Using a USB flash device
- Using network boot
- Interrupting the SSTK deployment process
- 5 Utilities Reference

-elilo.conf: configuration file for the Linux boot loader
-elilo.efi: Linux boot loader
-linux: Linux kernel
-rootfs.gz: Linux root file system in a compressed file
• The data_files directory is a placeholder that is used to store drivers and software that is
installed when a deployment occurs.
- acu.ini: The captured RAID configuration file. This file is created when the
readhwconfig option is executed on a target server with a supported
RAID controller. The acu.ini file is read when the
windows-setup.sh script is executed. This file is not included in the
sample file structure.
-conrep.dat: The conrep EFI variables output file. This file is created when the
readhwconfig option is executed.
-hba.ini: The hpqlarep configuration file, used to enable or disable the EFI boot
setting on QLogic HBAs. This file is also captured when the
readhwconfig option is executed, and applied before installing
Windows.
-drivers: Placeholder directory that you can populate with OEM driver files. For
example, to properly load the Intel NIC drivers, you must place the
drivers in the following directory:
Network/intelNIC/windows/2003-enterprise/
other-files/$OEM$/$1/PnPDrivers/Network/intelNIC/
-software: Placeholder directory that you can populate with applications that will
be copied to the HP Service Partition or Windows tools that will be
installed after the OS is first loaded. Files placed under
software\EFI_TOOLS will be automatically copied to the HP Service
Partition.
NOTE: When using SSTK in a SAN (storage area network) environment, be careful when
updating acu.ini. Doing so can result in modifications to storage controller configurations
seen on other machines, besides the one on which you are running SSTK. ACU configurations
are applied during “win” option execution
• The os directory contains a sample unattended installation answer file, which you can
customize for your deployments.
• The scripts directory contains the following shell scripts (typically, you can edit the bold
blue scripts but not the underlined red scripts):
-capture.sh: Runs the conrep, acu, and hpqlarep utilities,
capturing the hardware configuration and saving the
results in the repository under the data_files
directory.
-deploy.sh: Replicates the captured information from the
repository to the target system.
-main_toolkit_launch.sh: The main script in the toolkit sets up the toolkit
environment by setting environment variables,
creating a RAMdisk, copying scripts and utilities into
the RAMdisk, running I/O hardware inventory, and
prompting the user to select a deployment task.
-windows-setup.sh: Launches Windows installation by creating and
formatting disk partitions, copying the OS files to the
MSDATA partition, copying the setup loader (
Unpack the toolkit 19