Trusted launch security type WVD's "Unavailable" and cannot contact DNS

Thomas Essick 0 Reputation points
2024-09-03T14:38:18.6133333+00:00

We have configured a new multi use WVD/AVD image utilizing "Trusted Launch" security type. Strange behavior is we can deploy/add systems to a host pool. Computers complete the deployment with no errors reported and the computers also join the legacy active directory domain. However, with "Non Trusted Launch" security type WVD's, the FQDN of the asset would be displayed on the session hosts view of the host pool. The "Trusted Launch" WVDs do NOT show FQDN and only display the short host name. These "Trusted Launch" WVD's also show as Unavailable in the session host pool view and cannot be connected to thru the Remote Desktop App. In fact, we can ONLY connect to the "Trusted Launch" WVD's by direct IPaddress RDP. We cannot connect with FQDN. Verified the WVD is in fact joined to the on premise domain. Appears to be something blocking communication with DNS servers. Group Policy has turned local Windows Firewall to "off", so local firewall cannot be the issue. Thoughts?

Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,516 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sai Krishna Katakam 120 Reputation points Microsoft Vendor
    2024-09-04T00:55:46.2566667+00:00

    Hi Thomas Essick,

    Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

    Based on the issue described, it appears that the "Trusted Launch" WVDs are experiencing DNS resolution problems. Here are a few steps to troubleshoot and resolve the issue:

    • Ensure the "Trusted Launch" WVDs have the correct DNS server addresses configured. You can check this by running ipconfig /all on the affected WVDs. Make sure the DNS servers are reachable and can resolve internal domain names.
    • Run ipconfig /registerdns on the "Trusted Launch" WVDs to force them to register their FQDN with the DNS server.
    • Review the NSG rules associated with the WVD subnet to ensure that DNS traffic (UDP/TCP on port 53) is allowed both ways.
    • Verify that the "Trusted Launch" and "Non Trusted Launch" WVDs have the same network and DNS configurations. This includes checking that they are part of the same virtual network and subnet.
    • Make sure that the WVD session host agents are running and properly registered with the AVD infrastructure.

    If you have any further queries, do let us know. If the comment is helpful, please click "Upvote".

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.