Cloud MCS EnableDHCP error

[Erwin Vos]

We are implementing Citrix Cloud in our environment. We have a base image (azure marketplace) and after we created a snapshot we use this to create a machine catalog. But the creation fails at EnableDHCP error. We did a test to disable the service Network Setup Service in the base image and with the newly created snapshot the machine catalog was created but machines not registered and not in DNS, probably of the service. We have a windows 10 multi session image with the 2112 VDA installed on it. What can we do to fix this? 

[James Kindon]

this is known issue, fire this against your environment

Set-ProvServiceConfigurationData -Name ImageManagementPrep_Excluded_Steps -Value EnableDHCP

https://www.citrix.com/blogs/2016/04/04/machine-creation-service-image-preparation-overview-and-fault-finding/

[Erwin Vos]

Hello,

 

i saw indeed it was a known issue. But because we do this in Citrix Cloud we don't have a DDC or XenApp server where we can execute the script because the infrastructure is hosted by Citrix. Or there must be an other way to execute the ps.

[James Kindon]

Download the Citrix cloud powershell sdk - same rules apply as on prem, you can do pretty much anything via powershell 

[Erwin Vos]

I will do that and try to get it working. Thanks for your quick reply

[Erwin Vos]

So I tried as you described but the thing is that as a customer you aren’t allowed to change the landing plane which is managed by Citrix. So your solution is only applicable for on-prem sites. We walked through the mcs wizard and finally we were able to solve the problem. When selecting the hardware there are a v3, v4 and v5 series. It seems our issue is generated by the v5 series. With the v3 and v4 we successfully create a mcs catalog with a working win10 multi session vm. So if you making the transition to cloud you aren’t allowed to change the most site settings. 

[James Kindon]

I didn’t realise that exact param was locked in cloud - support should be able to change that for you if you cannot 

 

I know this specific issue is on the radar with the MCs team, dhcp prep in public cloud isn’t needed 

[Erwin Vos]

As far as we can see now it is an issue in the v5 series. So for now we continue with the v4 which is working.