In the Value data: entry box, paste the registration token from step 1. In the Value data: entry box, type 0 and select Ok. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RDInfraAgent. To create a new registration token, follow the steps in the Generate a new registration key for the VM section. To resolve this issue, create a valid registration token: If you see an event with ID 3277 with INVALID_REGISTRATION_TOKEN in the description, the registration token that has been used isn't recognized as valid. On your session host VM, go to Event Viewer > Windows Logs > Application. For more information, see INVALID_REGISTRATION_TOKEN. If the service stops after you started and refreshed it, you may have a registration failure.Wait 10 seconds, then right-click Remote Desktop Agent Loader.If this option is greyed out for you, you don't have administrator permissions and will need to get them to start the service.
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 on your session host VM: Look for events that have one of the following sources to identify your issue:Įrror: The RDAgentBootLoader and/or Remote Desktop Agent Loader has stopped running For troubleshooting issues related to session connectivity and the Azure Virtual Desktop agent, we recommend you review the event logs on your session host virtual machines (VMs) by going to Event Viewer > Windows Logs > Application.
0 kommentar(er)
