|
| Component | Version |
|
| Microsoft .NET Framework | 1.1 and 2.0 x86 |
| Microsoft SQL Server Express | 2005 SP2 |
| Altiris Deployment Solution | 6.9 |
| WinPE Automation Environment | 2.1 x86, x64, and IA64 |
| Linux Automation Environment | 2.6.18.8 x86 and IA64 |
| HP ProLiant Integration Module (EN, JA) | 3.81 |
| SmartStart Scripting Toolkit for WinPE 2.1 x86 | 2.0 |
| SmartStart Scripting Toolkit for Linux | 2.0 |
| Firmware Maintenance CD | 8.20 |
| ProLiant Support Pack for Windows 2003 | 8.11 |
| ProLiant Support Pack for Windows 2008 | 8.11 |
| ProLiant Support Pack for VMware ESX 3.x | 8.10 |
| ProLiant Support Pack for Red Hat EL 4 | 8.12 |
| ProLiant Support Pack for Red Hat EL 5 | 8.11 |
| ProLiant Support Pack for SUSE Linux 10 | 8.11 |
| HP Integrity Integration Module (EN, JA) | 3.81 |
| SmartSetup Scripting Toolkit for WinPE 2.1 | 3.0 |
| SmartSetup Scripting Toolkit for Linux | 3.1 |
| Integrity Support Pack for Windows 2003 | 6.0 |
| Integrity Support Pack for Red Hat EL 4 | 4.27 |
| Integrity Support Pack for Red Hat EL 5 | 4.27 |
| Integrity Support Pack for SUSE Linux 10 | 4.27 |
|
| • | On servers with PXE first in the boot order, Windows Server 2008 x86/x64 scripted install jobs will hang
The "rem scripted-install" command in the Start Install Run Script, instructs the Deployment Server that this task should be automatically marked as complete since the Windows setup program will be taking over. However, when PXE is first in the boot order and Windows SErver 2008 setup reboots, the server incorrectly boots to automation. The Deployment Server thinks there is a pending task, but since there isn't, the server stops. Force the server to boot to the local hard drive by either canceling the PXE boot or temporarily changing the boot order. |
| • | Deployment Server installation hangs if Z drive is mapped and not connected
Either connect or unmap Z drive and then retry the installation. |
| • | If UUID is the Primary Lookup Key, a Deployment Server upgrade installation will duplicate computer records in the database
Before an upgrade installation, change the lookup key to something other than UUID. Altiris is providing a tool to repair the database if the installation was performed. |
| • | iLO channel interface driver is not loading under WinPE 2.1 x86/x64
When a new computer performs an initial WinPE 2.1 x86/x64 PXE boot, the iLO inventory information will be missing from the Computer Properties dialog. When the server boots to a production operating system or LinuxPE, the iLO inventory information will be retrieved. |
| • | Rip-And-Replace jobs fail with an error 1 on the Support Pack installation task
When performing a rip-and-replace, Windows jobs that contain a Distribute Software task to install the Support Pack will fail with an error 1 because the generated jobs do not persist custom return codes. Error 1 means that installation was successful and that a reboot is required. Manually reboot the target server to complete the job. |
| • | Windows Server 2003 scripted install jobs now require a minimum of SP2
You must either use slipstreamed SP2 media or manually slipstream your existing distribution files to SP2. Otherwise the included Emulex driver will cause a blue screen during the scripted install process. |
| • | After an image capture of SUSE LINUX Enterprise Server 10 Service Pack 2, the reference server may lose network connectivity
If the reference server does not have the first NIC connected to the RDP network, after the image capture, the reference server may not have network connectivity to the Deployment Server. A deployment of the captured image file to other targets is not impacted, regardless of which NICs are connected to the RDP network. |
| • | Upgrade Firmware job fails with iLO/iLO2 error reported in log file
If the log file has the Original Version as a range starting with "0.00", hp_ilo reported the original version incorrectly. The firmware upgrade actually did occur. |
| • | Upgrade Firmware job fails to upgrade the QLogic firmware on a ProLiant BL20p G2 or BL20p G3
The job will fail with the log file reporting an error with the QLogic firmware component. A future release will contain a new QLogic firmware component to fix this issue. |
Printable version
