The PVS CVAD Setup Wizard fails to create new virtual machines when running on a VMware Hypervisor.  vCenter displays an error when the CVAD Setup Wizard fails to complete its task similar to the following:

Unable to find device or file / Failed to clone a VM, error: Invalid configuration for device "0"

CDF Traces Taken From PVS Server Where Console Points:

PVS_Dll_EnterpriseManager_AO,_#dotNet#_,0,,1,Error,"XdSetupFinish: Clone for device PVS-TEST-01 exception: System.Exception: [XX-Datacenter-Citrix-VLANXXX] Invalid configuration for device '0'. ---> 
Citrix.Xip.XipException: Invalid configuration for device '0'.

CDFLogFile1.csv  PVS_Dll_EnterpriseManager_AO,_#dotNet#_,0,,5,Information,"Citrix Virtual Desktop Setup Wizard: Cannot clone device PVS-TEST-01 on the Hypervisor    [XdSetupFinish.cs(2130): createOneVM]",""

Citrix is not responsible for and does not endorse or accept any responsibility for the contents or your use of these third party Web sites. Citrix is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Citrix of the linked Web site. It is your responsibility to take precautions to ensure that whatever Web site you use is free of viruses or other harmful items.

Workarounds:

1.  Where possible change the network port group name back to its original settings in vCenter.  See VMware KB article 1017348 for details.

2.  In vCenter under the vSwitch properties explicitly deny access to the vLAN for the user running the wizard in the PVS console.  In the vCenter vSwitch properties for the VLAN in question create a new rule, add the user and be sure the role = no access.

3.  Deploy new CVAD Machine Catalog if required.

---

Problem Cause

When creating a new virtual machine the Provisioning Services CVAD Setup Wizard will first clone the template in question.  Once the template is cloned the mis-matched network interface port group is caught during VM's resource enumeration and the process comes to a halt.  This behavior has been observed when the VM's being created have a different network port group ID than the network port group ID associated with the original deployed VM's. Provisioning Services appears to reference a CVAD DB record for this network port group ID that is statically defined.  vCenter appears to fail based on the reference of stale parameters.

This issue is currently under further investigation.

https://kb.vmware.com/s/article/1017348