Server Deployment Toolbox Jobs; Directory Structure; Deployment Server Directory Structure - HP BL860c User Manual
Rapid deployment pack
Hide thumbs
Also See for BL860c:
- Datasheet (511 pages) ,
- User's & service manual (184 pages) ,
- Deployment manual (84 pages)
Table of Contents
Advertisement
Linux imaging notes:
The reference and target servers must have an identical storage controllers.
The capture image file will be .\lib\images\yyyy-linux.img where yyyy is the computer model
name, for example ProLiant DL360 G4.
Subsequent captures on the same model will overwrite any existing image file.
Some applications do not image properly.
Server Deployment Toolbox Jobs
This folder contains jobs that are decompositions of the other jobs, variants of the generic hardware jobs,
and non-deployment jobs.
The Hardware Configuration and OS Imaging jobs are available in Read/Write and Capture/Deploy
pairs respectively. The job pairs use the same output/input file.
Jobs denoted with "[server-specific]" use a output/input filename based upon the Computer ID of the
target server instead of a static filename. To determine the Computer ID look at the Properties of the
server in the console.
If you execute a Read or Capture job, the output file will be overwritten.
The Offline Wait job can be used to "hold" a target server in the LinuxPE environment. This job essentially
emulates a first-time LinuxPE PXE boot "Waiting for instructions" state.
The Read Hardware Configuration jobs can generate an extensive inventory of the target server
hardware. These jobs execute various toolkit utilities, such as conrep and acu, to gather the inventory.
The Upgrade ProLiant ML/DL/BL Firmware job uses LinuxPE, not the production operating system.
Therefore you can use it on bare-metal servers. The job upgrades the following hardware: System BIOS,
Smart Array, iLO, NIC, QLogic HBA, and local hard drives.
Directory structure
The following table provides an overview of the Deployment Server directory as populated by the Rapid
Deployment Pack. The '.' in the directory paths below represents the Deployment Server installation directory.
Table 5-6 Deployment Server directory structure
Directory
.\docs
.\jobs
.\lib\bin32
.\lib\bin64
.\lib\binia64
.\lib\hwconfig
.\lib\images
.\lib\osconfig
.\lib\osdist
.\lib\osoem
.\lib\ossysprep
.\lib\software
Directory contents
Rapid Deployment Pack documentation
The .bin files for the provided jobs
Windows SmartStart Scripting Toolkit, Linux SmartStart Scripting Toolkit, and various tools and
scripts
Various tools and scripts
Smart Setup Scripting Toolkit for Integrity and various tools and scripts
Presupplied and captured hardware configuration files
Presupplied and captured image files
Operating system scripted installation answer files separated into subdirectories per OS
Operating system distribution files separated into subdirectories per OS
ProLiant Drivers for Windows, Integrity Drivers for Windows, and Altiris Deployment Agents
The driver subdirectories are either a specific version number, such as 800, or zzz which is a copy
of the latest version subfolder. The provided jobs use the zzz subfolder.
Operating system sysprep imaging answer files separated into subdirectories.
ProLiant Support Packs, ProLiant Firmware Maintenance, and Integrity Support Packs
The support pack subdirectories are either a specific version number such as 800, or Z.ZZ which
is a copy of the latest version subfolder. The provided jobs use the Z.ZZ subfolder.
Server Deployment Toolbox Jobs
29
Advertisement
Table of Contents
