HP Insight Control Virtual Machine Management 7.3 User Guide

VMM does not support remote WMI mapper configuration with only IPv6 address
VMM does not support and communicate to remote WMI mapper when the mapper is configured
on a machine with IPv6 address.
To resolve this issue, you must configure the WMI Mapper on either an IPv4 or a dual address
machine.
VMM does not register ESX Hosts when HP SIM has IPv6 enabled
When you discover either a vCenter node or VM Host with FQDS, and if FQDN has both IPv4
and IPv6 addresses, then the primary IP address for those systems can either be IPv4 or IPv6 and
interchange over time depending on the discovery. You need to lock the primary IP address to
IPv4.
To lock the primary IP address in the System page, navigate to Tools & Links ⇒ Edit System
Properties.
You can choose an IP from the primary IP list and enable the check box.
Microsoft Windows 2008 SP2 guest on Microsoft Windows 2008 SP2 Hyper-v is
not able to populate the IP address in the LSM\SIM UI
WMI query does not provide IPv4 address for Microsoft Windows 2008 SP2 guest on Microsoft
Windows 2008 SP2 Hyper-v.
To resolve this issue, you must discover the VM with IP address and the same reflects in LSM\SIM
UI too.
Customizing the Windows VM more than 3 times corrupts the virtual hard disk
To resolve this issue, set the following registry keys, which enables you to customize the guest OS
multiple times:
• HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\
GeneralizationState\CleanupState:2
• HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\
GeneralizationState\GeneralizationState:7
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersio\
SoftwareProtectionPlatform\SkipRearm:1
Microsoft Windows 2012 linked clone guest customization fails
In ESX server, when you try to customize Microsoft Windows 2012 linked clone guest having a
shared disk on VC5.10b with ESXi5.1 and ESXi5.1U1 hosts, the customization fails.
This is the limitation from VMWare for Microsoft Windows 2012 linked clone guest.
Microsoft Windows 2003 guest login fails
In ESX server, when you assign autologon as true for the Microsoft Windows 2003 guest, it
automatically fails to login to the Microsoft Windows 2003 guest.
To resolve this issue, on ESX host, enter the credentials manually to the Windows 2003 guest.
Microsoft Windows 2012 and Microsoft Windows 2012 R2 guest NIC customization
fails for static IPv4 on Microsoft Windows 2012 R2 host
If you try to sysprep the guest using the command C:\Windows\System32\Sysprep\
Sysprep.exe on the guest VM, it does not set the static IPv4 address, but successfully sets the
IPv6 address. Simultaneously, the IPv4 gateway successfully sets, but other fields like IP address
and Subnet mask are disabled for IPv4.
Insight Control virtual machine management functions 37