Using the HP Rapid Deployment Pack 3.7 to Deploy Microsoft Windows Server 2003 for IA64

Scheduling three Read HW Configuration jobs
This example uses the jobs that read the hardware array, HBA, and system configuration.
However, you can use any jobs from the Read HW Configuration group in any order.
In the Altiris Deployment Server Console, drag and drop the following jobs, in sequence, to the
target system icon:
• Set ACPI Mode to Linux (Windows)
• Set ACPI Mode to Windows {LinuxPE}
• Read Integrity RX/BL Array Configuration {LinuxPE}
• Read Integrity RX/BL HBA Configuration [server specific] {LinuxPE}
• Read Integrity RX/BL System Configuration {LinuxPE}
The above jobs sequence results in the following behavior:
• Initial state:
— Client booted to Windows Server 2003
— ACPI Mode is set to Windows
• Action: Run the Set ACPI Mode to Linux (Windows) job
— Change ACPI Mode to default (sx2000 chipset) or single-pci-domain (sx1000 chipset).
For chipset specifications, see Table 2-2 (page 13).
• Action: Set ACPI Mode to Windows {LinuxPE}
— Client reboots to Altiris LinuxPE Automation.
— When the client boots to LinuxPE, ACPI Mode is changed to production Windows.
• Action: Run the Read Integrity RX/BL Array Configuration {LinuxPE} job
— Reads array configuration.
• Action: Run the Read Integrity RX/BL HBA Configuration [server-specific] {LinuxPE} job
— Reads HBA configuration.
• Action: Run the Read Integrity RX/BL System Configuration {LinuxPE} job
— Reads system configuration.
— Reboots to Windows Server 2003.
Notice that if the second job is moved to the end of the job list, the result would be the same: at
the end of the last job, the client system reboots to production Windows Server 2003 with the
ACPI mode correctly set to Windows. You should run the Set ACPI Mode to Windows {LinuxPE}
job before the third, fourth, and fifth jobs to guarantee that, if any of these jobs fail, the ACPI
Mode is already set to Windows, and the system can safely boot to production Windows Server
2003.
NOTE: When the first job is dragged and dropped to the target system icon, you can schedule
to run the job later. This allows you to drag and drop the remaining jobs to the job list before the
first job begins. Reschedule all remaining jobs, in order, to run after the first one.
Method B: Customizing with the Set ACPI tasks
The alternative method is to customize RDP jobs by copying the tasks from Set ACPI Mode jobs
directly into the job being customized. These jobs should not have an internal reboot, as in the
Read HW Configuration jobs (group 1).
The following examples illustrates how this can be done, and assumes that:
• The target system is powered on and running one of the following Windows operating
systems:
20 Performing customization