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

In the Altiris Deployment Server console, drag and drop the following jobs, in sequence, to the
active target system icon:
1. Set ACPI Mode to Linux (Windows)
2. Set ACPI Mode to Windows {LinuxPE}
3. Read Integrity RX/BL Hardware Configuration [server-specific] {LinuxPE}
Executing this sequence of jobs results in the following actions:
• Initial state:
— Client booted to Windows Server 2003
— ACPI Mode is set to Windows
• Action: Run the Set ACPI Mode to Linux (Windows) job
— Changes ACPI Mode to default (sx2000 chipset) or single-pci-domain (sx1000 chipset).
For chipset specifications, see Table 2-2 (page 13).
• Action: Run the Set ACPI Mode to Linux (Windows) job
— Client reboots to Altiris LinuxPE Automation.
— The ACPI Configuration Mode is changed to Windows.
• Action: Run the Read Integrity RX/BL Hardware Configuration [server-specific] {LinuxPE}
job
— Reads HW configuration.
— Reboots to Windows Server 2003.
Notice that if the last two jobs from the jobs sequence are swapped, 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. However, you should run the Set ACPI Mode to Windows
{LinuxPE} job before the Read Integrity RX/BL Hardware Configuration [server-specific]
{LinuxPE} job to guarantee that, if the Read Integrity RX/BL Hardware Configuration
[server-specific] {LinuxPE} job fails, 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
the job to begin 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.
Read HW Configuration jobs (group 1) 19