Symptoms


When configuring a VPG, an administrator can configure a specific Failover/Move and Failover Test IP configuration for each NIC on each source VM.  When undergoing a Live Failover, a Failover Test, or a Move operation, it is possible for a NIC's IP configuration to not change as per its configuration in its VPG.  This solution article explains potential causes for this behavior.




Solution


As explained by the following Microsoft KB article, applications that use the EnableStatic method, such as Zerto Virtual Replication, in the Win32_NetworkAdapterConfiguration class may not always be able to specify a static IP address for a NIC on a Windows-7 or Windows Server 2008 R2-based computer.  In order to resolve this behavior, Microsoft has provided the following Hotfixes:


Windows 7, Windows 2008 R2:

An application that uses the EnableStatic method in the Win32_NetworkAdapterConfiguration class cannot set a static IP address for a network adapter on a Windows 7-based or Windows Server 2008 R2-based computer


Windows Vista:

On a Windows Vista-based computer, an application that uses the EnableStatic method of the Win32_NetworkAdapterConfiguration class may not always set a static IP address for a network adapter


Note that another possible cause for for this behavior is due to having a VMXNET3 adapter configured for a VM running WIndows Server 2008 R2 for a guest OS.  If this is the case, refer to the following VMware and Microsoft KB articles for resolution:


VMware:

Deploying Windows 2008 R2 and Windows 7 templates with vmxnet3 renames the NIC as #2 (1020078)


Microsoft:

"0x0000007B" Stop error after you replace an identical iSCSI network adapter in Windows Server 2008 R2 SP1 or in Windows 7 SP1