After uninstalling Hyper-V role from MCS master image to remove Hyper-V Virtual Ethernet adapter the MCS catalog update process does not complete
Article ID: CTX696446
Updated On:
Description
Azure VM in Citrix DaaS has two network adapters, one domain-connected Microsoft Hyper-V Network adapter and Hyper-V Virtual Ethernet adapter
Post removing the Hyper-v role from the MCS master image the Hyper-V Virtual Ethernet adapter is removed. However, the MCS catalog update process does not complete.
The machine creation will stay with “creating” status and doesn’t complete the machine creation.
Cause
By default, the the image from Azure Market place doesn't have Hyper-V role enabled. The Hyper-V Virtual Ethernet adapter is created when you create a Virtual Switch in Hyper-V. After the removing the Hyper-V role the Hyper-V Virtual Ethernet adapter remains in disabled state or orphaned device and it is visible when you enable hidden devices in Device Manager.
To show hidden or disconnected devices in Windows Device Manager, open Device Manager, click the View menu, and select Show hidden devices and expand Network Adapter.
If you see the Greyed-out Hyper-V Ethernet network adapters (Orphaned devices) then the virtual switch was not removed from Hyper-V Manager before removing the Hyper-V role.
Resolution
Please do not enable Hyper-V role with the Virtual Switch created on Hyper-V
OR
Remove the Greyed-out Hyper-V Ethernet network adapters, orphaned devices from the Device Manager.
Issue/Introduction
Azure VM in Citrix DaaS has two network adapters, one domain-connected Microsoft Hyper-V Network adapter and Hyper-V Virtual Ethernet adapter
Post removing the Hyper-v role from the MCS master image the vEthernet adapter is removed. However, the MCS catalog update process does not complete
