HP Insight Control Virtual Machine Management 7.3 User Guide

To resolve this issue, set the IPv4 address manually on the guest.
IPv6 Customization fails on Microsoft Windows 2003 systems
This is because Microsoft Windows 2003 does not support IPv6 customization.
CPU properties for powered on VM fails to update
In ESX, when you enable the Hot ADD CPU feature on a NON-OS VM, and try to update the CPU
properties for a powered on VM, it fails to update. This happens from both VCenter UI and ViSDK.
This is the limitation from VMWare for NON-OS VM, where CPU properties are not updated for
a powered on VM.
VM guest retains the static IPV6 addressing mode on the NIC assigned to the template
The static IPv6 address of Microsoft Windows 2008 SP1 template when deployed on Microsoft
Windows 2012 R2 host is retained, even if you specify to use DHCP from HPIO.
When assigning the DHCP address to the Microsoft Windows 2008 SP1 VM, which is created
on Microsoft Windows 2012 R2 host, always set DHCP address to the guest while creating the
template.
Limitation with diskpath and controller ID in multiple data stores on ESX
In ESX server, when you try to copy or move a guest VM, provide multiple data store location, and
specify incorrect SCSI controller ID where the disk is not attached, the copy or move operation
fails. You might receive an error message, which Insight Control Virtual Machine Management
does not handle.
When you try to provide specific directory name inside a data store for copy or move operation
with multiple data stores, guest VM is copied or moved to the folder with target VM name, but not
to the specified directory. The operation succeeds, but VMM does not change the directory name.
Unable to perform power on or off operations on a virtual machine through virtual
machine management
The power on or off operation on a VM through Insight Control virtual machine management fails
when you restore the VM from a backup. The backup and restore is performed using the HP Data
protector software. The getVmDetails API will show incorrect data for the backed up VM.
To Unregister/register the VM in vCenter:
1. Select the VM in vCenter (ensure that VM is in the powered off state) and right-click to select
Remove from Inventory. This unregisters the VM from inventory.
2. Navigate to vCenter Inventory→Datastores and Datastore clusters.
3. Select the datastore on which the VM was residing before and right-click to browse the
datastore.
4. Select the .vmx file of the VM in the datastore and right-click to select the option Add to
Inventory. This completes the VM registration. Now you can perform power on or off operations
on the VM from virtual machine management.
Customization fails for Microsoft Windows 2003 R2 Guest VM on VMWare vCenter
4.1 U2 with ESXi 4.1 host.
To solve this issue, set the parameters on the virtual machine manually using vCenter Settings option
or directly on the virtual machine.
38 Troubleshooting