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/configure-host-pool-load-balancing.md
+38-7Lines changed: 38 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,34 +17,65 @@ Configuring the load-balancing method for a host pool allows you to adjust the W
17
17
>[!NOTE]
18
18
> This does not apply to a persistent desktop host pool because users always have a 1:1 mapping to a session host within the host pool.
19
19
20
+
## Prerequisites
21
+
22
+
This article assumes you've followed the instructions in [Set up the Windows Virtual Desktop PowerShell module](powershell-module.md) to download and install the PowerShell module and sign in to your Azure account.
23
+
20
24
## Configure breadth-first load balancing
21
25
22
26
Breadth-first load balancing is the default configuration for new non-persistent host pools. Breadth-first load balancing distributes new user sessions across all available session hosts in the host pool. When configuring breadth-first load balancing, you may set a maximum session limit per session host in the host pool.
23
27
24
-
First, [download and import the Windows Virtual Desktop PowerShell module](/powershell/windows-virtual-desktop/overview/) to use in your PowerShell session if you haven't already. After that, run the following cmdlet to sign in to your account:
28
+
To configure a host pool to perform breadth-first load balancing without adjusting the maximum session limit, run the following PowerShell cmdlet:
Depth-first load balancing distributes new user sessions to an available session host with the highest number of connections but has not reached its maximum session limit threshold. When configuring depth-first load balancing, you **must** set a maximum session limit per session host in the host pool.
51
+
Depth-first load balancing distributes new user sessions to an available session host with the highest number of connections but has not reached its maximum session limit threshold. When configuring depth-first load balancing, you must set a maximum session limit per session host in the host pool.
45
52
46
53
To configure a host pool to perform depth-first load balancing, run the following PowerShell cmdlet:
Copy file name to clipboardExpand all lines: articles/virtual-desktop/configure-host-pool-personal-desktop-assignment-type.md
+13-17Lines changed: 13 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: HeidiLohr
6
6
7
7
ms.service: virtual-desktop
8
8
ms.topic: conceptual
9
-
ms.date: 12/10/2019
9
+
ms.date: 04/30/2020
10
10
ms.author: helohr
11
11
manager: lizross
12
12
---
@@ -23,33 +23,26 @@ You can configure the assignment type of your personal desktop host pool to adju
23
23
>[!NOTE]
24
24
> The instructions in this article only apply to personal desktop host pools, not pooled host pools, since users in pooled host pools aren't assigned to specific session hosts.
25
25
26
+
## Prerequisites
27
+
28
+
This article assumes you've already downloaded and installed the Windows Virtual Desktop PowerShell module. If you haven't, follow the instructions in [Set up the PowerShell module](powershell-module.md).
29
+
26
30
## Configure automatic assignment
27
31
28
32
Automatic assignment is the default assignment type for new personal desktop host pools created in your Windows Virtual Desktop environment. Automatically assigning users doesn't require a specific session host.
29
33
30
34
To automatically assign users, first assign them to the personal desktop host pool so that they can see the desktop in their feed. When an assigned user launches the desktop in their feed, they will claim an available session host if they have not already connected to the host pool, which completes the assignment process.
31
35
32
-
Before you start, [download and import the Windows Virtual Desktop PowerShell module](/powershell/windows-virtual-desktop/overview/) if you haven't already.
33
-
34
-
> [!NOTE]
35
-
> Make sure you've installed Windows Virtual Desktop PowerShell module version 1.0.1534.2001 or later before following these instructions.
36
-
37
-
After that, run the following cmdlet to sign in to your account:
Copy file name to clipboardExpand all lines: articles/virtual-desktop/configure-vm-gpu.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Azure offers a number of [GPU optimized virtual machine sizes](/azure/virtual-ma
28
28
29
29
## Create a host pool, provision your virtual machine, and configure an app group
30
30
31
-
Create a new host pool using a VM of the size you selected. For instructions, see [Tutorial: Create a host pool with Azure Marketplace](/azure/virtual-desktop/create-host-pools-azure-marketplace).
31
+
Create a new host pool using a VM of the size you selected. For instructions, see [Tutorial: Create a host pool with the Azure portal](/azure/virtual-desktop/create-host-pools-azure-marketplace).
32
32
33
33
Windows Virtual Desktop supports GPU-accelerated rendering and encoding in the following operating systems:
Copy file name to clipboardExpand all lines: articles/virtual-desktop/create-validation-host-pool.md
+15-17Lines changed: 15 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,54 +27,52 @@ You can debug issues in the validation host pool with either [the diagnostics fe
27
27
>[!NOTE]
28
28
> We recommend that you leave the validation host pool in place to test all future updates.
29
29
30
-
Before you begin, [download and import the Windows Virtual Desktop PowerShell module](/powershell/windows-virtual-desktop/overview/), if you haven't already. After that, run the following cmdlet to sign in to your account:
30
+
>[!IMPORTANT]
31
+
>The Windows Virtual Desktop Spring 2020 release currently has trouble enabling and disabling validation environment. We'll update this article when we've resolved the issue.
Before you begin, follow the instructions in [Set up the Windows Virtual Desktop PowerShell module](powershell-module.md) to set up your PowerShell module and sign in to Azure.
35
36
36
37
## Create your host pool
37
38
38
39
You can create a host pool by following the instructions in any of these articles:
39
40
-[Tutorial: Create a host pool with Azure Marketplace](create-host-pools-azure-marketplace.md)
40
-
-[Create a host pool with an Azure Resource Manager template](./virtual-desktop-fall-2019/create-host-pools-arm-template.md)
41
41
-[Create a host pool with PowerShell](create-host-pools-powershell.md)
42
42
43
43
## Define your host pool as a validation host pool
44
44
45
-
Run the following PowerShell cmdlets to define the new host pool as a validation host pool. Replace the values in quotes by the values relevant to your session:
45
+
Run the following PowerShell cmdlets to define the new host pool as a validation host pool. Replace the values in brackets with the values relevant to your session:
Run the following PowerShell cmdlet to confirm that the validation property has been set. Replace the values in quotes by the values relevant to your session.
51
+
Run the following PowerShell cmdlet to confirm that the validation property has been set. Replace the values in brackets with the values relevant to your session.
The results from the cmdlet should look similar to this output:
59
58
60
-
```
61
-
TenantName : contoso
62
-
TenantGroupName : Default Tenant Group
63
-
HostPoolName : contosoHostPool
59
+
```powershell
60
+
HostPoolName : hostpoolname
64
61
FriendlyName :
65
62
Description :
66
63
Persistent : False
67
-
CustomRdpProperty : use multimon:i:0;
64
+
CustomRdpProperty : use multimon:i:0;
68
65
MaxSessionLimit : 10
69
66
LoadBalancerType : BreadthFirst
70
-
ValidationEnv : True
71
-
Ring :
67
+
ValidationEnvironment : True
72
68
```
73
69
74
70
## Update schedule
75
71
76
72
Service updates happen monthly. If there are major issues, critical updates will be provided at a more frequent pace.
77
73
74
+
If there are any service updates, make sure you have at least a small group of users signing in each day to validate the environment. We recommend you regularly visit our [TechCommunity site](https://techcommunity.microsoft.com/t5/forums/searchpage/tab/message?filter=location&q=wvdupdate&location=forum-board:WindowsVirtualDesktop&sort_by=-topicPostDate&collapse_discussion=true) and follow any posts with WVDUPdate to stay informed about service updates.
75
+
78
76
## Next steps
79
77
80
78
Now that you've created a validation host pool, you can learn how to use Azure Service Health to monitor your Windows Virtual Desktop deployment.
Copy file name to clipboardExpand all lines: articles/virtual-desktop/customize-feed-for-virtual-desktop-users.md
+71-15Lines changed: 71 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,11 +20,9 @@ manager: lizross
20
20
21
21
You can customize the feed so the RemoteApp and remote desktop resources appear in a recognizable way for your users.
22
22
23
-
First, [download and import the Windows Virtual Desktop PowerShell module](/powershell/windows-virtual-desktop/overview/) to use in your PowerShell session if you haven't already. After that, run the following cmdlet to sign in to your account:
This article assumes you've already downloaded and installed the Windows Virtual Desktop PowerShell module. If you haven't, follow the instructions in [Set up the PowerShell module](powershell-module.md).
28
26
29
27
## Customize the display name for a RemoteApp
30
28
@@ -33,16 +31,55 @@ You can change the display name for a published RemoteApp by setting the friendl
33
31
To retrieve a list of published RemoteApps for an app group, run the following PowerShell cmdlet:

99
+
100
+
## Customize a display name in Azure portal
101
+
102
+
You can change the display name for a published remote desktop by setting a friendly name using the Azure portal.
103
+
104
+
1. Sign in to the Azure portal at <https://portal.azure.com>.
105
+
106
+
2. Search for **Windows Virtual Desktop**.
107
+
108
+
3. Under Services, select **Windows Virtual Desktop**.
109
+
110
+
4. On the Windows Virtual Desktop page, select **Application groups** on the left side of the screen, then select the name of the app group you want to edit.
111
+
112
+
5. Select **Applications** in the menu on the left side of the screen.
113
+
114
+
6. Select the application you want to update, then enter a new **Display name**.
115
+
116
+
7. Select **Save**. The application you edited should now display the updated name.
64
117
65
118
## Next steps
66
119
67
120
Now that you've customized the feed for users, you can sign in to a Windows Virtual Desktop client to test it out. To do so, continue to the Connect to Windows Virtual Desktop How-tos:
68
121
69
-
*[Connect from Windows 10 or Windows 7](connect-windows-7-and-10.md)
70
-
*[Connect from a web browser](connect-web.md)
122
+
*[Connect with Windows 10 or Windows 7](connect-windows-7-and-10.md)
123
+
*[Connect with the web client](connect-web.md)
124
+
*[Connect with the Android client](connect-android.md)
125
+
*[Connect with the iOS client](connect-ios.md)
126
+
*[Connect with the macOS client](connect-macos.md)
0 commit comments