How A Job Is Run On A Target - HP Rx2620-2 - Integrity - 0 MB RAM User Manual

How a job is run on a target

This section provides a walkthrough of how a job is executed on a target server. The table within
each step lists the state of the target server and the job action during that execution step.
The term "automation environment" is used throughout this section. It is an operating system in which
scripts can be run on the target independent of the target's production operating system or the
Deployment Server operating system. The target can boot the automation environment either from a
CD-ROM, USB key, or through PXE. The Rapid Deployment Pack supports the following automation
environments: Linux x86 and ia64 (hereafter LinuxPE) and WinPE 1.6 x86 and x64. Each automation
environment consists of the necessary base files, additional HP drivers, and the appropriate Altiris
Deployment Agent.
NOTE: A CD-ROM or USB key can only hold one automation environment. Many of the jobs use
multiple automation environments. This means that as the job progresses, the boot media must be
swapped accordingly.
The Run Script, Create Disk Image, and Distribute Disk Image tasks enable the user to specify which
automation environment to run in. The Rapid Deployment Pack jobs specify a specific automation
environment to avoid ambiguity and to ensure that the utilities run in the correct and tested
environment.
Power up the bare-metal target server. Since the target does not have a bootable hard drive, the
1.
boot order attempts a PXE boot. The PXE Server sends it the Initial Deploy boot option image. By
default, this is Linux Managed (auto-select). The Deployment Agent connects to the Deployment
Server. Since this is the initial connection and no pending job exists, the Deployment Server
directs the Deployment Agent to wait.
Table 8 Step 1
Target Server
Schedule the "Deploy ProLiant ML/DL/BL + Windows 2003 x64 Enterprise + PSP" job on the
2.
target.
Table 9 Step 2
Target Server
Job
The Deployment Server determines that the target is in the incorrect automation environment. It
3.
directs the Deployment Agent to set the one-time boot EV to PXE and then reboot. When the
target reboots to PXE, the PXE Server sends it the WinPE 32-bit image.
Table 10 Step 3
Target Server
Job
LinuxPE, waiting
LinuxPE, waiting
Task 1—Deploy System Configuration {WinPE 32-bit}, pending
Rebooting to WinPE Managed 32-bit
Task 1— Deploy System Configuration {WinPE 32-bit}, pending
Understanding the Deployment Server 24