|
1 | 1 | ---
|
2 |
| -title: Manage app groups for Windows Virtual Desktop - Azure |
3 |
| -description: Describes how to set up Windows Virtual Desktop tenants in Azure Active Directory. |
| 2 | +title: Manage app groups for Windows Virtual Desktop portal - Azure |
| 3 | +description: How to manage Windows Virtual Desktop app groups with the Azure portal. |
4 | 4 | services: virtual-desktop
|
5 | 5 | author: Heidilohr
|
6 | 6 |
|
7 | 7 | ms.service: virtual-desktop
|
8 | 8 | ms.topic: tutorial
|
9 |
| -ms.date: 08/29/2019 |
| 9 | +ms.date: 04/30/2020 |
10 | 10 | ms.author: helohr
|
11 | 11 | manager: lizross
|
12 | 12 | ---
|
13 |
| -# Tutorial: Manage app groups for Windows Virtual Desktop |
| 13 | +# Tutorial: Manage app groups with the Azure portal |
14 | 14 |
|
15 | 15 | >[!IMPORTANT]
|
16 | 16 | >This content applies to the Spring 2020 update with Azure Resource Manager Windows Virtual Desktop objects. If you're using the Windows Virtual Desktop Fall 2019 release without Azure Resource Manager objects, see [this article](./virtual-desktop-fall-2019/manage-app-groups-2019.md).
|
17 | 17 | >
|
18 | 18 | > The Windows Virtual Desktop Spring 2020 update is currently in public preview. This preview version is provided without a service level agreement, and we don't recommend using it for production workloads. Certain features might not be supported or might have constrained capabilities.
|
19 | 19 | > For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
|
20 | 20 |
|
21 |
| -The default app group created for a new Windows Virtual Desktop host pool also publishes the full desktop. In addition, you can create one or more RemoteApp application groups for the host pool. Follow this tutorial to create a RemoteApp app group and publish individual **Start** menu apps. |
| 21 | +The default app group created for a new Windows Virtual Desktop host pool also publishes the full desktop. In addition, you can create one or more RemoteApp application groups for the host pool. Follow this tutorial to create a RemoteApp app group and publish individual Start menu apps. |
22 | 22 |
|
23 | 23 | In this tutorial, learn how to:
|
24 | 24 |
|
25 | 25 | > [!div class="checklist"]
|
26 | 26 | > * Create a RemoteApp group.
|
27 | 27 | > * Grant access to RemoteApp programs.
|
28 | 28 |
|
29 |
| -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: |
| 29 | +## Create a RemoteApp group |
30 | 30 |
|
31 |
| -```powershell |
32 |
| -Add-RdsAccount -DeploymentUrl "https://rdbroker.wvd.microsoft.com" |
33 |
| -``` |
| 31 | +If you've already created a host pool and session host VMs using the Azure |
| 32 | +portal or PowerShell, you can add virtual machines from the Azure portal with |
| 33 | +the following process: |
34 | 34 |
|
35 |
| -## Create a RemoteApp group |
| 35 | +1. Sign in to the [Azure portal](https://portal.azure.com/). |
| 36 | + |
| 37 | +2. Search for and select **Windows Virtual Desktop**. |
36 | 38 |
|
37 |
| -1. Run the following PowerShell cmdlet to create a new empty RemoteApp app group. |
| 39 | +3. Select **Application Groups** in the menu on the left side of the page, then select **+ Add**. |
38 | 40 |
|
39 |
| - ```powershell |
40 |
| - New-RdsAppGroup <tenantname> <hostpoolname> <appgroupname> -ResourceType "RemoteApp" |
41 |
| - ``` |
| 41 | +4. Select the subscription group and resource group you want to create the app group for. You can also choose to create a new resource group instead of selecting an existing one. |
42 | 42 |
|
43 |
| -2. (Optional) To verify that the app group was created, you can run the following cmdlet to see a list of all app groups for the host pool. |
| 43 | +5. Select the host pool that will be associated with the application group. |
44 | 44 |
|
45 |
| - ```powershell |
46 |
| - Get-RdsAppGroup <tenantname> <hostpoolname> |
47 |
| - ``` |
| 45 | + >[!NOTE] |
| 46 | + >You must select the host pool associated with the application group. App groups have apps or desktops that are served from a session host and session hosts are part of host pools. So, an app group needs to be associated with a host pool during creation. |
48 | 47 |
|
49 |
| -3. Run the following cmdlet to get a list of **Start** menu apps on the host pool's virtual machine image. Write down the values for **FilePath**, **IconPath**, **IconIndex**, and other important information for the application that you want to publish. |
| 48 | +  |
50 | 49 |
|
51 |
| - ```powershell |
52 |
| - Get-RdsStartMenuApp <tenantname> <hostpoolname> <appgroupname> |
53 |
| - ``` |
| 50 | +6. If you want to add virtual machines to your host pool, select **Host pools** in the menu on the left side of the screen. Next, select the name of the host pool you want to add virtual machines to. |
54 | 51 |
|
55 |
| -4. Run the following cmdlet to install the application based on `AppAlias`. `AppAlias` becomes visible when you run the output from step 3. |
| 52 | + After that, select **Application groups** from the menu on the left side of the screen, then select **+ Add**. |
| 53 | + |
| 54 | +  |
| 55 | + |
| 56 | + Finally, select the subscription group and resource group you want to create the app group in. You can choose to create a new resource group instead of selecting an existing one. |
| 57 | + |
| 58 | + >[!NOTE] |
| 59 | + >With this approach, the host pool that is related to the application group is already selected since you navigated from the host pool context. |
| 60 | +
|
| 61 | + |
| 62 | + |
| 63 | +7. Select **RemoteApp** under **Application group type** and provide a name. |
| 64 | + |
| 65 | + |
| 66 | + |
| 67 | +1. Select **Assignments**. |
| 68 | + |
| 69 | + |
| 70 | + |
| 71 | +1. To publish individual users or user groups to the app group, select **+Add Azure AD users or user groups**. |
| 72 | + |
| 73 | +2. When the Azure Active Directory user selector opens, select single or multiple users and user groups. |
| 74 | + |
| 75 | + |
| 76 | + |
| 77 | +1. Select **Select**. |
| 78 | + |
| 79 | +2. Select **Applications**, then select **+Add applications**. |
| 80 | + |
| 81 | +3. To add an application from the start menu: |
| 82 | + |
| 83 | +- For *Application source*, choose Start menu and then choose the application from the list under *Application*. |
| 84 | + |
| 85 | + |
| 86 | + |
| 87 | +- Add a *Display name*. This will be the name shown to the user on their client. |
| 88 | + |
| 89 | +- Leave the other options as is and click on **Save**. |
| 90 | + |
| 91 | +4. To add an application from specific file path: |
| 92 | + |
| 93 | +1. For *Application source*, choose File path. |
| 94 | + |
| 95 | +2. Enter the path to the application on the session host, registered with the associated host pool. |
| 96 | + |
| 97 | +3. Enter all other details of the application like *Application name, Display name, Icon path and Icon index*. |
| 98 | + |
| 99 | +4. Click on **Save**. |
| 100 | + |
| 101 | + |
| 102 | + |
| 103 | +Repeat this for every application you want added to the application group. |
| 104 | + |
| 105 | +1. Click on Workspace. As part of the application group creation wizard, you can hoose to register the app group to a workspace. |
| 106 | + |
| 107 | +2. If you want to register the app group to a workspace, choose Yes. If you want to register the app group at a later time, choose No. |
| 108 | + |
| 109 | + |
| 110 | + |
| 111 | +1. If yes, you can then create a new workspace or select from existing workspaces. Only workspaces created in the same location as the host pool will be allowed to register the app group to. Also if you have previously registered another app group (from the same host pool) to a workspace, it will be selected and you cannot edit it. All app groups from a host pool must be registered to the same workspace. |
| 112 | + |
| 113 | + |
| 114 | + |
| 115 | +Then click on **Tags**. This can be skipped and you can choose to select **Review + create.** |
| 116 | + |
| 117 | +Then select **Review + create** |
| 118 | + |
| 119 | +validate all your input. |
56 | 120 |
|
57 |
| - ```powershell |
58 |
| - New-RdsRemoteApp <tenantname> <hostpoolname> <appgroupname> -Name <remoteappname> -AppAlias <appalias> |
59 |
| - ``` |
| 121 | +Once validation is completed click **Create**. Optionally you can download the ARM template used by the wizard. |
60 | 122 |
|
61 |
| -5. (Optional) Run the following cmdlet to publish a new RemoteApp program to the application group created in step 1. |
| 123 | + When the deployment completes, these are the following will be completed: |
62 | 124 |
|
63 |
| - ```powershell |
64 |
| - New-RdsRemoteApp <tenantname> <hostpoolname> <appgroupname> -Name <remoteappname> -Filepath <filepath> -IconPath <iconpath> -IconIndex <iconindex> |
65 |
| - ``` |
| 125 | +- The RemoteApp app group |
66 | 126 |
|
67 |
| -6. To verify that the app was published, run the following cmdlet. |
| 127 | +- Applications added to the app group |
68 | 128 |
|
69 |
| - ```powershell |
70 |
| - Get-RdsRemoteApp <tenantname> <hostpoolname> <appgroupname> |
71 |
| - ``` |
| 129 | +- App group published to the selected users and user groups. |
72 | 130 |
|
73 |
| -7. Repeat steps 1–5 for each application that you want to publish for this app group. |
74 |
| -8. Run the following cmdlet to grant users access to the RemoteApp programs in the app group. |
| 131 | +- If you chose to create a workspace, workspace will be created |
75 | 132 |
|
76 |
| - ```powershell |
77 |
| - Add-RdsAppGroupUser <tenantname> <hostpoolname> <appgroupname> -UserPrincipalName <userupn> |
78 |
| - ``` |
| 133 | +- If you chose to register the app group, the registration will be complete |
79 | 134 |
|
80 | 135 | ## Next steps
|
81 | 136 |
|
|
0 commit comments