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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-desktop/add-session-hosts-host-pool.md
+31-1Lines changed: 31 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -182,7 +182,7 @@ Here's how to create session hosts and register them to a host pool using the Az
182
182
183
183
## Register session hosts to a host pool
184
184
185
-
If you created virtual machines using an alternative method outside of Azure Virtual Desktop, such as an automated pipeline, you'll need to register them separately as session hosts to a host pool. To register session hosts to a host pool, you need to install what is referred to as the Azure Virtual Desktop agent on each virtual machine and use the registration key you generated. You can register session hosts to a host pool using the agent installers' graphical user interface (GUI) or using `msiexec` from a command line. Once complete, four applications will be listed as installed applications:
185
+
If you created virtual machines using an alternative method outside of Azure Virtual Desktop, such as an automated pipeline, you'll need to register them separately as session hosts to a host pool. To register session hosts to a host pool, you need to install the Azure Virtual Desktop Agent and the Azure Virtual Desktop Agent Bootloader on each virtual machine and use the registration key you generated. You can register session hosts to a host pool using the agent installers' graphical user interface (GUI) or using `msiexec` from a command line. Once complete, four applications will be listed as installed applications:
186
186
187
187
- Remote Desktop Agent Boot Loader.
188
188
- Remote Desktop Services Infrastructure Agent.
@@ -199,6 +199,12 @@ Select the relevant tab for your scenario and follow the steps.
199
199
200
200
1. Sign in to your virtual machine as an administrator.
201
201
202
+
1. Download the Agent and the Agent Bootloader installation files using the following links You may need to unblock them; right-click each file and select **Properties**, then select **Unblock**, and finally select **OK**.
1. Run the `Microsoft.RDInfra.RDAgent.Installer-x64-<version>.msi` file to install the Remote Desktop Services Infrastructure Agent.
203
209
204
210
1. Follow the prompts and when the installer prompts for the registration token, paste it into the text box, which will appear on a single line. Select **Next**, then complete the installation.
@@ -226,6 +232,30 @@ Using `msiexec` enables you to install the agent and boot loader from the comman
Copy file name to clipboardExpand all lines: articles/virtual-desktop/troubleshoot-agent.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -349,8 +349,10 @@ You must generate a new registration key that is used to re-register your sessio
349
349
By 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:
350
350
351
351
1. Sign in to your session host VM as an administrator and run the agent installer and bootloader for your session host VM:
> For each of the the agent and boot loader installers you downloaded, you may need to unblock them. Right-click each file and select **Properties**, then select **Unblock**, and finally select **OK**.
@@ -371,7 +373,7 @@ By reinstalling the most updated version of the agent and boot loader, the side-
371
373
> [!div class="mx-imgBorder"]
372
374
> 
373
375
374
-
## Remove DisableRegistryTools
376
+
## Remove DisableRegistryTools registry key
375
377
376
378
If you've performed all four steps but the agent still doesn't work, that may be because the DisableRegistryTools registry key is enabled in one of the following locations:
0 commit comments