HP Insight Control server deployment Knowledge base HP Insight Control server deployment Release Notes And Support

Transcription

1 HP Insight Control server deployment Knowledge base HP Insight Control server deployment Release Notes And Support Last revision: Applies to: Release Deployment Server Prerequisites Feature List Known Issues Supported Operating Systems Supported ProLiant Targets Supported Integrity Targets Supported Other Targets Supported Option Cards NEW! 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 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 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 ; 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 (available at 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 MR1 NEW! Deployment Server Hotfix 1.0 NEW! Deployment Server Tools and Documentation Deployment Server Automation Drivers ProLiant Firmware ProLiant Hardware Integrity Hardware Windows 2008 x64 Enterprise/Standard (EN-US) Windows 2008 x86 Enterprise/Standard (EN-US) Windows 2008 R2 x64 Enterprise/Standard (EN-US)

2 Windows 2008 R2 SP1 x64 Enterprise/Standard (EN-US) Windows 2008 IA64 (EN-US) Windows 2008 R2 IA64 (EN-US) Windows 2003 x64 Enterprise (EN-US) Windows 2003 x64 Standard (EN-US) Windows 2003 x86 Enterprise (EN-US) Windows 2003 x86 Standard (EN-US) Windows XP x86 Professional (EN-US) Windows 7 For Workstation Blades(EN-US) Hyper-V Server 2008 x Hyper-V Server 2008 R2 x ESX 4.0 U ESX 4.1 U NEW! ESXi 4.1 U NEW! ESXi RHEL 5.7 x NEW! RHEL 6.1 x NEW! RHEL 6.2 x NEW! SLES 10 SP4 x SLES 11 SP1 x HP Management Agents for Windows x86/x HP Management Agents for Windows IA HP Management Agents for RHEL HP Management Agents for RHEL HP Management Agents for SLES HP Management Agents for SLES HP MPIO EVA DSM 4.02 HP MPIO XP DSM Known Issues 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. 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. Windows 2008 R2 and Windows 2008 R2 SP1 capture image job will hang on SAN brocade controller. This issue will be addressed in next version of RDP release.on SAN brocade controller the capture image job for Windows 2008 R2 and Windows 2008 R2 SP1 will hang with Windows error recovery page in target system. 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 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 HP Virtual Connect FlexFabric 10Gb/24-port modules and 3PAR storage 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. 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.

3 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 Click on Apply and Finish buttons RDP installation may fail with Error 194 while pxe regeneration. NEW! One of the below are will be the workaround for this issue. Change the windows registry key HKLM\System\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation to 0 and install RDP again. NTFS generates a short name in the 8.3 naming convention for long file names and for file names that contain characters from the extended character set. If the value of this entry is 0, then files can have two names: the name that the user specifies and the short name that NTFS generates. If the name that the user specifies conforms to the 8.3 naming convention, then NTFS does not generate a short name.which will cause to pxe regenaration fails. For more information on this windows regsitry key, refer to NtfsDisable8dot3NameCreation Deployment of SLES11 SP1 may fail on G7 with AMD Opteron 6200 series processor or Gen8 targets NEW! To workaround this issue Please refer to How to deploy SLES 11 SP1 x64/x86 to Gen Next or G7 Servers with AMD Opteron 6200 series processors popup message shown while installing HP Insight Control Server Deployment and WinPE installation will fail during PXE installation. NEW! This problem will occur when user has not installed WAIK in the server where HP Insight Control Server Deployment is being installed and provides mapped network drive path which contains WAIK installer files during installation. To work around this issue, 1.Copy the WAIK installer contetnts to local hard drive and provide path for the installation. or 2.Create a directory in mapped network drive and copy the WAIK installer contents and provide path during the installation. This issue will be addressed in future release. VGA G200eH and Headless Registry drivers are not updated in Windows 2008/2008 R2 OS's. NEW! To work around this issue user needs to install SPP in target server after deploying the Windows server 2008/2008 R2 OS. To know how to install SPP after OS installation please refer to How To Install Software Packages,Service Pack for ProLiant (SPP) And Support Packs Image deploy is retaining the name of the original computer the image was captured from. NEW! This will be addressed in future release of RDP. To work around this issue please refer to Symantec KnowledgeBase User will encounter an error as "Error was encountered while formatting device /dev/mapper/mpthap1 during deployment of RHEL 6.1 x64 on a ProLiant server connected to a Thin Provisioned LUN on EVA Storage Arrays. NEW! When user does thin provisioning with EVAP6300 or EVA 4400 storage, RHEL 6.1 Deployments will fail. This issue will not be observed with full or thick provisioning. This is a known limitation with EVAP6300 / EVA 4400 storage and RHEL6.1. Executing "Install HP MPIO EVA DSM" or "Install HP MPIO XP DSM" job on 3 par storage will hang. NEW! "Install HP MPIO EVA DSM" or "Install HP MPIO XP DSM" jobs are not supported on 3 par storage. Blue Screen Is Displayed After Initial Reboot to WindowsPEX64 on a target server with AMD Interlagos processor. NEW! This issue is observed on DL585G7 with 4 Interlargos CPUs and 16 cores. To work around this issue user has to do the following steps manually in Deployment Server for Windows PE X64 image. 1. Go to Start->Run->type cmd. 2. Go to %ALTIRIS_SHARE%\Deployment Server\PXE\Images\MenuOption131\X64 3. Run bcdedit /store pxeboot.bcd /set {default} numproc 2 4. PXE Boot the target server to Windows PEx64. Note:Please don't regenerate the pxe image after this above modification.if user regenerates pxe image then the above modifications done will be lost 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/Professional Windows Server 2008 R2 SP1 x64 Enterprise/Standard Windows Server 2008 IA64 Windows Server 2008 R2 IA64 Hyper-V Server 2008 x64 Hyper-V Server 2008 R2 x64 VMware ESX 4.0 U3 VMware ESX 4.0 U4 NEW! VMware ESX 4.1 U2 NEW! VMware ESXi 4.1 U2 NEW! VMware ESXi 5.0 Red Hat Enterprise Linux 5.7 x86 and x64 AS/ES NEW! Red Hat Enterprise Linux 6.1 x86 and x64 NEW!

4 Red Hat Enterprise Linux 6.2 x86 and x64 NEW! SUSE LINUX Enterprise Server 10 SP4 x86 and x64 SUSE LINUX Enterprise Server 11 SP1 x86 and x64 Windows XP x86 Professional Windows 7 For Workstation Blades 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: Windows Server 2003 and Windows Server 2008 IA64 require minimum SP2. Windows XP requires minimum SP2 Windows client operating systems are only supported on blade PCs and Blade Workstations. To deploy VMware ESXi, using only the HP-provided ESXi distributions is supported. These distributions already contain HP Agents and drivers. For the HPprovided distributions, refer to HP VMware ESXi 4. The Altiris Deployment Agent for Linux (ADLagent) does not support ESXi and is not installed. Image deployment for Linux updates or service packs that were supported by a previous RDP version are still supported. For additional deployment information, refer to Knowledge Base article How To Capture And Deploy A Linux Image (Article ). Supported ProLiant Targets Not every target platform configuration is supported by the Operating System support list. Refer to certification matrices: Windows support for HP ProLiant Servers Linux certification and support matrix - HP ProLiant servers ProLiant server VMware support matrix Additionally, to deploy VMware ESX, a driver CD may be required for certain ProLiant models. Including the driver CD is not supported. Refer to the VMware Compatibility Guide for additional information. Refer to support documents for additional information on how to deploy an operating system: Knowledge Base article Servers With Multiple Disks Deployment Support (Article ) Knowledge Base article How To Perform a Boot From SAN Installation (Article ) Knowledge Base article Multipath SAN Deployment Support (Article ) Knowledge Base article Fibre Channel Over Ethernet (FCoE) And Internet Small Computer System Interface (iscsi) Deployment Support (Article ) For virtual machine deployment, Windows Server 2003 x86 or x64, Windows Server 2008 x86 or x64, and Windows Server 2008 R2 x64 may be deployed to a virtual machine created within one of the supported virtualization hosts, as well as, VMware ESXi 3, Windows Server 2008 Hyper-V x86/x64, or Windows Server 2008 R2 Hyper-V. However, Windows Server 2003 x64 deployments to virtual machines hosted by Hyper-V Server 2008 or Hyper-V Server 2008 R2 are not supported. For additional deployment information, refer to Knowledge Base article Virtual Machine Deployment Support (Article ). 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. Deployments are supported when the target server contains the HP SmartArray B110i controller. This is the Intel SATA controller which becomes HP SmartArray B110i when set to RAID mode. BL260c G5 BL280c G6 BL2x220c G5 BL2x220c G6 BL2x220c G7 BL460c G5 BL460c G6 BL460c G7 [2] BL465c G5 BL465c G6 BL465c G7 [2] BL490c G6 BL490c G7[2] BL495c G5 BL495c G6 BL680c G5 BL685c G5 BL685c G6 BL685c G7 DL120 G5 DL120 G6 DL140 G3 DL145 G3 DL160 G5 DL160 G6 BL620G7 DL165 G5 DL165 G6 DL165 G7 DL170h G6 DL180 G5 DL180 G6 DL185 G5 DL320 G5 BL680G7 DL320 G6 DL360 G5 DL360 G6 ML110G7 DL360 G7 DL380 G6 DL380 G7 DL365 G5 DL370 G6 DL380 G5 [1] DL385 G2 DL385 G5 [1] DL120G7 DL385 G6 DL385 G7 DL580 G5 [1] DL580 G7[2] DL585 G2 DL585 G5 DL585 G6 DL585 G7[2] DL785 G5 DL785 G6 DL980 G7[2] DL620c G7[2] ML310 G5 ML330 G6 SL160sG6 DL680c G7[2] ML310 G4 ML370 G5 ML370 G6 SL160z G6 SL165z G6 SL165z G7 SL170s G6 SL170z G6 SL390s G7 SL165sG7 ML350pGen8 [2] NEW! DL360pGen8 [2] NEW! DL380pGen8 NEW! BL460cGen8 NEW! SL230Gen8 NEW! SL250Gen8 NEW!

5 SL270Gen8 NEW! DL160Gen8 [2] NEW! ML380pGen8 [2] NEW! DL460cGen8 [2] NEW! [1] For SAN, only Boot from SAN storage is supported. Brocade FC HBA is only supported for Windows. [2] VMware ESX 4.0 Update 3 and ESX/ESXi 4.1 Update 2 and ESXi 5.0 are supported on ProLiant G7 and Gen8 servers but require an HP provided custom ESX/ESXi distribution. Refer to Knowledge Base article How To Create An ESX Deployment Job To Install An HP Provided Custom ESX Distribution To Support ProLiant G7 Servers (Article ). Supported Integrity Targets Refer to support documents for additional information on how to deploy an operating system: Knowledge Base article Integrity Server Deployment Support (Article ) Knowledge Base article Servers With Multiple Disks Deployment Support (Article ) Knowledge Base article How To Perform a Boot From SAN Installation (Article ) Knowledge Base article Multipath SAN Deployment Support (Article ) 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 [3] BL860c i2 [4] BL870c [3] BL870c i2 [4] BL890c i2 [4] rx2660 rx3600 rx6600 rx7640 rx8640 Superdome sx2000 rx2800 i2 [3] For direct attached storage (DAS), RAID 1 configuration is only supported. [4] For the BladeSystem Integrity i2 servers, only Windows 2008 R2 deployments are supported. The servers require minimum system firmware version and management firmware version Supported Other Targets WS460c G6 Workstation Blade Supported Option Cards NEW! HP Smart Array P420 HP Flex-10 10Gb 2-port 530FLB Adapter [5] HP Flex-10 10Gb 2-port 530M Adapter[5] HP Ethernet 10GB 2-port 530FLR-SFP Adapter[5] HP Ethernet 1GB 4-port 331FLR Adapter HP StorageWorks CN1000E Dual Port Converged Network Adapter HP FlexFabric 10GB 2-port 554M Adapter HP FlexFabric 10GB 2-port 554 FLB Adapter HP NC552SFP 2-port 10Gb HP Ethernet 1GB 4-port 331T Adapter HP Smart Array P420i HP Smart Array P222 HP FlexFabric 10Gb 2-port 554FLR-SFP Adapter HP Smart Array P220i [5] Deployment of Red Hat Enterprise Linux 6.1 x86 and x64 is not supported.