2203 LTSR MCS provisioning DHCP not set

[Dominik Volk]

Hello eveyone,

 

we migrated our Citrix infrastructure to 2203 LTSR, which in retrospect was not the smartest thing to do.

At the moment our environment looks like this:

• Virtual infrastructure on VMware vSphere 7.0.3 and ESXi server on 6.7U3, 18828794
• Microsoft Active Directory + DNS + DHCP,  Windows Server 2019
• Microsoft SQL Server 2016 SP2,  Windows Server 2016
• Citrix ADC VPX, NS13.0 83.27.nc (used for external connection only)
• Controller 1, 2203 LTSR, Windows Server 2019
• Controller 2, 2203 LTSR + license server 11.17.2 build 37000,  Windows Server 2019
• Storefront 1, 2203 LTSR with Hotfix (CTX399424/CTX457757) + Director 2203 LTSR,  Windows Server 2019
• Storefront 2, 2203 LTSR with Hotfix (CTX399424/CTX457757) + Director 2203 LTSR,  Windows Server 2019
• Windows Server 2019 as file server for UPM and FSLogix
• VDA 2112,  Windows Server 2019, full desktops (production)
• VDA 2203 LTSR,  Windows Server 2019, full desktops (testing)
• VDA, Storefront, Controller and file server share the same /24-network. Database, Active Directory, DNS and DHCP are localed in another network. Netscaler is placed in DMZ.

 

We deploy our VDA with MCS provisioning.

With 2203 LTSR there is a problem with setting the network adapter to DHCP at the stage of preperation the golden image. The adapter has the same static IPv4 configured as the snapshot on which the catalog is based. Before the upgrade to 2203 LTSR the adapter was automatically configured for DHCP.

 

With the following command set on our controller

Set-ProvServiceConfigurationData -Name ImageManagementPrep_NoAutoShutdown -Value $True

and this registry value set on the VDA

[HKEY_LOCAL_MACHINE\Software\Citrix\MachineIdentityServiceAgent]
"LOGGING"=dword:00000001

we look into the process of preperation and find this in the image-prep.log:

[...]
Enabling DHCP on all network adapters
Netsh tool completed, exit code 0
Netsh executed command 'int ipv6 show addresses' successfully
ReadIpv6Addresses: Found 0 addresses.
EnableDHCP: Checking adapter, Ethernet-Adapter für vmxnet3
EnableDHCP: Checking configuration, Ethernet-Adapter für vmxnet3
Skipping DHCP enablement for Ethernet-Adapter für vmxnet3, adapter is not IPEnabled
[...]

To rule out some side effects from our installed software we tested these on a fresh and patched install of a Active Directory domain joined Windows Server 2019 only with VMware Tools.

We tested VDA 2112, 2203 LTSR and 2203 LTSR with IPv6 enabled in the NIC. (usually we uncheck Ipv6 in the Windows network adapter)

In the VDA setup we unchecked "UPM" and added "MCS Storage Optimization" and "Use-Real-Time -Audio Transport for audio".

In the Machine Catalog wizard we configure MCS and MCS Storage Optimization with a minimun funcional level of 2106.

As expected on 2203 LTSR, regardless whether IPv6 is enabled or not, the IPv4 adapter settings are not changed to DHCP, with the same output in the image-prep.log as above.

However on 2112 everything is working as it should be with following output in the image-prep.log:

[...]
Enabling DHCP on all network adapters
Netsh tool competed, exit code 0
Netsh executed command 'int ipv6 show addresses' successfully
ReadIpv6Addresses: Found 0 addresses.
EnableDHCP: Checking adapter, Ethernet-Adapter für vmxnet3
EnableDHCP: Checking configuration, Ethernet-Adapter für vmxnet3
DHCP not enabled, enabling for Ethernet-Adapter für vmxnet3
Netsh tool competed, exit code 0
Netsh executed command 'interface ip set address name="Ethernet0" source=dhcp' successfully Ethernet-Adapter für vmxnet3
Netsh tool competed, exit code 1
[...]

 

With this tests done we estimate the problem is related to VDA 2203 LTSR.

As a workaround we enable DHCP on the preperation VM manually. In theory you could enable DHCP on your image also.

 

Can someone confirm this behaviour and/or give advice or information about this topic?

 

Kind regards

[Pierre-Alain Parent1709160271]

Hi,

Yes i received the same feeback.

The fix is going to be available in the 2206 and 2203 CU1 VDA.

 

Regards.

[Martin Nygaard Jensen1709162950]

Same behavior here. Windows Server 2019 template with static IP. VDA 2112 works.

Upgrading to VDA 2203, DHCP no longer gets activated on the NICs.

The customer is also running vmware vsphere. Version is unknown to me.

NICs are vmxnet3.

 

The issue could possibly be related to a windows update instead, as these get deployed on the template during build.

 

I have reverted to using DHCP on the template servers aswell, which solves the issue.

 

EDIT: You can disregard on-prem backend infrastructure. My environment is Citrix Cloud DaaS.

[Brady Bachhofer]

Also seeing this same issue... getting duplicate IP's on the worker servers that MCS creates since upgrading to 2203 LTSR VDA on Windows Server 2019

[Dominik Volk]

Thank you for your response.

We will open a case for this issue.

 

On 5/31/2022 at 10:59 AM, Martin Nygaard Jensen1709162950 said:

The issue could possibly be related to a windows update instead, as these get deployed on the template during build.

I think we can rule Windows Updates out. As I mentioned before we tested this on a fresh and patched install of Windows Server 2019. With VDA2112 it worked. With VDA2203 LTSR it doesn't.

 

17 hours ago, Brady Bachhofer said:

Also seeing this same issue... getting duplicate IP's on the worker servers that MCS creates since upgrading to 2203 LTSR VDA on Windows Server 2019

Same here, we've a testing deployment of 2203. We only noticed that as we deployed another machine.

[Pierre-Alain Parent1709160271]

Hi Dominik,

 

I have the same problem. If you have a private fix. I would like the number please. It is possible to indicate the case number ? I am going to open a ticket and indicate you number please.

 

Thank you.

[Pierre-Alain Parent1709160271]

Hi,

 

If you change the adapter in DHCP just before the snapshot. The clone work correctly.

The problem only exists with static adapter on the Master.

 

Do you have any feedback from support ?

 

 

[Pierre-Alain Parent1709160271]

Hi,

I have open a case #81241400.

 

Regards.

[Dominik Volk]

Hi everyone,

 

a brief update from us.

We opened a case and work on a solution with support. There is no fix yet. Only workarounds. We post here if there is something to share.

 

On 6/8/2022 at 10:27 AM, Pierre-Alain Parent1709160271 said:

If you change the adapter in DHCP just before the snapshot. The clone work correctly.

The problem only exists with static adapter on the Master.

We tested this on suggestion from support also and can confirm that it will work.

But we found another strange behaviour:

 

Our DHCP server is a Windows Server 2019 virtual machine.  We use it only for Citrix VDA Worker and use DHCP reservations only.

First we configure a DHCP reservation for the Master, so you can work with it as normal. Then shutdown the vm and take a snapshot and deploy a new catalog. After that MSC deployment is normal but the worker servers get the DHCP IP address we configured for the Master. Even though the worker have different MAC addresses. And even if we configure new DHCP reservations for the workers they get the address from the Master. Of course only one worker get the IP. The others don't get anything.

 

As this seems to be to strange to be true. We guess this may be some Windows specific behaviour like remembering DHCP lease or something environmental.

So we tested again, but this time without setting up a DHCP reservation for the master. So the Master doesn't get an IP address.

With this configuration and DHCP reservations set up for the worker everything worked as it should be.

 

As mentioned in our original post you can set DHCP on the adapter manually if you halt the preperation process with the follwing command on DDC:

Set-ProvServiceConfigurationData -Name ImageManagementPrep_NoAutoShutdown -Value $True

On 6/7/2022 at 9:49 AM, Pierre-Alain Parent1709160271 said:

It is possible to indicate the case number ?

Sure, its #81229874

 

Kind regards.

[Pierre-Alain Parent1709160271]

Hi,

Thank you for update.

 

Do you know if Citrix search a solution because i think that is a bug. It works with older versions.

 

Regards.

[Dominik Volk]

22 hours ago, Pierre-Alain Parent1709160271 said:

Hi,

Thank you for update.

 

Do you know if Citrix search a solution because i think that is a bug. It works with older versions.

 

Regards.

Hi,

 

We received feedback that it is definitely a bug. However, there will be no private fix for it. According to Citrix Support, the bug will be fixed in the next CR and LTSR. Only the workarounds that we have already found out here remain.

 

Kind Regards

[lbellotto]

On 6/15/2022 at 9:20 AM, Pierre-Alain Parent1709160271 said:

The fix is going to be available in the 2206 and 2203 CU1 VDA.

 

Hi,

We deployed the 2203 LTSR this weekend and had the same problem. Is there a release date for the CU1

 

[Julien Berne]

On 7/11/2022 at 9:12 AM, lbellotto said:

 

Hi,

We deployed the 2203 LTSR this weekend and had the same problem. Is there a release date for the CU1

 

Hey team hello,

 

Got the same issue as all of you with CVAD 2203. Thanks to the 2203 CU1, only upgraded the VDA (master), all is working better

 

2203 CU is already released :)

https://www.citrix.com/downloads/citrix-virtual-apps-and-desktops/product-software/citrix-virtual-apps-and-desktops-2203ltsr-cu1-all-editions.html

 

Cheers,

Regards.