Problem: Nerdio Manager is currently unable to handle the following scenario (and similar) which is properly handled by the AVD platform-native management plane:
1) Deploy Entra-joined AVD session host with Nerdio Manager.
2) Assign Intune policy that sets Primary DNS Suffix on AVD session host.
Current Nerdio Manager behavior: VM is no longer "found" in Az subscription and Nerdio Manager is unable to automatically manage or perform automation tasks on that session host.
Current AVD platform behavior: RDAgent telemetry back to Microsoft includes the updated FQDN, the AVD platform backend automatically updates the Session Host display name while maintaininbg the existing session host <-> Azure VM resource ID mapping.
Root cause: Nerdio Manager appears to exclusively rely on the VM-resource level NWW_VM_FQDN tag for matching AVD session hosts to Azure VM resources, but this tag is only set once (at time of Nerdio deploying the VM resource). There does not appear to be any fallback logic within Nerdio Manager to automatically parse or otherwise handle the AVD platform session host API data that correctly maintains AVD session host to Az VM resource ID mappings on VM DNS suffix / FQDN change.
This limitation is not mentioned in any existing public Nerdio documentation (but is known by Nerdio Support). There are various types of customer workarounds to this, but this is a scenario that customers shouldn't have to work around in the first place as the underlying AVD platform does not have this limitation.
Comments (1 comment)