Professional Documents
Culture Documents
• Hardware: ProLiant server with at least 2.0 GHz processor and 2 GB of memory, or an equivalent virtual machine.
• Operating System: Microsoft Windows Server 2003 x86 or x64 Standard or Enterprise Editions; Microsoft Windows
Server 2008 x86 or x64 Standard or Enterprise Editions; or Microsoft Windows Server 2008 R2 x64 Standard or
Enterprise Editions.
• Storage: 2 GB for the base installation, plus space for each distribution, and plus space for each capture disk image.
• Networking: a network adapter configured with a static IP address.
• Microsoft .NET Frameworks 1.1 and 2.0 (available at http://www.microsoft.com/net/Download.aspx).
• Microsoft SQL Server 2005 SP2 Express, Standard, or Enterprise Editions; or Microsoft SQL Server 2008 Express,
Standard, or Enterprise Editions (installed either locally or remotely; available at
http://www.microsoft.com/sqlserver/2008/en/us/default.aspx). Configured as follows:
• SQL Server Protocols TCP/IP and Named Pipes must be enabled.
• SQL Server must be configured with a static port; dynamic ports are not supported.
• The user performing the installation must be a member of the SYSADMIN SQL Server Security Role.
• For remote SQL Server installations, the user performing the installation must have Administrator permissions on
the Windows Server that is hosting the SQL Server.
NOTE: The HP Insight Software DVD SQL Server 2005 Express SP2 installation is already configured properly.
• Microsoft Windows Automated Installation Kit (AIK) for Windows Vista SP1 and Windows Server 2008 1.1
(available at http://www.microsoft.com/downloads/details.aspx?familyid=94bb6e34-d890-4932-81a5-
5b50c657de08&displaylang=en&tm).
• To use the Deployment Web Console, Microsoft IIS with ASP.NET.
• To deploy VMware ESX or Linux, Microsoft IIS FTP. For IIS 7.5, IIS 6 compatibility mode must be enabled and
FTP Publishing must be added to the default web site with anonymous read access.
• When upgrading, disable console security and turn off agent autoupdating.
Feature List
Feature Version
Major Changes
Known Issues
• WinPE 3.0 from the Windows Automated Installation Kit (AIK) for Windows 7 and Windows Server 2008 R2
is not supported and should not be installed on the intended Deployment Server
The Deployment Server installation will fail if this WAIK is installed. Only WAIK 1.1/WinPE 2.1 (for Windows
Vista and Windows Server 2008) is 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: Open the PXE Configuration Utility, select the PXE Server tab, and for DHCP
Server discovery select the No DHCP server installed on PXE server (Use DHCP port) option. For more
information, refer to Altiris Knowledgebase (Article 45903).
• An RDP installation on Windows localized in Italian or Spanish requires the English Windows AIK
Localized Italian or Spanish Windows AIK does not have support for WinPE IA64 which is required for RDP
installation.
• An RDP installation cannot be run from a localized path
If the rdp-x.x.x.x.exe file is located and run from a path with localized characters, it will fail to extract with the
error, "Failed to extract files.". Running the installer from a non-localized path will work properly.
• The Deployment Web Console fails to open when RDP is installed on a Windows x64 operating system
The issue will be fixed in a future release.
• Jobs exported from Deployment Server versions prior to 6.9 will not import
Either an error message will be received or the import will complete, but the job will not appear in the Deployment
Console. For information on how to resolve this issue and how to obtain a conversion utility, refer to Altiris
Knowledgebase (Article 48574).
• Windows XP Sysprep capture hangs
Before executing the Sysprep capture job, for the Create Disk Image task, click on Advanced Settings and select
Enable mass storage device support using built-in drivers.
• Write ProLiant FC HBA Configuration job fails with error 255 when ran on servers with a Emulex 8Gb Fibre
Channel HBA
Use the VirtualConnect for FibreChannel or the Emulex BIOS utility to update the HBA settings.
• Not every target platform configuration is supported by the Operating System support list. Refer to certification
matrices:
• Windows support for HP ProLiant Servers
• ProLiant server VMware support matrix
• Linux certification and support matrix - HP ProLiant servers
• Refer to support documents for additional information on how to deploy an operating system:
• Knowledge Base article Servers With Multiple Disks Deployment Support (Article 20000038)
• Knowledge Base article How To Perform a Boot From SAN Installation (Article 20000039)
• Knowledge Base article Multipath SAN Deployment Support (Article 20000041)
• For virtual machine deployment, Windows Server 2003 x86 or x64 and Windows Server 2008 x86 or x64 may be
deployed to a virtual machine created within one of the RDP-supported virtualization hosts including VMware ESX
3i and Windows Server 2008 Hyper-V x64. For additional deployment information, refer to Knowledge Base article
Virtual Machine Deployment Support (Article 20000044).
• Boot from SAN and SAN attached hardware configuration using Emulex and QLogic Fibre Channel HBAs are
supported on all ProLiant server blades.
• ProLiant DL100 series servers and virtual machines created within the supported virtualization hosts require PXE or
Network boot first in the boot order.
• Configuration of and operating system deployment to servers with RAID enabled through the ROM-Based Setup
Utility (RBSU) is not supported.
• Red Hat Linux updates that were supported by a previous RDP version can be deployed using imaging.
• Refer to support documents for additional information on how to deploy an operating system:
• Knowledge Base article Integrity Server Deployment Support (Article 20000025)
• Knowledge Base article Servers With Multiple Disks Deployment Support (Article 20000038)
• Knowledge Base article How To Perform a Boot From SAN Installation (Article 20000039)
• Knowledge Base article Multipath SAN Deployment Support (Article 20000041)
• Boot from SAN and SAN attached hardware configuration using Emulex and QLogic Fibre Channel HBAs are
supported on all Integrity server blades.
• Deployments to Integrity mid-range and Superdome servers are not supported with Japanese localized operating
systems.
BL860c [5] BL870c [5] rx2660 rx3600
rx6600 rx7620 rx7640 rx8620
rx8640 Superdome sx1000 Superdome sx2000
[5] For direct attached storage (DAS), RAID 1 configuration is only supported.