Insight Dynamics 6.1 Release Notes

NOTE: The Hyper-V host version is shown in the Platform column in the Available Target
Hosts table on the activate or move logical server target screen. The host is a Hyper-V R1 host if
the host version begins with 6.0 (for example, 6.0.6001 or 6.0.6002 in Windows 2008 Server –
Hyper-V SP1 or Windows 2008 Server – Hyper-V SP2). The host is a Hyper-V R2 host if the host
version begins 6.1 (for example, 6.1.7077 in Windows Server 2008 R2).
Suggested action Be certain that you want to move or reactivate the logical server from Microsoft
Hyper-V R1 to R2 before you complete the operation. After the operation completes, you cannot
move or reactivate the logical server back to Hyper-V R1.
Importing a Microsoft Hyper-V virtual machine with configuration file in default location is not
supported
A Hyper-V virtual machine whose configuration file (.vmx) is in the default location on the hard
disk in \ProgramData\Microsoft Windows\Hyper-V is not supported by logical server
management. You cannot import a virtual machine guest as a logical server if the virtual machine's
configuration file is in this location. There is a limitation in Microsoft Hyper-V that allows HP
Insight Control virtual machine management to re-register the virtual machine if the configuration
file is created in this directory. To prevent issues with reactivation, logical server management
checks the path and rejects any virtual machines with a configuration file in the default location.
iSCSI disk requirements for use with Microsoft Hyper-V virtual machine logical servers
To enable selection of a specific iSCSI data store as the storage definition during logical server
creation or modification, iSCSI disks associated with Microsoft Hyper-V hosts must be a cluster
disk or a shared cluster volume, online, and contain a volume created with a drive letter.
One Microsoft Hyper-V target displayed when activating a logical server created on a cluster disk
volume
A limitation in Microsoft Hyper-V R1 prevents the hypervisor from providing logical server
management with required information about a Hyper-V cluster. The result is that only one
target is shown when you attempt to activate a virtual machine logical server configured to be
created on a cluster disk volume. In Hyper-V R1, a logical server that is high availability
(HA)-enabled can be configured only on a cluster disk volume.
Suggested action Upgrade to Hyper-V R2. In R2, Microsoft corrected the problem so that the
activation of a virtual machine logical server configured to be created on a cluster disk or a cluster
shared volume lists all Hyper-V hosts in the cluster on the target screen.
Virtual machine logical server with more than one storage pool entry is not supported
HP Insight Dynamics does not support a virtual machine logical server with more than one
storage pool entry. Although you are not prevented from creating a logical server, associating
more than one storage pool entry to it, and then activating the logical server, if you subsequently
attempt to reactivate or move the logical server, the operation may fail.
File-based storage pool entry not supported
Beginning in HP Insight Dynamics 6.0 Update 1, file-based storage pool entries are not supported.
Storage pool entries must be SAN-based (or RDM-based in the cross-technology logical servers
technology preview).
File-based storage entries are created by default for all virtual machine logical servers. However,
these entries cannot be inserted into the storage pool or managed on the Modify→Logical Servers
Storage Pools... screen.
Logical server management 29