Hyper-V synthetic Network Interface Card (NIC) reinitializes on new Provisioning Services target. During the synthetic NIC reinitialize at boot, it delays any software to use the interface. Windows redetects the NIC as a new device and increments the name of the device, for example, “Local Area Connection #2”.
The IMA service might timeout and fail to start.
 

Background

The default network adapter on all VMs created in Hyper-V is a synthetic network adapter, whose driver is included with the Integration Components. However, the synthetic network adapter cannot be used, as its software driver does not load until the Integration Services are installed in the VM. The synthetic NIC and its driver are called "synthetic" because they are not emulations of any "real" NIC or NIC driver, and there is no existing driver for any OS to be installed.

Please Note: This is a workaround and not a resolution, this workaround may not apply to all environments.

To address this issue, new virtual machines must have the same hardware profile as the virtual machine that virtual disk was captured from.

To accomplish this, use the Microsoft System Center Virtual Machine Manager (SCVMM) clone function.

When the virtual disk has been captured, open the SCVMM console.

1. Right-click on the virtual machine and choose Clone.

   

2. When the wizard appears, choose a new name for your virtual machine and click Next.

   

3. On the Configure Hardware screen, generate new MAC addresses for the NIC.

   

4. On the next screen, choose where to place the virtual machine.  This procedure places it on the host. Note: If the virtual machine is stored in the library, the same behavior as specified earlier occurs.

   

5. Specify the host where the virtual machine will reside.

6. Specify the location where the virtual machine will be stored.

7. Confirm that the NICs are on the correct virtual networks.

   

8. Specify any additional properties for the virtual machine.

9. On the last screen, click Create to build the virtual machine.

After building this first clone machine, use it as a template for any additional virtual machines.

If the Write Back Cache (WBC) is located on the Server, any locally attached hard drives should be removed. If the WBC is to be located on the target device hard drive, add a hard drive to the virtual machine.

Using WBC on the Hard Drive

If using WBC on the hard drive, add a hard drive to the clone template.

1. Open the settings on the virtual machine and add hard drive of the appropriate size for your virtual disk image.

2.  Change the virtual disk mode to Private and boot the clone template virtual machine.

3.  Use the Disk Management console to partition and format the hard drive.

4.  Run the XenApp Server Role Manager and prepare the server for imaging and provisioning.

5.  After the machine is shutdown, follow the preceding steps to clone this virtual machine to deploy to a new target virtual machine.

The new virtual machine will have a local HDD prepared for use with Local HDD caching.

---

Problem Cause

There is a limitation of Hyper-V synthetic network cards.

In addition, the behavior has been caused by Hyper-V virtual hard disk associated with another Hyper-V virtual machine.

Microsoft is aware of the behavior and it is explained in the article:
http://blogs.technet.com/b/jhoward/archive/2008/07/22/hyper-v-why-is-networking-reset-in-my-vm-when-i-copy-a-vhd.aspx

“The reason for this is that the “GUID” of the original network adapter was stored in the “lost” configuration. So when a new configuration is created, when a synthetic NIC is added, a new GUID is generated. When the virtual machine starts, plug-and-play see this new NIC, as a completely different NIC, just like as you would in a physical machine.”

Hyper-V Synthetic Network Interface Card Reinitializes on New Target Devices

How to Manually Create Hyper-V GEN2 Provisioning Services Target Devices