Skip to content

Commit 4c478c9

Browse files
Merge pull request #237086 from dknappettmsft/avd-agent-notes
AVD agent notes
2 parents 7ff43b6 + bdbb31e commit 4c478c9

File tree

3 files changed

+17
-3
lines changed

3 files changed

+17
-3
lines changed

articles/virtual-desktop/add-session-hosts-host-pool.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -202,9 +202,11 @@ Select the relevant tab for your scenario and follow the steps.
202202
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**.
203203

204204
- [Azure Virtual Desktop Agent](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RWrmXv)
205-
206205
- [Azure Virtual Desktop Agent Bootloader](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RWrxrH)
207206

207+
> [!TIP]
208+
> This is the latest downloadable version of the Azure Virtual Desktop Agent in [non-validation environments](terminology.md#validation-environment). For more information about the rollout of new versions of the agent, see [What's new in the Azure Virtual Desktop Agent](whats-new-agent.md#latest-agent-versions).
209+
208210
1. Run the `Microsoft.RDInfra.RDAgent.Installer-x64-<version>.msi` file to install the Remote Desktop Services Infrastructure Agent.
209211

210212
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.
@@ -256,6 +258,9 @@ Using `msiexec` enables you to install the agent and boot loader from the comman
256258
}
257259
```
258260

261+
> [!TIP]
262+
> This is the latest downloadable version of the Azure Virtual Desktop Agent in [non-validation environments](terminology.md#validation-environment). For more information about the rollout of new versions of the agent, see [What's new in the Azure Virtual Desktop Agent](whats-new-agent.md#latest-agent-versions).
263+
259264
1. To install the Remote Desktop Services Infrastructure Agent, run the following command as an administrator:
260265

261266
```powershell

articles/virtual-desktop/terminology.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,13 +34,20 @@ The following table goes into more detail about the differences between each typ
3434
|Windows Updates|Updated with Windows Updates, [System Center Configuration Manager (SCCM)](configure-automatic-updates.md), or other software distribution configuration tools.|Updated by redeploying session hosts from updated images instead of traditional updates.|
3535
|User data| Each user only ever uses one session host, so they can store their user profile data on the operating system (OS) disk of the VM. | Users can connect to different session hosts every time they connect, so they should store their user profile data in [FSLogix](/fslogix/configure-profile-container-tutorial). |
3636

37+
### Validation environment
38+
39+
You can set a host pool to be a *validation environment*. Validation environments let you monitor service updates before the service applies them to your production or non-validation environment. Without a validation environment, you may not discover changes that introduce errors, which could result in downtime for users in your production environment.
40+
41+
To ensure your apps work with the latest updates, the validation environment should be as similar to host pools in your non-validation environment as possible. Users should connect as frequently to the validation environment as they do to the production environment. If you have automated testing on your host pool, you should include automated testing on the validation environment.
42+
3743
## Application groups
3844

3945
An application group is a logical grouping of applications installed on session hosts in the host pool.
4046

4147
An application group can be one of two types:
4248

4349
- RemoteApp, where users access the RemoteApps you individually select and publish to the application group. Available with pooled host pools only.
50+
4451
- Desktop, where users access the full desktop. Available with pooled or personal host pools.
4552

4653
Pooled host pools have a preferred application group type that dictates whether users see RemoteApp or Desktop apps in their feed if both resources have been published to the same user. By default, Azure Virtual Desktop automatically creates a Desktop application group with the friendly name **Default Desktop** whenever you create a host pool and sets the host pool's preferred application group type to **Desktop**. You can remove the Desktop application group at any time. If you want your users to only see RemoteApps in their feed, you should set the **preferred application group type** value to **RemoteApp**. If you want your users to only see session desktops in their feed, you should set the **preferred application group type** value to **Desktop**. You can't create another Desktop application group in a host pool while a Desktop application group exists.

articles/virtual-desktop/whats-new-agent.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: What's new in the Azure Virtual Desktop Agent? - Azure
33
description: New features and product updates for the Azure Virtual Desktop Agent.
44
author: Heidilohr
55
ms.topic: release-notes
6-
ms.date: 04/11/2023
6+
ms.date: 05/09/2023
77
ms.author: helohr
88
manager: femila
99
ms.custom: references_regions
@@ -21,7 +21,9 @@ Make sure to check back here often to keep up with new updates.
2121

2222
## Latest agent versions
2323

24-
New versions of the Azure Virtual Desktop Agent are installed automatically. When new versions are released, they are rolled out progressively to all session hosts. This process is called *flighting* and it enables Microsoft to monitor the rollout in [validation environments](create-validation-host-pool.md) first. A rollout may take several weeks before the agent is available in all environments.
24+
New versions of the Azure Virtual Desktop Agent are installed automatically. When new versions are released, they're rolled out progressively to session hosts. This process is called *flighting* and it enables Microsoft to monitor the rollout in [validation environments](create-validation-host-pool.md) first.
25+
26+
A rollout may take several weeks before the agent is available in all environments. Some agent versions may not reach non-validation environments, so you may see multiple versions of the agent deployed across your environments.
2527

2628
## Version 1.0.6425.300
2729

0 commit comments

Comments
 (0)