|
| Component | Version |
|
| Microsoft .NET Framework | 1.1 and 2.0 x86 |
| Microsoft SQL Server Express | 2005 SP2 |
| Altiris Deployment Solution | 6.9 SP1 (+ MP1) |
| 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.83 |
| SmartStart Scripting Toolkit for WinPE 2.1 x86 | 2.1 |
| SmartStart Scripting Toolkit for Linux | 2.1 |
| Firmware Maintenance CD | 8.40 |
| ProLiant Support Pack for Windows 2003 | 8.20 |
| ProLiant Support Pack for Windows 2008 | 8.20 |
| ProLiant Support Pack for Windows XP x86 | 8.20 |
| ProLiant Support Pack for VMware ESX 3.x | 8.11 |
| ProLiant Support Pack for Red Hat EL 4 | 8.20 |
| ProLiant Support Pack for Red Hat EL 5 | 8.20 |
| ProLiant Support Pack for SUSE Linux 10 | 8.20 |
| VMware ESX Supplement | |
| ProLiant Support Pack for VMware ESX 3.x | 8.20 |
| ProLiant Support Pack for VMware ESX 4.x | 8.25 |
| HP Integrity Integration Module (EN, JA) | 3.83 |
| SmartSetup Scripting Toolkit for WinPE 2.1 | 3.1 |
| SmartSetup Scripting Toolkit for Linux | 3.1 |
| Integrity Support Pack for Windows 2003 | 6.10 |
| Integrity Support Pack for Windows 2008 | 6.15 |
| 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 |
|
| • | 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 drivers, such as the included Emulex driver will cause a blue screen during the scripted install process. |
| • | Windows Server 2008 scripted install stops at "Select the edition of Windows that you purchased"If utilizing the Microsoft Windows Server 2008 without Hyper-V media, the OS Image value string in the default.xml file will need to be modified to allow the unattended process to complete without user interaction. As an example, the string Windows Longhorn SERVERENTERPRISE will need to be modified to Windows Longhorn SERVERENTERPRISEV. The Windows 2008 default.xml files are located on the Deployment Server in the .\lib\osconfig directory. |
| • | Windows Server 2008 and WinPE do not consistently boot target servers into PXE automation when the servers have 24 or more memory DIMMS installed This problem will be corrected in a future release of RDP. |
| • | Additional SQL Server Configuration Requirements for RDP installationsThe user account used for the RDP installation must be a member of the SYSADMIN SQL Server Security Role. SQL Server must be configured with a static port; dynamic ports are not supported. |
| • | An RDP installation from read-only media on Windows Server 2008 with a remote SQL Server may fail the ProLiant or Integrity Integration Module Console Security check
To correct the problem, reboot the Deployment Server and restart the ProLiant or Integrity Integration Module installation. |
| • | RDP does not support installations to MS SQL Server 2008 Express Edition
Current issues prevent Altiris Deployment Server from installing to MS SQL Server 2008 Express Edition. A future release of Altiris Deployment Solution will correct this issue. Installations to MS SQL 2008 Server Enterprise Edition and Standard Edition are supported. |
| • | An RDP installation on Windows Server 2008 with the DHCP service installed locally, does not set the 060 DHCP option
Modify the following PXE configuration option if DHCP service is required to be installed locally on a Windows Server 2008 Deployment Server: Navigate to PXE Configuration Utility -> PXE Server tab -> DHCP Server discovery setting and change the setting to No DHCP server installed on PXE server (Use DHCP port). A future release of Altiris Deployment Solution will correct this issue. |
| • | An RDP installation on Windows localized in Italian or Spanish requires the English Windows AIKLocalized Italian or Spanish Windows AIK does not have support for WinPE IA64 which is required for RDP installation. |
| • | A target server with multipath Boot from SAN will not boot after a Red Hat Enterprise Linux 5.3 image deployment
The image contains the reference server's LUN WWID. This ID is not updated after the image is deployed to the new target server causing a boot failure since the hard drive cannot be found. Deploying the image to the same reference server from where the image was captured will boot properly. |
| • | During LinuxPE startup, messages may be seen on the target server that do not impact functionality and can be safely ignored: |
| "A fatal error has occurred: The disk was not found." message is seen if no partitions are on the hard drive. |
| "Fixup flags cleared." and "Fixup completed." |
| "ethX NIC SerDes Link is Down" messages on some c-Class target servers that are connected to a HP Gbe2 (Layer 2) switch. |
| "mf_cfg function disabled" on servers with Broadcom 10Gb NIC. |
| • | 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. |
| |
| |
| |
| |
| |
| |
| |
| |
Printable version
