Windows Virtual Desktop Agent
Agile working has become an important hurdle to jump in forwarding your corporate development.Windows Virtual Desktop can help you do this. Show
The COVID-19 pandemic has highlighted the need of companies to empower workers with fast, flexible and simple remote working capacibilities, without compromising compatibility, performance, security or simultaneous access to shared resources. Window Virtual Desktop (WVD) can help you bring your company's IT infrastructure up to scratch - with state-of-the-art Window 10 combined with the dynamic scalability of the Microsoft Cloud, providing an unmatched, cost efficient pricing model. Troubleshoot Azure Virtual Desktop Agent Issues - Azure How to resolve common agent and connectivity issues. The Azure Virtual Desktop Agent can cause connection issues because of multiple factors: This article will guide you through solutions to these common scenarios and how to address connection issues. [!NOTE]
For troubleshooting issues related to session connectivity and the Azure Virtual Desktop agent, we recommend you review the event logs in Event Viewer > Windows Logs > Application. Look for events that have one of the following sources to identify your issue: If you're seeing any of the following issues, this means that the boot loader, which loads the agent, was unable to install the agent properly and the agent service isn't running: To resolve this issue, start the RDAgent boot loader: Go to Event Viewer > Windows Logs > Application. If you see an event with ID 3277, that says INVALID_REGISTRATION_TOKEN in the description, the registration token that you have isn't recognized as valid. To resolve this issue, create a valid registration token: To create a new registration token, follow the steps in the Generate a new registration key for the VM section. Open the Registry Editor. Go to HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > RDInfraAgent. Select IsRegistered. In the Value data: entry box, type 0 and select Ok. Select RegistrationToken. In the Value data: entry box, paste the registration token from step 1. [!div class="mx-imgBorder"]
Open a command prompt as an administrator. Enter net stop RDAgentBootLoader. Enter net start RDAgentBootLoader. Open the Registry Editor. Go to HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > RDInfraAgent. Verify that IsRegistered is set to 1 and there is nothing in the data column for RegistrationToken.
Error: Agent cannot connect to broker with INVALID_FORMGo to Event Viewer > Windows Logs > Application. If you see an event with ID 3277 that says "INVALID_FORM" in the description, something went wrong with the communication between the agent and the broker. The agent can't connect to the broker or reach a particular URL because of certain firewall or DNS settings. To resolve this issue, check that you can reach BrokerURI and BrokerURIGlobal:
Error: 3703Go to Event Viewer > Windows Logs > Application. If you see an event with ID 3703 that says "RD Gateway Url: is not accessible" in the description, the agent is unable to reach the gateway URLs. To successfully connect to your session host and allow network traffic to these endpoints to bypass restrictions, you must unblock the URLs from the Required URL List. Also, make sure your firewall or proxy settings don't block these URLs. Unblocking these URLs is required to use Azure Virtual Desktop. To resolve this issue, verify that your firewall and/or DNS settings are not blocking these URLs: Error: 3019Go to Event Viewer > Windows Logs > Application. If you see an event with ID 3019, this means the agent can't reach the web socket transport URLs. To successfully connect to your session host and allow network traffic to bypass these restrictions, you must unblock the URLs listed in the the Required URL list. Work with the Azure Networking team to make sure your firewall, proxy, and DNS settings aren't blocking these URLs. You can also check your network trace logs to identify where the Azure Virtual Desktop service is being blocked. If you open a support request for this particular issue, make sure to attach your network trace logs to the request. Error: InstallationHealthCheckFailedExceptionGo to Event Viewer > Windows Logs > Application. If you see an event with ID 3277 that says "InstallationHealthCheckFailedException" in the description, that means the stack listener isn't working because the terminal server has toggled the registry key for the stack listener. To resolve this issue: Error: ENDPOINT_NOT_FOUNDGo to Event Viewer > Windows Logs > Application. If you see an event with ID 3277 that says "ENDPOINT_NOT_FOUND" in the description that means the broker couldn't find an endpoint to establish a connection with. This connection issue can happen for one of the following reasons:
To resolve this issue: Error: InstallMsiExceptionGo to Event Viewer > Windows Logs > Application. If you see an event with ID 3277, that says InstallMsiException in the description, the installer is already running for another application while you're trying to install the agent, or a policy is blocking the msiexec.exe program from running. To resolve this issue, disable the following policy:
To disable a policy:
Error: Win32ExceptionGo to Event Viewer > Windows Logs > Application. If you see an event with ID 3277, that says InstallMsiException in the description, a policy is blocking cmd.exe from launching. Blocking this program prevents you from running the console window, which is what you need to use to restart the service whenever the agent updates. To resolve this issue, disable the following policy:
To disable a policy:
Error: Stack listener isn't working on Windows 10 2004 VMRun qwinsta in your command prompt and make note of the version number that appears next to rdp-sxs. If you're not seeing the rdp-tcp and rdp-sxs components say Listen next to them or they aren't showing up at all after running qwinsta, it means that there's a stack issue. Stack updates get installed along with agent updates, and when this installation goes awry, the Azure Virtual Desktop Listener won't work. To resolve this issue:
Error: DownloadMsiExceptionGo to Event Viewer > Windows Logs > Application. If you see an event with ID 3277, that says DownloadMsiException in the description, there isn't enough space on the disk for the RDAgent. To resolve this issue, make space on your disk by:
Error: Agent fails to update with MissingMethodExceptionGo to Event Viewer > Windows Logs > Application. If you see an event with ID 3389 that says "MissingMethodException: Method not found" in the description, that means the Azure Virtual Desktop agent didn't update successfully and reverted to an earlier version. This may be because the version number of the .NET framework currently installed on your VMs is lower than 4.7.2. To resolve this issue, you need to upgrade the .NET to version 4.7.2 or later by following the installation instructions in the .NET Framework documentation. Error: VMs are stuck in Unavailable or Upgrading stateOpen a PowerShell window as an administrator and run the following cmdlet: Get-AzWvdSessionHost -ResourceGroupName <resourcegroupname> -HostPoolName <hostpoolname> | Select-Object * If the status listed for the session host or hosts in your host pool always says "Unavailable" or "Upgrading," the agent or stack didn't install successfully. To resolve this issue, reinstall the side-by-side stack:
Error: Connection not found: RDAgent does not have an active connection to the brokerYour VMs may be at their connection limit, so the VM can't accept new connections. To resolve this issue:
Error: Operating a Pro VM or other unsupported OSThe side-by-side stack is only supported by Windows Enterprise or Windows Server SKUs, which means that operating systems like Pro VM aren't. If you don't have an Enterprise or Server SKU, the stack will be installed on your VM but won't be activated, so you won't see it show up when you run qwinsta in your command line. To resolve this issue, create a VM that is Windows Enterprise or Windows Server.
Error: NAME_ALREADY_REGISTEREDThe name of your VM has already been registered and is probably a duplicate. To resolve this issue:
Your issue isn't listed here or wasn't resolvedIf you can't find your issue in this article or the instructions didn't help you, we recommend you uninstall, reinstall, and re-register Azure Virtual Desktop Agent. The instructions in this section will show you how to reregister your VM to the Azure Virtual Desktop service by uninstalling all agent, boot loader, and stack components, removing the session host from the host pool, generating a new registration key for the VM, and reinstalling the agent and boot loader. If one or more of the following scenarios apply to you, follow these instructions:
Step 1: Uninstall all agent, boot loader, and stack component programsBefore reinstalling the agent, boot loader, and stack, you must uninstall any existing component programs from your VM. To uninstall all agent, boot loader, and stack component programs:
Step 2: Remove the session host from the host poolWhen you remove the session host from the host pool, the session host is no longer registered to that host pool. This acts as a reset for the session host registration. To remove the session host from the host pool:
Step 3: Generate a new registration key for the VMYou must generate a new registration key that is used to re-register your VM to the host pool and to the service. To generate a new registration key for the VM:
Step 4: Reinstall the agent and boot loaderBy reinstalling the most updated version of the agent and boot loader, the side-by-side stack and Geneva monitoring agent automatically get installed as well. To reinstall the agent and boot loader:
Next stepsIf the issue continues, create a support case and include detailed information about the problem you're having and any actions you've taken to try to resolve it. The following list includes other resources you can use to troubleshoot issues in your Azure Virtual Desktop deployment.
Page 2
You can’t perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. |