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
4. Check you only have one object in the application properties by running the following command:
210
+
4. Check you only have one object in the application properties by running the following commands:
211
211
212
212
```azurepowershell
213
213
$app | FL *
214
214
```
215
215
216
-
*Optional*: if you have more than one object in the output, for example an x64 and an x86 version of the same application, you can use the parameter `PackageFullName` to specify which application you want to add by running the following command:
216
+
*Optional*: if you have more than one object in the output, for example an x64 and an x86 version of the same application, you can use the parameter `PackageFullName` to specify which application you want to add by running the following commands:
217
217
218
218
```azurepowershell
219
219
# Specify the package full name
@@ -247,7 +247,7 @@ Here's how to add an MSIX or Appx image as an app attach package using the [Az.D
247
247
248
248
There's no output when the package is added successfully.
249
249
250
-
6. You can verify the package is added by running the following command:
250
+
6. You can verify the package is added by running the following commands:
251
251
252
252
```azurepowershell
253
253
$parameters = @{
@@ -313,7 +313,7 @@ Here's how to assign an application package to host pools as well as groups and
313
313
> [!IMPORTANT]
314
314
> The host pool IDs you specify each time will overwrite any existing assignments. If you want to add or remove a host pool to or from an existing list of host pools, you need to specify all the host pools you want to assign the application to.
315
315
316
-
1. In the same PowerShell session, get the resource IDs of the host pool(s) you want to assign the application to and add them to an array to by running the following command:
316
+
1. In the same PowerShell session, get the resource IDs of the host pool(s) you want to assign the application to and add them to an array to by running the following commands:
317
317
318
318
```azurepowershell
319
319
# Add a comma-separated list of host pools names
@@ -326,7 +326,7 @@ Here's how to assign an application package to host pools as well as groups and
326
326
}
327
327
```
328
328
329
-
1. Once you have the resource IDs of the host pool(s), you can assign the application package to them by running the following command:
329
+
1. Once you have the resource IDs of the host pool(s), you can assign the application package to them by running the following commands:
330
330
331
331
```azurepowershell
332
332
$parameters = @{
@@ -339,7 +339,7 @@ Here's how to assign an application package to host pools as well as groups and
339
339
Update-AzWvdAppAttachPackage @parameters
340
340
```
341
341
342
-
1. To unassign the application package from all host pools, you can pass an empty array of host pools by running the following command:
342
+
1. To unassign the application package from all host pools, you can pass an empty array of host pools by running the following commands:
343
343
344
344
```azurepowershell
345
345
$parameters = @{
@@ -358,7 +358,7 @@ Here's how to assign an application to groups and users using the [Az.DesktopVir
358
358
359
359
1. Get the object ID of the groups or users you want to add to or remove from the application and add them to an array to by using one of the following examples. We recommend you assign applications to groups.
360
360
361
-
1. Get the object ID of the group or groups and add them to an array to by running the following command. This example uses the group display name:
361
+
1. Get the object ID of the group or groups and add them to an array to by running the following commands. This example uses the group display name:
362
362
363
363
```azurepowershell
364
364
# Add a comma-separated list of group names
@@ -375,7 +375,7 @@ Here's how to assign an application to groups and users using the [Az.DesktopVir
375
375
}
376
376
```
377
377
378
-
1. Get the object ID of the user(s) and add them to an array to by running the following command. This example uses the user principal name (UPN):
378
+
1. Get the object ID of the user(s) and add them to an array to by running the following commands. This example uses the user principal name (UPN):
379
379
380
380
```azurepowershell
381
381
# Add a comma-separated list of user principal names
@@ -385,39 +385,43 @@ Here's how to assign an application to groups and users using the [Az.DesktopVir
1. Once you have the object IDs of the users or groups, you can add them to or remove them from the application by using one of the following examples, which assigns the [Desktop Virtualization User](rbac.md#desktop-virtualization-user) RBAC role. You can also assign the Desktop Virtualization User RBAC role to your groups or users using the [New-AzRoleAssignment](../role-based-access-control/role-assignments-powershell.md) cmdlet.
395
+
1. Once you have the object IDs of the users or groups, you can add them to or remove them from the application by using one of the following examples, which assigns the [Desktop Virtualization User](rbac.md#desktop-virtualization-user) RBAC role.
396
396
397
-
1. To add the groups or users to the application, run the following command:
397
+
1. To add the groups or users to the application, run the following commands:
@@ -451,8 +455,7 @@ Here's how to change a package's registration type and state using the [Az.Deskt
451
455
452
456
```azurepowershell
453
457
$parameters = @{
454
-
FullName = '<FullName>'
455
-
HostPoolName = '<HostPoolName>'
458
+
Name = '<Name>'
456
459
ResourceGroupName = '<ResourceGroupName>'
457
460
Location = '<AzureRegion>'
458
461
IsRegularRegistration = $true
@@ -466,7 +469,6 @@ Here's how to change a package's registration type and state using the [Az.Deskt
466
469
```azurepowershell
467
470
$parameters = @{
468
471
Name = '<Name>'
469
-
HostPoolName = '<HostPoolName>'
470
472
ResourceGroupName = '<ResourceGroupName>'
471
473
Location = '<AzureRegion>'
472
474
IsActive = $true
@@ -516,7 +518,7 @@ Here's how to add an application from the package you added in this article to a
516
518
517
519
Here's how to add an application from the package you added in this article to a RemoteApp application group using the [Az.DesktopVirtualization](/powershell/module/az.desktopvirtualization/) PowerShell module.
518
520
519
-
1. In the same PowerShell session, if there are multiple applications in the package, you need to get the application ID of the application you want to add from the package by running the following command:
521
+
1. In the same PowerShell session, if there are multiple applications in the package, you need to get the application ID of the application you want to add from the package by running the following commands:
520
522
521
523
```azurepowershell
522
524
Write-Host "These are the application IDs available in the package. Many packages only contain one application." -ForegroundColor Yellow
@@ -539,7 +541,7 @@ Here's how to add an application from the package you added in this article to a
539
541
New-AzWvdApplication @parameters
540
542
```
541
543
542
-
1. Verify the list of applications in the application group by running the following command:
544
+
1. Verify the list of applications in the application group by running the following commands:
543
545
544
546
```azurepowershell
545
547
$parameters = @{
@@ -584,7 +586,7 @@ Here's how to update an existing package using the Azure portal:
584
586
585
587
Here's how to update an existing package using the [Az.DesktopVirtualization](/powershell/module/az.desktopvirtualization/) PowerShell module.
586
588
587
-
1. In the same PowerShell session, get the properties of the updated application and store them in a variable by running the following command:
589
+
1. In the same PowerShell session, get the properties of the updated application and store them in a variable by running the following commands:
588
590
589
591
```azurepowershell
590
592
# Get the properties of the application
@@ -597,13 +599,13 @@ Here's how to update an existing package using the [Az.DesktopVirtualization](/p
1. Check you only have one object in the application properties by running the following command:
602
+
1. Check you only have one object in the application properties by running the following commands:
601
603
602
604
```azurepowershell
603
605
$app | FL *
604
606
```
605
607
606
-
If you have more than one object in the output, for example an x64 and an x86 version of the same application, you can use the parameter `PackageFullName` to specify which one you want to add by running the following command:
608
+
If you have more than one object in the output, for example an x64 and an x86 version of the same application, you can use the parameter `PackageFullName` to specify which one you want to add by running the following commands:
607
609
608
610
```azurepowershell
609
611
# Specify the package full name
@@ -707,7 +709,7 @@ Here's how to add an MSIX package using the [Az.DesktopVirtualization](/powershe
2. Get the properties of the application in the MSIX image you want to add and store them in a variable by running the following command:
712
+
2. Get the properties of the application in the MSIX image you want to add and store them in a variable by running the following commands:
711
713
712
714
```azurepowershell
713
715
# Get the properties of the MSIX image
@@ -728,13 +730,13 @@ Here's how to add an MSIX package using the [Az.DesktopVirtualization](/powershe
728
730
hp01/expandmsiximage
729
731
```
730
732
731
-
3. Check you only have one object in the application properties by running the following command:
733
+
3. Check you only have one object in the application properties by running the following commands:
732
734
733
735
```azurepowershell
734
736
$app | FL *
735
737
```
736
738
737
-
If you have more than one object in the output, for example an x64 and an x86 version of the same application, you can use the parameter `PackageFullName` to specify which one you want to add by running the following command:
739
+
If you have more than one object in the output, for example an x64 and an x86 version of the same application, you can use the parameter `PackageFullName` to specify which one you want to add by running the following commands:
738
740
739
741
```azurepowershell
740
742
# Specify the package full name
@@ -767,7 +769,7 @@ Here's how to add an MSIX package using the [Az.DesktopVirtualization](/powershe
767
769
768
770
There's no output when the MSIX package is added successfully.
769
771
770
-
5. You can verify the MSIX package is added by running the following command:
772
+
5. You can verify the MSIX package is added by running the following commands:
771
773
772
774
```azurepowershell
773
775
$parameters = @{
@@ -827,7 +829,7 @@ Here's how to change a package's registration type and state using the Azure por
827
829
828
830
Here's how to change a package's registration type and state using the [Az.DesktopVirtualization](/powershell/module/az.desktopvirtualization/) PowerShell module.
829
831
830
-
1. In the same PowerShell session, get a list of MSIX packages on a host pool and their current registration type and state by running the following command:
832
+
1. In the same PowerShell session, get a list of MSIX packages on a host pool and their current registration type and state by running the following commands:
831
833
832
834
```azurepowershell
833
835
$parameters = @{
@@ -945,7 +947,7 @@ Here's how to add MSIX applications to an application group using the [Az.Deskto
945
947
New-AzWvdApplication @parameters
946
948
```
947
949
948
-
1. To add an MSIX application to a RemoteApp application group, if there are multiple applications in the package, you need to get the application ID of the application you want to add from the package by running the following command:
950
+
1. To add an MSIX application to a RemoteApp application group, if there are multiple applications in the package, you need to get the application ID of the application you want to add from the package by running the following commands:
949
951
950
952
```azurepowershell
951
953
Write-Host "These are the application IDs available in the package. Many packages only contain one application." -ForegroundColor Yellow
@@ -968,7 +970,7 @@ Here's how to add MSIX applications to an application group using the [Az.Deskto
968
970
New-AzWvdApplication @parameters
969
971
```
970
972
971
-
Verify the list of applications in the application group by running the following command:
973
+
Verify the list of applications in the application group by running the following commands:
972
974
973
975
```azurepowershell
974
976
$parameters = @{
@@ -1002,7 +1004,7 @@ Here's how to remove an MSIX package from your host pool using the Azure portal:
1002
1004
1003
1005
Here's how to remove applications using the [Az.DesktopVirtualization](/powershell/module/az.desktopvirtualization/) PowerShell module.
1004
1006
1005
-
1. In the same PowerShell session, get a list of MSIX packages on a host pool by running the following command:
1007
+
1. In the same PowerShell session, get a list of MSIX packages on a host pool by running the following commands:
1006
1008
1007
1009
```azurepowershell
1008
1010
$parameters = @{
@@ -1021,7 +1023,7 @@ Here's how to remove applications using the [Az.DesktopVirtualization](/powershe
1021
1023
My App \\fileshare\Apps\MyApp\MyApp.cim hp01/MyApp_1.0.0.0_neutral__abcdef123ghij 1.0.0.0
1022
1024
```
1023
1025
1024
-
1. Find the package you want to remove and use the value for the `Name` parameter, but remove the **host pool name** and `/` from the start. For example, `hp01/MyApp_1.0.0.0_neutral__abcdef123ghij` becomes `MyApp_1.0.0.0_neutral__abcdef123ghij`. Then remove the package by running the following command:
1026
+
1. Find the package you want to remove and use the value for the `Name` parameter, but remove the **host pool name** and `/` from the start. For example, `hp01/MyApp_1.0.0.0_neutral__abcdef123ghij` becomes `MyApp_1.0.0.0_neutral__abcdef123ghij`. Then remove the package by running the following commands:
0 commit comments