Understanding the Deployment Server Directory Structure

When you install the ProLiant Integration Module for Deployment Server, the directory .\Deployment Server is populated with the tools, scripts, and configuration files.

Table 9.3 provides an overview of the directory structure for .\Deployment Server .

Table 9.3. Deployment Server Directory Structure

Reference Name	Directory Path	Directory Description
Images	.\images	Contains the default image files created during an image capture task or deployed during an image deployment task
Configurations	.\deploy\ configs	Contains hardware, array, and partitioning configuration files
Tools	.\deploy\tools	Contains various applications used specifically for Rapid Deployment Pack not provided by the SmartStart Scripting Toolkit
Scripts	.\deploy\tools\scripts	Contains operating system-specific batch files
SmartStart Scripting Toolkit	.\deploy\tools\ssst	Contains the SmartStart Scripting Toolkit, which includes the SmartStart Scripting Toolkit documentation
Windows OS Files	.\deploy\cds\windows	Contains the Windows operating system files for system-specific scripted installation
Linux Boot Files	.\deploy\cds\compaq\ss. xxx \ yyyy [*]	Contains Linux-specific installation kernels and initial RAM disk images for starting the operating system-specific scripted installation
Documentation	.\docs	Contains Rapid Deployment Pack ”Windows Edition documentation

^[*] where xxx represents the ProLiant Support Pack version installed and yyyy represents the operating system/distribution shortcut name

Images

When performing the Capture Hardware Configuration and Image jobs and Deploy Hardware Configuration and Image jobs for both Windows and Linux, the image files are saved in this directory. These provided jobs use the default image file, wincap.img for Windows and lnxcap.img for Linux, which is specified within the imaging tasks of the jobs. If you use the jobs without modification, each time you capture a new image it will overwrite the previous image. To capture or deploy images for different server configurations, you must copy and rename the jobs, then modify the image file name in the imaging task so that the files are saved with a unique name.

Configurations

The various initialization files for setting the server hardware, array, and drive partitions during the scripted installation jobs are found in this directory.

When performing the Capture Hardware Configuration and Image and Deploy Hardware Configuration and Image jobs, the default initialization files representing hardware configuration and array configuration are WINCAP-H.INI and WINCAP-A.INI for Windows and LNXCAP-H.INI and LNXCAP-A.INI for Linux.

When performing the Capture Hardware Configuration and Deploy Hardware Configuration jobs, the default initialization files representing hardware configuration and array configuration are CPQCAP-H.INI and CPQCAP-A.INI as shown in Table 9.4.

Table 9.4. Configuration Files

Files	Used for
*-h.ini	CONREP.EXE
*-a.ini	ACR.EXE
*-p.ini	CPQDISK.EXE

If you use the capture jobs without modification, each time you capture a new configuration, it overwrites the previous configuration. To capture and deploy configurations for different servers, copy and rename the jobs, and then modify the configuration file name variable within the jobs so that the files are saved with a unique name.

Tools

The Tools directory contains tools used during server deployment that are not included in the SSSTK.

Scripts

The scripts contained in this directory are used for

• Wrapping utilities in the SSSTK to detect and report errors back to the OS

• Setting up the target server to begin an OS installation

Table 9.5. Script Files

Files	Used for
acr.bat	Calls ACR.EXE
conrep.bat	Calls CONREP.EXE
cpqdisk.bat	Calls CPQDISK.EXE
set*.bat	Sets operating system, hardware, array, and partition settings
get*.bat	Gets operating system, hardware, array, and partition settings
yyyy .bat	Prepares hardware for operating system install, where yyyy is the operating system or distribution shortcut name

Windows OS Files

One directory is created for each Windows OS to store the OS files. These files are used by the Windows scripted install jobs. The directory names are derived from the OS name to distinguish each Windows OS version. For example, .\deploy\cds\windows\w2k is the directory name for the Windows 2000 OS files.

Documentation Files

The RDP documentation is installed in the .\docs directory in Portable Document Format (.pdf). These files can be viewed using Adobe Acrobat Reader.