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/manage-app-groups-powershell.md
+38-17Lines changed: 38 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,12 +5,12 @@ services: virtual-desktop
5
5
author: Heidilohr
6
6
7
7
ms.service: virtual-desktop
8
-
ms.topic: tutorial
8
+
ms.topic: conceptual
9
9
ms.date: 04/30/2020
10
10
ms.author: helohr
11
11
manager: lizross
12
12
---
13
-
# Tutorial: Manage app groups using PowerShell
13
+
# Manage app groups using PowerShell
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).
@@ -26,60 +26,81 @@ In this tutorial, learn how to:
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:
This article assumes you've followed the instructions in [Set up the PowerShell module](powershell-module.md) to set up your PowerShell module and sign in to your Azure account.
34
32
35
33
## Create a RemoteApp group
36
34
35
+
To create a RemoteApp group with PowerShell:
36
+
37
37
1. Run the following PowerShell cmdlet to create a new empty RemoteApp app group.
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.
Id : /subscriptions/beec440d-0623-4cf1-8237-e1cb4a9bcba7<sub id>/resourcegroups/0301RG/providers/Microsoft.DesktopVirtualization/applicationgroups/0301RAG/startmenuitems/Access
65
+
Name : 0301RAG/Access
66
+
Type : Microsoft.DesktopVirtualization/applicationgroups/startmenuitems
67
+
68
+
AppAlias : charactermap
69
+
CommandLineArgument :
70
+
FilePath : C:\windows\system32\charmap.exe
71
+
FriendlyName :
72
+
IconIndex : 0
73
+
IconPath : C:\windows\system32\charmap.exe
74
+
Id : /subscriptions/beec440d-0623-4cf1-8237-e1cb4a9bcba7<sub id>/resourcegroups/0301RG/providers/Microsoft.DesktopVirtualization/applicationgroups/0301RAG/startmenuitems/Character Map
75
+
Name : 0301RAG/Character Map
76
+
Type : Microsoft.DesktopVirtualization/applicationgroups/startmenuitems
53
77
```
54
78
55
79
4. Run the following cmdlet to install the application based on `AppAlias`. `AppAlias` becomes visible when you run the output from step 3.
In this tutorial, you learned how to create an app group, populate it with RemoteApp programs, and assign users to the app group. To learn how to create a validation host pool, see the following tutorial. You can use a validation host pool to monitor service updates before rolling them out to your production environment.
83
-
84
-
> [!div class="nextstepaction"]
85
-
> [Create a host pool to validate service updates](./create-validation-host-pool.md)
106
+
If you came to this How-to guide from our tutorials, check out [Create a host pool to validate service updates](create-validation-host-pool.md). You can use a validation host pool to monitor service updates before rolling them out to your production environment.
0 commit comments