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

A ACPI
Background information
ACPI is an open-industry specification codeveloper by HP, Intel, Microsoft, Phoenix, and Toshiba.
ACPI establishes industry-standard interfaces for operating system-directed configuration and
power management on laptops, desktops, and servers.
Because of differences in the operating systems, ACPI tables can vary, making it necessary to set
the ACPI mode differently on Integrity mid-range and high-end systems. ACPI can be set to one
of the following values:
• Windows
• Default
• single-pci-domain
• Longhorn
NOTE: Longhorn refers to Windows Server 2008, and is not within the scope of this
document.
Integrity mid-range and high-end systems contain several PCI root bridges. In default mode, the
bridges appear in several PCI domains. Currently, each I/O chassis is assigned a different domain,
which you can view by entering the info io command at the EFI Shell prompt.
Single-pci-domain mode is the same as default mode, except that all bridges appear in PCI
domain 0. Windows mode also places all bridges in PCI domain 0, but in addition, some ACPI
tables are changed because Windows does not yet support some ACPI 2.0 constructs.
From the EFI Shell, enter the acpiconfig command to modify the ACPI mode. This variable
is found only on Integrity mid-range and high-end systems as depicted in the following figure.
ACPI values
Most RDP Integrity jobs have tasks that run in Altiris LinuxPE automation. You can expect
intermittent operating system reboots from Windows Server 2003 to LinuxPE and vice versa
while the jobs are running. Because RDP uses Linux as its automation environment to perform
scripted and imaged Windows Install jobs, switching between operating systems (Altiris LinuxPE
Automation and production Windows Server 2003) is necessary. Consequently ACPI settings
must be changed to values suitable to Windows or Linux before each reboot of an Integrity
mid-range or high-end system. Each time this value is changed, a reboot is required to activate
the change. This incompatibility exists between system firmware and operating systems on ACPI
implementations.
Background information 33