Submitting a feature request, referring to a long running ticket #114231
Autoscale or manual Entra-only VM creation fails at the ‘check if host exists’ step, because it is looking for ‘hostname’, and sees ‘hostname.suffix.com’. This is due to the VNet's DNS pointing to AD servers (which are being retired). So Nerdio creates and destroys the VM over and over, until auto-scaling is turned off.
In the Azure portal the session host is named 'hostname', and the tag also says ‘hostname’, but if you do a DNS lookup, it shows a hosname.suffix.com response. It's a showstopper for deploying AVD hosts into an existing environment, where they have a VNet with AD DCs and other servers, but are going to move to Entra-only, so building AVD Entra-only.
Noting we have AVD internally and otehr clients with AVD, including one who has on-prem AD – this particular issue seems to be because the client's VNet's DNS points to AD DCs in the VNet (and they need it that way until they nuke AD)
If would be great if Nerdio were able to recognise it had built perfectly good session hosts and not destroy them straight away.
Thanks
Dave
---------
Hi David,
Just received an update from the product team.
During host provisioning, FQDN is used to find the host for the vm. You can find these steps in the job:
- Join to ARM AVD
- Check if host exists <-- this step uses projected FQDN calculated based on the AD profile, tag is not used here. Projected FQDN is a VM name for Entra ID profile.
They are currently checking for a workaround that doesn't require a code change, but in the mean time they would require a feature request.
Kind Regards,
Ben Sadler
Comments (1 comment)