HP Insight Control server deployment

HP Insight Control server deployment 6.3.0 Release Notes And Support Article: 20000066 Last revision: March 31, 2011 Applies to: Release 6.3.0 Deployment Server Prerequisites Feature List Added Functionality 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 (SP1, SP2, and R2) 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 or Microsoft Windows Server 2008 R2 SP1 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 Framework 2.0 (available at http://www.microsoft.com/net/Download.aspx). • Microsoft SQL Server 2005 SP3 Express, Standard, or Enterprise Editions; or Microsoft SQL Server 2008 SP2 Express, Standard, or Enterprise Editions (installed either locally or remotely; available at http://www.microsoft.com/sqlserver/2008/en/us/default.aspx) ; or Microsoft SQL Server 2008 R2 Express. 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). • Disable antivirus software. • 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 SP5   NEW! Deployment Server 6.9.4 Hotfix 1.0   NEW! Deployment Server Tools and Documentation 6.3.0 Deployment Server Automation Drivers 8.70.0 ProLiant Firmware 9.20.0 ProLiant Hardware 8.70.0 Integrity Hardware 4.1.0 Windows 2008 x64 Enterprise/Standard (EN-US) 8.70.0 Windows 2008 x86 Enterprise/Standard (EN-US) 8.70.0 Windows 2008 R2 x64 Enterprise/Standard (EN-US) 8.70.0 Windows 2008 R2 SP1 x64 Enterprise/Standard (EN-US) 8.70.0   NEW! Windows 2008 IA64 (EN-US) 7.10.0 Windows 2008 R2 IA64 (EN-US) 7.10.0 Windows 2003 x64 Enterprise (EN-US) 8.70.0 Windows 2003 x64 Standard (EN-US) 8.70.0 Windows 2003 x86 Enterprise (EN-US) 8.70.0 Windows 2003 x86 Standard (EN-US) 8.70.0 Windows XP x86 Professional (EN-US) 8.40.1 Windows 7 For Workstation Blades(EN-US) 8.60.0   NEW! Hyper-V Server 2008 x64 8.70.0 Hyper-V Server 2008 R2 x64 8.70.0 ESX 4.0 U2 8.70.0 ESX 4.1 U1 8.70.0   NEW! ESXi 4.1 8.70.0 RHEL 5.5 x64 8.70.0 RHEL 5.6 x64 8.70.0   NEW! RHEL 6 x64 8.70.0   NEW! SLES 10 SP3 x64 8.70.0 SLES 11 SP1 x64 8.70.0 HP Management Agents for Windows x86/x64 8.70.0 HP Management Agents for Windows IA64 7.10.0 HP Management Agents for RHEL 5 8.70.0 HP Management Agents for RHEL 6 8.70.0 HP Management Agents for SLES 10 8.70.0 HP Management Agents for SLES 11 8.70.0 HP MPIO EVA DSM 4.01.2 HP MPIO XP DSM 4.01.2 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 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. • 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 Symantec Knowledgebase (Article TECH43843). • On the BL2x220c G7, using the HP NC543i 10Gb Adapter to PXE boot into automation will fail The drivers for this network interface card are not available in WinPE or Linux Managed automation environments. Use the NC 362i Gigabit Server Adapter to PXE boot the target. • Integrity i2 server fails to boot to Windows automation when executing Capture Windows 2008 R2 IA64 Sysprep Image job The Integrity rx2800 i2 servers may fail to boot to automation when the server is executing the Capture Windows 2008 R2 IA64 Sysprep Image job. The Create Disk Image task will fail with error 116, Unable to boot to Windows automation. This issue occurs because the target's system firmware does not properly set the path to automation for the next reboot. This issue will be addressed in a future system firmware version. To work around this issue, manually boot the target server to automation when the job task needs to proceed to automation. • Installing SLES 11 SP1 on DL100 series servers with RAID-enabled Smart Array B110i controller will halt for user input A message on the target server will indicate Could not find /dev/disk/by-id/xxxxxxxxxx. Want me to fall back to /dev/disk/by-id/xxxxxxxxxx? (Y/n). Reboot the target at this point for the installation to continue. • Executing Capture Integrity Smart Array Configuration job on Superdome sx2000 will capture incorrect smart array data The job will complete successfully, but the controller identification data in the captured file will be incorrect and possibly two controllers have the same controller identification data. When you execute the Write Integrity Smart Array Configuration job on a similar target with the captured configuration file, the job will fail. Capturing the data by running the job on the production operating system will capture valid data.This is a known issue in hpacucli in WinPE on Integrity Superdome sx2000 To work around this issue,Use Serial number instead of slot number as the identifier in acu-capture.ini file. Such as: Controller= SerialNumber P92B30E9SSI0J9 Please copy the string 'SerialNumber P92B30E9SSI0J9' from the commented configuration that is captured for a specific card • Executing 'Write Integrity System Configuration' job might hang User has to manually restart the target system. After the restart, users need to delete the job that is hanging. This is observed in BL860c i2, BL870c i2, BL890c i2, rx2800 i2 servers and this is a known issue in SFW.To work around this issue remove 'Lang' from %ALTIRIS_SHARE%\hpfeatures\hw-integrity\bin \Conrep.xml before the job is run. • VMWare ESX 4.1 U1 deployment will be failed To work around this issue user needs to use HP-Branded media distribution only for VMWare ESX 4.1 and ESX 4.1 U1 deployment. • RHEL 6.0 Deployment will hangs on the target servers where Interlagos (IL) processor is present The issue is observed in DL585cG7, BL465cG7 target servers where IL processor is present. RHEL 6.1 is the minimum version for Interlagos processor. • HP Management Agents for Windows x86/x64 deployment will be failed with error 1 To work around this issue user needs to copy the system management controller driver for the selected appropriate OS type from Windows 2003/2008 X86 and Windows 2003/2008 X64. To know how to add the components for a scripted install please refer to How To Add Components To A Scripted Install • Windows 2008 R2 SP1 Deployment will be failed To work around this issue,User needs to update version="6.1.7600.16385" with version="6.1.7601.17514" in both unattended.xml and sysprep.xml files. • Windows 2003 Deployment will be failed with Error 2 in install package on Emulex FC/FCOE storport configured server. To work around this issue,User needs to apply the Microsoft Storport update (KB943545) before installing or upgrading to this version of the miniport driver.This is observed in BL620cG7 target server and is configured with Emulex FC controller. • Executing 'Install HP Management Agents for Windows x86/x64' job might hang for windows 2008 R2 X64 in SAN environment This issue is because of the WBEM component does not support SAN environment.This is observed in BL460c G7 server model and the environment is configured with 4 sheppard modules and 3PAR storage • Blue Screen Is Displayed After Initial Reboot When Hyper-V Installed on Windows Server 2008 R2 To work around this issue user needs to refer the Customer Advisory ( http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01905084&lang=en&cc=us&taskId=101&prodSeriesId=3884098&prodTypeId=3709945) published in HP Customer support. • RHEL 6.0 media distribution validation will also accepts RHEL 5.5 and RHEL 5.6 media distributions This issue will be addressed in next version of RDP release. • Deployment of OS on BL685c G7 will be hangs during reboot with continuous error from be2net nicdriver "Error in cmd completion" This issue will be addressed in next version of RDP release. • 15 minutes delay during Windows 2008 R2 and Windows 2008 R2 SP1 capture sysprep image and deploy sysprep image jobs with Broadcom 1 GB Multifunction Network adapters Windows 2008 R2 and Windows 2008 R2 SP1 capture sysprep image and deploy sysprep image jobs will be wait for 15 mintues after Create Disk Image task with Broadcom 1 GB Multifunction Network adapters. • Executing Capture Integrity Smart Array Configuration job on Superdome sx2000 will capture incorrect smart array data The job will complete successfully, but the controller identification data in the captured file will be incorrect and possibly two controllers have the same controller identification data. When you execute the Write Integrity Smart Array Configuration job on a similar target with the captured configuration file, the job will fail. Capturing the data by running the job on the production operating system will capture valid data.This is a known issue in hpacucli in WinPE on Integrity Superdome sx2000 To work around this issue,Use Serial number instead of slot number as the identifier in acu-capture.ini file. Such as: Controller= SerialNumber P92B30E9SSI0J9 Please copy the string 'SerialNumber P92B30E9SSI0J9' from the commented configuration that is captured for a specific card • Installation of SLES x.x & RHEL x.x on SL335sG7 series servers with SATA Controller setup and enabling 100% partitions size will fail with "GRUB loading, please wait... Error 17". To work around this issue user has to do the following steps manually. • Go to the Deployment Console on the RDP CMS Server • Select the Deploy SLES x.x or Deploy RHEL x.x jobs from the job panel in RDP Deployemnt Console. • Select Distribute Disk Imageand Click on Modify button • Click on Advanced button under the Automation preboot Environment and Go to Resizing tab on Distribute Disk Image Advanced panel • For SLES x.x fix the partition size to 1,038,255MB and for RHEL x.x fix the partition size to 1,006,695MB NEW! • Click on Apply and Finish buttons • RHEL 6.x64 installation METADATA ERROR related to packages To work around this issue user has to do the following steps manually. • Please delete the repodata soft link file with 0KB size from %ALTIRIS_SHARE%\hpfeatures\rhel6-x64\dist folder. • Now go to %rdpinstalldir%\hpfeatures\rhel6-x64\dist\Server folder and move "repodata"folder to %ALTIRIS_SHARE%\hpfeatures\rhel6-x64\dist folder. • Delete "packages" file with 0KB size and copy the "packages" folder from %ALTIRIS_SHARE%\hpfeatures\rhel6-x64\dist to the below locations as needed. • %ALTIRIS_SHARE%\hpfeatures\rhel6-x64\dist\HighAvailability • %ALTIRIS_SHARE%\hpfeatures\rhel6-x64\dist\LoadBalancer • %ALTIRIS_SHARE%\hpfeatures\rhel6-x64\dist\ResilientStorage • %ALTIRIS_SHARE%\hpfeatures\rhel6-x64\dist\ScalableFileSystem • %ALTIRIS_SHARE%\hpfeatures\rhel6-x64\dist\Server

Note:The function of repodata file is to link to repodata folder.

IMPORTANT:Incase of any problem with RHEL 6.x64 deployment related to packages, do the above mentioned steps.

Note: Copying of the packages folder to 6 locations will increase the size of the distribution drastically.

Supported Operating Systems

There are a few operating systems that are listed as supported, but jobs are not provided. Refer to the Insight Control server deployment Knowledge Base.

The following restrictions apply:

Supported ProLiant Targets

Supported Integrity Targets

Supported Other Targets