HP Insight Dynamics 6.0 Release notes

specifies data disks. You can modify the storage pool entry allocated to the server to add
data volumes, and then continue the request.
When NPIV is supported on Integrity blades running HP-UX and HP OpenVMS, you will be
able to define separate storage pool entries for the boot volume and for the data volumes intended
to be allocated to the same physical server. This will allow a flexible management model of
storage pool entries that contain only boot volumes, and other entries that contain only data
volumes. Insight Dynamics can combine these for use on a single server.
Install Microsoft Sysprep tool for customization of Windows 2003 guests on Hyper-V after installation
The Microsoft System Preparation (Sysprep) tool, which is required for customization of Windows
2003 guests on Microsoft Hyper-V, is not retained on the CMS after upgrading from previous
versions of Insight Software. Without these tools, customization of Windows 2003 guests on
Hyper-V results in failures.
Suggested action To enable customization of Windows 2003 guests on Hyper-V, install the
Microsoft Sysprep tool on the CMS in the folder C:\Program Files\HP\Insight Control
virtual machine management\Sysprep\2003 after the installation or upgrade of Insight
Software 6.0.
Console access to provisioned virtual servers from operating systems and browsers
Launching a console to a provisioned virtual server (VM) hosted on VMware ESX 3.5, ESX 4,
ESXi 3.5, and ESXi 4 VM hosts is supported using Microsoft Internet Explorer and Mozilla Firefox
browsers running on Windows XP and Windows 2003 operating systems.
Browsing to user interface requires default Systems Insight Manager port
HP Systems Insight Manager is installed with a default port of 50000 in the JBoss container.
Browsing to the Insight Orchestration user interfaces, for example, Designer, depends on this
port value.
Suggested action Do not modify the Systems Insight Manager default port of 50000 in the JBoss
container.
Major issues
Physical server provisioning using Insight Control server deployment fails during final personalization
step when the CMS is configured with an automatic proxy configuration script in IE
Using Insight Orchestration for physical server deployments via HP Insight Control server
deployment fails during the final personalization step. This can occur when there is a problem
or delay communicating with the automatic configuration script configured in Microsoft Internet
Explorer. The problem is in Windows .NET, and the proxy configuration is shared between IE
and .NET.
The Insight Orchestration log for the failed deployments contains lines similar to the following:
ERROR com.hp.hpio.sbapi.tasks.CreatePhysicalServerTask.execute - Error
personalizing OS with host uuid: 38C77BED-9FAE-4886-8C06-0F536BA46507
com.hp.hpio.sbapi.exception.AresAdapterException: Deployment server did not
accept customization data.
The log for the connector software that drives Insight Control server deployment, C:\Program
Files\HP\Systems Insight Manager\logs\Alc1_0.0.log, shows that the operations
that perform the customizations are timing out.
Suggested action 1 Configure Internet Explorer with an explicit proxy server address and
appropriate exceptions instead of using an automatic configuration script. Check "bypass proxy
server for local addresses" if the server deployment server is on the CMS. Otherwise, make sure
to include the address of the server deployment server in the Exceptions field of the Advanced
options for configuring a proxy server.
HP Insight Orchestration 21