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/create-host-pools-azure-marketplace.md
+76-58Lines changed: 76 additions & 58 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,22 +6,30 @@ author: Heidilohr
6
6
7
7
ms.service: virtual-desktop
8
8
ms.topic: tutorial
9
-
ms.date: 08/30/2019
9
+
ms.date: 03/09/2020
10
10
ms.author: helohr
11
11
---
12
12
# Tutorial: Create a host pool by using the Azure Marketplace
13
13
14
+
In this tutorial, you'll learn how to create a host pool within a Windows Virtual Desktop tenant by using a Microsoft Azure Marketplace offering.
15
+
14
16
Host pools are a collection of one or more identical virtual machines within Windows Virtual Desktop tenant environments. Each host pool can contain an app group that users can interact with as they would on a physical desktop.
15
17
16
-
This tutorial describes how to create a host pool within a Windows Virtual Desktop tenant by using a Microsoft Azure Marketplace offering. The tasks include:
18
+
The tasks in this tutorial include:
17
19
18
20
> [!div class="checklist"]
21
+
>
19
22
> * Create a host pool in Windows Virtual Desktop.
20
23
> * Create a resource group with VMs in an Azure subscription.
21
24
> * Join the VMs to the Active Directory domain.
22
25
> * Register the VMs with Windows Virtual Desktop.
23
26
24
-
Before you begin, [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:
27
+
## Prerequisites
28
+
29
+
* A tenant in Virtual Desktop. A previous [tutorial](tenant-setup-azure-active-directory.md) creates a tenant.
@@ -36,103 +44,113 @@ Sign in to the [Azure portal](https://portal.azure.com).
36
44
To run the Azure Marketplace offering to provision a new host pool:
37
45
38
46
1. On the Azure portal menu or from the **Home** page, select **Create a resource**.
39
-
2. Enter **Windows Virtual Desktop** in the Marketplace search window.
40
-
3. Select **Windows Virtual Desktop - Provision a host pool**, and then select **Create**.
47
+
1. Enter **Windows Virtual Desktop** in the Marketplace search window.
48
+
1. Select **Windows Virtual Desktop - Provision a host pool**, and then select **Create**.
41
49
42
-
After that, follow the instructions in the next section to enter the information for the appropriate blades.
50
+
After that, follow the instructions in the next section to enter the information for the appropriate tabs.
43
51
44
52
### Basics
45
53
46
-
Here's what you do for the **Basics**blade:
54
+
Here's what you do for the **Basics**tab:
47
55
48
-
1. Enter a name for the host pool that’s unique within the Windows Virtual Desktop tenant.
49
-
2. Select the appropriate option for a personal desktop. If you select **Yes**, each user that connects to this host pool will be permanently assigned to a virtual machine.
50
-
3. Enter a comma-separated list of users who can sign in to the Windows Virtual Desktop clients and access a desktop after the Azure Marketplace offering finishes. For example, if you want to assign [email protected] and [email protected] access, enter "[email protected],[email protected]."
51
-
4. Select **Create new** and provide a name for the new resource group.
52
-
5. For **Location**, select the same location as the virtual network that has connectivity to the Active Directory server.
1. For **Service metadata location**, select the same location as the virtual network that has connectivity to the Active Directory server.
54
63
55
-
>[!IMPORTANT]
56
-
>If you're using a pure Azure Active Directory Domain Services and Azure Active Directory solution, make sure to deploy your host pool in the same region as your Azure Active Directory Domain Services to avoid domain-join and credential errors.
64
+
>[!IMPORTANT]
65
+
>If you're using a pure Azure Active Directory Domain Services (Azure AD DS) and Azure Active Directory (Azure AD) solution, make sure to deploy your host pool in the same region as your Azure AD DS to avoid domain-join and credential errors.
66
+
67
+
1. Select **Next: Configure virtual machines**.
57
68
58
69
### Configure virtual machines
59
70
60
-
For the **Configure virtual machines** blade:
71
+
For the **Configure virtual machines** tab:
72
+
73
+
1. Either accept the defaults or customize the number and size of the virtual machines.
61
74
62
-
1. Either accept the defaults or customize the number and size of the VMs.
63
-
64
75
>[!NOTE]
65
-
>If the specific VM size you're looking for doesn't appear in the VM size selector, that's because we haven't onboarded it to the Azure Marketplace tool yet. To request a VM size, create a request or upvote an existing request in the [Windows Virtual Desktop UserVoice forum](https://windowsvirtualdesktop.uservoice.com/forums/921118-general).
66
-
67
-
2. Enter a prefix for the names of the virtual machines. For example, if you enter the name "prefix," the virtual machines will be called "prefix-0," "prefix-1," and so on.
68
-
3. Select **Next: Virtual machine settings**.
76
+
>If the specific virtual machine size you're looking for doesn't appear in the size selector, that's because we haven't onboarded it to the Azure Marketplace tool yet. To request a size, create a request or upvote an existing request in the [Windows Virtual Desktop UserVoice forum](https://windowsvirtualdesktop.uservoice.com/forums/921118-general).
77
+
78
+
1. Enter a prefix for the names of the virtual machines. For example, if you enter *prefix*, the virtual machines will be called **prefix-0**, **prefix-1**, and so on.
79
+
1. Select **Next: Virtual machine settings**.
69
80
70
81
### Virtual machine settings
71
82
72
-
For the **Virtual machine settings**blade:
83
+
For the **Virtual machine settings**tab:
73
84
74
-
>[!NOTE]
75
-
> If you're joining your VMs to an Azure Active Directory Domain Services (Azure AD DS) environment, ensure that your domain join user is a member of the [AAD DC Administrators group](../active-directory-domain-services/tutorial-create-instance-advanced.md#configure-an-administrative-group).
76
-
>
77
-
> The account must also be part of the Azure AD DS managed domain or Azure AD tenant - accounts from external directories associated with your Azure AD tenant can't correctly authenticate during the domain-join process.
85
+
1. For **Image source**, select the source and enter the appropriate information for how to find it and how to store it. Your options differ for Blob storage, Managed image, and Gallery.
78
86
79
-
1. For **Image source**, select the source and enter the appropriate information for how to find it and how to store it. If you choose not to use managed disks, select the storage account that contains the .vhd file.
80
-
2. Enter the user principal name and password for the domain account that will join the VMs to the Active Directory domain. This same username and password will be created on the virtual machines as a local account. You can reset these local accounts later.
81
-
3. Select the virtual network that has connectivity to the Active Directory server, and then choose a subnet to host the virtual machines.
82
-
4. Select **Next: Windows Virtual Desktop information**.
87
+
If you choose not to use managed disks, select the storage account that contains the *.vhd* file.
88
+
1. Enter the user principal name and password. This account must be the domain account that will join the virtual machines to the Active Directory domain. This same username and password will be created on the virtual machines as a local account. You can reset these local accounts later.
89
+
90
+
>[!NOTE]
91
+
> If you're joining your virtual machines to an Azure AD DS environment, ensure that your domain join user is a member of the [AAD DC Administrators group](../active-directory-domain-services/tutorial-create-instance-advanced.md#configure-an-administrative-group).
92
+
>
93
+
> The account must also be part of the Azure AD DS managed domain or Azure AD tenant. Accounts from external directories associated with your Azure AD tenant can't correctly authenticate during the domain-join process.
94
+
95
+
1. Select the **Virtual network** that has connectivity to the Active Directory server, and then choose a subnet to host the virtual machines.
96
+
1. Select **Next: Windows Virtual Desktop information**.
83
97
84
98
### Windows Virtual Desktop tenant information
85
99
86
-
For the **Windows Virtual Desktop tenant information**blade:
100
+
For the **Windows Virtual Desktop tenant information**tab:
87
101
88
102
1. For **Windows Virtual Desktop tenant group name**, enter the name for the tenant group that contains your tenant. Leave it as the default unless you were provided a specific tenant group name.
89
-
2. For **Windows Virtual Desktop tenant name**, enter the name of the tenant where you'll be creating this host pool.
90
-
3. Specify the type of credentials that you want to use to authenticate as the Windows Virtual Desktop tenant RDS Owner. If you completed the [Create service principals and role assignments with PowerShell tutorial](./create-service-principal-role-powershell.md), select **Service principal**. When **Azure AD tenant ID** appears, enter the ID for the Azure Active Directory instance that contains the service principal.
91
-
4. Enter the credentials for the tenant admin account. Only service principals with a password credential are supported.
92
-
5. Select **Next : Review + create**.
103
+
1. For **Windows Virtual Desktop tenant name**, enter the name of the tenant where you'll be creating this host pool.
104
+
1. Specify the type of credentials that you want to use to authenticate as the Windows Virtual Desktop tenant RDS Owner. Enter the UPN or Service principal and a password.
105
+
106
+
If you completed the [Create service principals and role assignments with PowerShell tutorial](./create-service-principal-role-powershell.md), select **Service principal**.
107
+
108
+
1. For **Service principal**, for **Azure AD tenant ID**, enter the tenant admin account for the Azure AD instance that contains the service principal. Only service principals with a password credential are supported.
109
+
1. Select **Next: Review + create**.
93
110
94
111
## Complete setup and create the virtual machine
95
112
96
-
For the last two blades:
113
+
In **Review and Create**, review the setup information. If you need to change something, go back and make changes. When you're ready, select **Create** to deploy your host pool.
97
114
98
-
1. On the **Review and Create** blade, review the setup information. If you need to change something, go back to the appropriate blade and make your change before continuing. If the information looks right, select **OK**.
99
-
2. Select **Create** to deploy your host pool.
115
+
Depending on how many virtual machines you're creating, this process can take 30 minutes or more to complete.
100
116
101
-
Depending on how many VMs you’re creating, this process can take 30 minutes or more to complete.
117
+
>[!IMPORTANT]
118
+
> To help secure your Windows Virtual Desktop environment in Azure, we recommend you don't open inbound port 3389 on your virtual machines. Windows Virtual Desktop doesn't require an open inbound port 3389 for users to access the host pool's virtual machines.
119
+
>
120
+
> If you must open port 3389 for troubleshooting purposes, we recommend you use just-in-time access. For more information, see [Secure your management ports with just-in-time access](../security-center/security-center-just-in-time.md).
102
121
103
122
## (Optional) Assign additional users to the desktop application group
104
123
105
-
After the Azure Marketplace offering finishes, you can assign more users to the desktop application group before you start testing the full session desktops on your virtual machines. If you've already added default users in the Azure Marketplace offering and don't want to add more, you can skip this section.
124
+
After Azure Marketplace finishes creating the pool, you can assign more users to the desktop application group. If youdon't want to add more, skip this section.
106
125
107
-
To assign users to the desktop application group, you must first open a PowerShell window. After that, you'll need to enter the following two cmdlets.
126
+
To assign users to the desktop application group:
108
127
109
-
Run the following cmdlet to sign in to the Windows Virtual Desktop environment:
1. Add users to the desktop application group by using this command:
120
137
121
-
The user’s UPN should match the user’s identity in Azure Active Directory (for example, [email protected]). If you want to add multiple users, you must run this cmdlet for each user.
After you've completed these steps, users added to the desktop application group can sign in to Windows Virtual Desktop with supported Remote Desktop clients and see a resource for a session desktop.
142
+
The user's UPN should match the user's identity in Azure AD, for example, *[email protected]*. If you want to add multiple users, run the command for each user.
124
143
125
-
Here are the current supported clients:
144
+
Users you add to the desktop application group can sign in to Windows Virtual Desktop with supported Remote Desktop clients and see a resource for a session desktop.
126
145
127
-
-[Remote Desktop client for Windows 7 and Windows 10](connect-windows-7-and-10.md)
128
-
-[Windows Virtual Desktop web client](connect-web.md)
146
+
Here are the current supported clients:
129
147
130
-
>[!IMPORTANT]
131
-
>To help secure your Windows Virtual Desktop environment in Azure, we recommend you don't open inbound port 3389 on your VMs. Windows Virtual Desktop doesn't require an open inbound port 3389 for users to access the host pool's VMs. If you must open port 3389 for troubleshooting purposes, we recommend you use [just-in-time VM access](../security-center/security-center-just-in-time.md).
148
+
*[Remote Desktop client for Windows 7 and Windows 10](connect-windows-7-and-10.md)
149
+
*[Windows Virtual Desktop web client](connect-web.md)
132
150
133
151
## Next steps
134
152
135
-
Now that you've made a host pool and assigned users to access its desktop, you can populate your host pool with RemoteApp programs. To learn more about how to manage apps in Windows Virtual Desktop, see this tutorial:
153
+
You've made a host pool and assigned users to access its desktop. You can populate your host pool with RemoteApp programs. To learn more about how to manage apps in Windows Virtual Desktop, see this tutorial:
136
154
137
155
> [!div class="nextstepaction"]
138
156
> [Manage app groups tutorial](./manage-app-groups.md)
0 commit comments