HP Insight Rapid Deployment software 6.0.0 Release Notes And Support
Article: 20000040
Last revision: October 10, 2010
Applies to: Release 6.0.0
Deployment Server Prerequisites
Feature List
Major Changes
Known Issues
Supported Operating Systems
Supported ProLiant Targets
Supported Integrity Targets
Supported Other Targets
Deployment Server Prerequisites
| • |
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. The server must not be a domain controller.
|
| • |
Storage: 8 GB of free space on the system drive, 4 GB for the base installation, about 4 GB for each distribution, and additional space for each captured disk image.
|
| • |
Networking: a network adapter configured with a static IP address and all firewalls properly configured.
For Windows 2008 with a local DHCP service, refer to
Symantec Knowledgebase (Article TECH41571).
|
| • |
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 TCP static port; TCP 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 on the remote Windows Server, (a) the user performing the installation must have Administrator permissions,
(b) the firewall must be properly configured, and (c) the SQL Browser service must be running.
|
|
| • |
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, console security must be disabled.
|
Feature List
|
| Feature | Version |
|
| Altiris Deployment Solution | 6.9 SP3 |
| Deployment Server 6.9.3 Hotfix | 1.0 |
| Deployment Server Tools and Documentation | 6.0.0 |
| Deployment Server Automation Drivers | 8.30 |
| ProLiant Firmware | 8.60 |
| ProLiant Hardware | 2.20 |
| Integrity Hardware | 3.2 |
| Windows 2008 x64 Enterprise/Standard (EN-US) | 8.30 |
| Windows 2008 x86 Enterprise/Standard (EN-US) | 8.30 |
| Windows 2008 R2 x64 Enterprise/Standard (EN-US) | 8.30 |
| Windows 2008 IA64 (EN-US) | 6.20 |
| Windows 2003 x64 Enterprise (EN-US) | 8.30 |
| Windows 2003 x64 Standard (EN-US) | 8.30 |
| Windows 2003 x86 Enterprise (EN-US) | 8.30 |
| Windows 2003 x86 Standard (EN-US) | 8.30 |
| Windows XP x86 Professional (EN-US) | 8.30 |
| Windows Vista x64 Business (EN-US) | 8.30 |
| Hyper-V Server 2008 x64 | 8.30 |
| Hyper-V Server 2008 R2 x64 | 8.30 |
| ESX 3.5.0 U4 | 8.20 |
| ESX 4.0 | 8.25 |
| RHEL 4.8 x64 AS | 8.30 |
| RHEL 5.3 x64 | 8.30 |
| SLES 10 SP2 x64 | 8.30 |
| SLES 11 x64 | 8.30 |
|
Major Changes
| • | New installation interface. |
| • | New feature-based design. Each feature is a self-contained set of jobs and files. |
| • | The WAIK, SQL Express and .NET frameworks are no longer included. |
| • | Only required support pack smart components are included, not the full support pack. |
| • | New LinuxPE kernel 2.6.27.7 based on OpenSUSE 11.1. |
| • | Only some operating system jobs are included. Adding support for missing architectures, editions, or languages can be found in the Knowledge Base. |
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.
|
| • |
A Deployment Sever 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 the installation.
|
| • |
A Deployment Server 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 the Deployment Server is installed on a Windows x64 operating system
For information on how to properly configure IIS to work with the Deployment Web Console, refer to
Symantec Knowledgebase (Article TECH43843).
|
| • |
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.
|
| • |
Write ProLiant Smart Array Configuration job fails with error 186 when ran on servers with a SmartArray P410i controller and do not have active license key
The Read ProLiant Smart Array Configuration job calls the Array Configuration Utility and captures information about
advanced license key-enabled features, even if there is no active license provided for the controller. When this captured configuration is deployed back
to same or similar controllers that do not have active license key, the job fails with
ERROR:(3002) Command Failed ATTR_NAME_MNP_DELAY:60 not available because:UNAVAILABLE_REASON_FEATURE_REQUIRES_LICENSE_KEY.
To work around this issue, edit the captured array configuration file in a Linux-compatible editor and remove the following lines:
MNPDelay=
IRPEnable=
DPOEnable=
ElevatorSortEnable=
QueueDepth=
.
|
| • |
Running the Erase ProLiant Hardware job on a target with a logical serial number will cause the target to appear new in the Deployment Server console with physical serial number name
When the Erase ProLiant Hardware job is run on a target with a logical serial number, after the target reboots, it will
appear in the Deployment Server Console as a new computer and its display name as its physical serial number. To work
around this issue, either prior to running the job, remove the Erase System Configuration task in the job, or after the job is run,
reboot the target. The rbsureset utility in the task removes logical values and they are not replaced until the target
is rebooted a second time.
|
Supported Operating Systems
|
| Windows Server 2003 x86 and x64 Enterprise/Standard/Web |
| Windows Server 2008 x86 and x64 Enterprise/Standard/Datacenter |
| Windows Server 2008 R2 x64 Enterprise/Standard/Datacenter NEW! |
| Windows Server 2008 IA64 |
| Hyper-V Server 2008 x64 |
| Hyper-V Server 2008 R2 x64 NEW! |
| VMware ESX 3.5.0 U4 |
| VMware ESX 4.0 |
| Red Hat Enterprise Linux 4.8 x86 and x64 AS/ES NEW! |
| Red Hat Enterprise Linux 5.3 x86 and x64 |
| SUSE LINUX Enterprise Server 10 SP2 x86 and x64 |
| SUSE LINUX Enterprise Server 11 x86 and x64 NEW! |
| Windows XP x86 Professional |
| Windows Vista x64 Business |
|
The following restrictions apply:
| • | Windows Server 2003 requires minimum SP2. |
| • | Windows Server 2008 IA64 requires minimum SP2. |
| • | Windows Server 2003 x64 deployments to virtual machines hosted by Hyper-V Server 2008 or Hyper-V Server 2008 R2 are not supported. |
| • | Windows Vista requires minimum SP1 and Windows XP requires minimum SP2 |
| • | Windows client operating systems are only supported on blade PCs and Blade Workstations. |
| • | Linux IA64 deployments are supported if upgraded from Releases 3.80 through 3.83 to 6.0.0. |
Supported ProLiant Targets
| • | Not every target platform configuration is supported by the Operating System support list. Refer to certification matrices:
|
| • | Refer to support documents for additional information on how to deploy an operating system:
|
| • | 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 supported virtualization hosts, VMware ESX 3i, Windows Server 2008 Hyper-V x86/x64, or Windows Server 2008 R2 Hyper-V.
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 version can be deployed using imaging. |
|
| BL20p G3 |
BL20p G4 |
BL25p |
BL25p G2 |
BL35p |
| BL45p [1] |
BL45p G2 |
BL260c G5 |
BL280c G6 |
BL2x220c G5 |
| BL2x220c G6 NEW! |
BL460c |
BL460c G5 |
BL460c G6 |
BL465c |
| BL465c G5 |
BL465c G6 |
BL480c |
BL490c G6 [2] |
BL495c G5 |
| BL495c G6 |
BL680c G5 |
BL685c |
BL685c G5 |
BL685c G6 |
| DL120 G5 |
DL140 G2 |
DL140 G3 |
DL145 G2 |
DL145 G3 |
| DL160 G5 |
DL160 G5p |
DL160 G6 |
DL165 G5 |
DL165 G5p |
| DL165 G6 NEW! |
DL170h G6 |
DL180 |
DL180 G5 |
DL180 G6 |
| DL185 G5 |
DL320 G4 |
DL320 G5 |
DL320 G5p |
DL320 G6 |
| DL320s |
DL360 G4 [3] |
DL360 G4p [3] |
DL360 G5 |
DL360 G6 |
| DL365 |
DL365 G5 |
DL370 G6 |
DL380 G4 |
DL380 G5 [4] |
| DL380 G6 |
DL385 |
DL385 G2 |
DL385 G5 [4] |
DL385 G5p |
| DL385 G6 |
DL580 G3 |
DL580 G4 |
DL580 G5 [4] |
DL585 |
| DL585 G2 |
DL585 G5 |
DL585 G6 |
DL785 G5 |
DL785 G6 NEW! |
| ML310 G3 |
ML310 G4 |
ML310 G5 |
ML310 G5p |
ML330 G6 |
| ML350 G4p |
ML350 G5 |
ML350 G6 |
ML370 G4 |
ML370 G5 |
| ML370 G6 |
ML570 G3 |
ML570 G4 |
SL160z G6 |
SL165z G6 NEW! |
| SL170z G6 |
|
[1] For SAN, only QLogic Fibre Channel HBA is supported.
[2] For VMware ESX 3.5.0, only Boot From SAN storage is supported.
[3] For VMware ESX, only Smart Array storage is supported.
[4] For SAN, only Boot from SAN storage is supported. Brocade FC HBA is only supported for Windows.
Supported Integrity Targets
| • | Refer to support documents for additional information on how to deploy an operating system:
|
| • | 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 |
rx7640 |
rx8640 |
Superdome sx2000 |
|
[5] For direct attached storage (DAS), RAID 1 configuration is only supported.
Supported Other Targets
|
| bc1500 blade PC [6] |
bc2000 blade PC [6] |
bc2200 blade PC |
| bc2500 blade PC [6] |
bc2800 blade PC |
WS460c G6 Workstation Blade NEW! |
| xw2x220c Blade Workstation |
xw460c Blade Workstation |
|
[6] Only Windows XP x86 is supported.
|
Printable version
