The upgrade from 2203 LTSR CU4 to 2402 LTSR RTM in our test environment has caused a new behavior. In DNS, our VDAs/machines don't reside in "domain.com". Our DHCP server instead hands out addresses ending in "vapps.domain.com". At some point in the past, MCS wanted to assign names ending in "domain.com" to all our VDAs. We were able to fix this in 7.6 LTSR by setting DisableDomainInjection to "true" and have left that setting in place ever since. After the upgrade to 2402 LTSR, any new catalogs (or even adding machines to existing catalogs) results in Citrix's thinking the VDA should reside in "domain.com", and app launches fail - probably as a direct result. Does anyone know of a way to have the proper domain assigned to machines, or do we just wait for CU1? 🙂 Note: In the screenshot, you can see how a machine created before the 2402 LTSR upgrade (ending with an "A") has the correct domain assigned, but a machine created after the upgrade (ending with an "L") does not.

did that setting get reverted? If you do a Get-ProvServiceConfigurationData, does it show that setting?

Hi Steve. The setting wasn't reverted, and I even re-ran the Set-ProvServiceConfigurationData -Name DisableDomainInjection -Value true command just to be sure.

HyperV or AzureVM?

In my case, our impacted test environment is on XenServer 8. (Our production environment is on VMware, but I haven't upgraded it to 2402 LTSR.)

gotcha, was just reviewing this one... https://updates.cloud.com/details/pmcs34792/ from https://community.citrix.com/forums/topic/251153-is-it-possible-to-change-the-dnsname-f[…]e-a-subdomain-that-isnt-actually-part-of-active-directory/

I went ahead and put in a ticket. I'm not super optimistic, but maybe they'll come back with something. 🙂

yeah good call, let us know if you find something

I spoke with Citrix support yesterday (Monday) and the missing subdomain shown above may just be cosmetic. The technician said he'd report the behavior and that it might be addressed in a later release. In preparing for the call with tech support, I looked in Studio and to my surprise the most recently-added machine actually HAD updated its subdomain over the course of the weekend. (???) So I had to create another machine in the catalog so that he could witness the undesired behavior. As an aside, the real reason that newly-added machine wasn't accepting application launches was that it lacked membership in that darn "Windows Authorization Access Group" AD group. That step is easy to forget, and became required in our environment after we implemented FAS, even though we don't have multiple domains.