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/app-attach-create-msix-image.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,12 @@ description: To use app attach in Azure Virtual Desktop, you need to expand an M
4
4
ms.topic: how-to
5
5
author: dknappettmsft
6
6
ms.author: daknappe
7
-
ms.date: 10/10/2023
7
+
ms.date: 03/04/2024
8
8
---
9
9
10
10
# Create an MSIX image to use with app attach in Azure Virtual Desktop
11
11
12
-
To use MSIX packages with MSIX app attach and app attach in Azure Virtual Desktop, you need to expand an MSIX package application into an MSIX image. This article shows you how to create an MSIX image.
12
+
To use MSIX packages with app attach and MSIX app attach in Azure Virtual Desktop, you need to expand an MSIX package application into an MSIX image. This article shows you how to create an MSIX image.
Copy file name to clipboardExpand all lines: articles/virtual-desktop/app-attach-overview.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,11 +129,11 @@ MSIX app attach doesn't limit the number of applications users can use. You shou
129
129
## Application state
130
130
131
131
::: zone pivot="app-attach"
132
-
An MSIX and Appx package is set as **active** or **inactive**. Packages set to active makes the application available to users. Packages set to inactive are ignored by Azure Virtual Desktop and not added when a user signs-in.
132
+
An MSIX and Appx package is set as **active** or **inactive**. Packages set to active makes the application available to users. Packages set to inactive are ignored by Azure Virtual Desktop and not added when a user signsin.
133
133
::: zone-end
134
134
135
135
::: zone pivot="msix-app-attach"
136
-
An MSIX package is set as **active** or **inactive**. MSIX packages set to active makes the application available to users. MSIX packages set to inactive are ignored by Azure Virtual Desktop and not added when a user signs-in.
136
+
An MSIX package is set as **active** or **inactive**. MSIX packages set to active makes the application available to users. MSIX packages set to inactive are ignored by Azure Virtual Desktop and not added when a user signsin.
Copy file name to clipboardExpand all lines: articles/virtual-desktop/app-attach-setup.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
@@ -1,22 +1,18 @@
1
1
---
2
-
title: Add and manage MSIX app attach and app attach applications - Azure Virtual Desktop
3
-
description: Learn how to add and manage applications with MSIX app attach and app attach in Azure Virtual Desktop using the Azure portal and Azure PowerShell, where you can dynamically attach applications from an application package to a user session.
2
+
title: Add and manage app attach and MSIX app attach applications - Azure Virtual Desktop
3
+
description: Learn how to add and manage applications with app attach and MSIX app attach in Azure Virtual Desktop using the Azure portal and Azure PowerShell, where you can dynamically attach applications from an application package to a user session.
# Add and manage MSIX app attach and app attach applications in Azure Virtual Desktop
13
-
14
-
> [!IMPORTANT]
15
-
> App attach is currently in PREVIEW.
16
-
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
12
+
# Add and manage app attach and MSIX app attach applications in Azure Virtual Desktop
17
13
18
14
> [!TIP]
19
-
> A new version of app attach for Azure Virtual Desktop is available in preview. Select a button at the top of this article to choose between *MSIX app attach*(current) and *app attach* (preview) to see the relevant documentation.
15
+
> A new version of app attach for Azure Virtual Desktop is available. Select a button at the top of this article to choose between *app attach* and *MSIX app attach* to see the relevant documentation.
20
16
21
17
::: zone pivot="app-attach"
22
18
App attach enables you to dynamically attach applications from an application package to a user session in Azure Virtual Desktop. Applications aren't installed locally on session hosts or images, enabling you to create fewer custom images for your session hosts, and reducing operational overhead and costs for your organization. Delivering applications with app attach also gives you greater control over which applications your users can access in a remote session.
@@ -27,15 +23,15 @@ MSIX app attach enables you to dynamically attach applications from an applicati
27
23
::: zone-end
28
24
29
25
::: zone pivot="app-attach"
30
-
This article shows you how to add and manage applications with app attach in Azure Virtual Desktop using the Azure portal and Azure PowerShell. You can't add or manage app attach applications using Azure CLI. Before you start, make sure you read the overview for [MSIX app attach and app attach in Azure Virtual Desktop](app-attach-overview.md).
26
+
This article shows you how to add and manage applications with app attach in Azure Virtual Desktop using the Azure portal and Azure PowerShell. You can't add or manage app attach applications using Azure CLI. Before you start, make sure you read the overview for [app attach and MSIX app attach in Azure Virtual Desktop](app-attach-overview.md).
31
27
::: zone-end
32
28
33
29
::: zone pivot="msix-app-attach"
34
-
This article shows you how to add and manage MSIX packages with MSIX app attach in Azure Virtual Desktop using the Azure portal and Azure PowerShell. You can't add or manage MSIX app attach applications using Azure CLI. Before you start, make sure you read the overview for [MSIX app attach and app attach in Azure Virtual Desktop](app-attach-overview.md).
30
+
This article shows you how to add and manage MSIX packages with MSIX app attach in Azure Virtual Desktop using the Azure portal and Azure PowerShell. You can't add or manage MSIX app attach applications using Azure CLI. Before you start, make sure you read the overview for [app attach and MSIX app attach in Azure Virtual Desktop](app-attach-overview.md).
35
31
::: zone-end
36
32
37
33
> [!IMPORTANT]
38
-
> You have to choose whether you want to use MSIX app attach or app attach with a host pool. You can't use both versions with the same host pool.
34
+
> You have to choose whether you want to use app attach or MSIX app attach with a host pool. You can't use both versions with the same host pool.
39
35
40
36
## Prerequisites
41
37
@@ -99,7 +95,7 @@ In order to use MSIX app attach in Azure Virtual Desktop, you need to meet the p
99
95
>
100
96
> - All MSIX and Appx application packages include a certificate. You're responsible for making sure the certificates are trusted in your environment. Self-signed certificates are supported with the appropriate chain of trust.
101
97
>
102
-
> - You have to choose whether you want to use MSIX app attach or app attach with a host pool. You can't use both versions with the same package in the same host pool.
98
+
> - You have to choose whether you want to use app attach or MSIX app attach with a host pool. You can't use both versions with the same package in the same host pool.
103
99
::: zone-end
104
100
105
101
::: zone pivot="msix-app-attach"
@@ -441,7 +437,7 @@ Here's how to change a package's registration type and state using the Azure por
441
437
442
438
1. Select the name of the package you want to change.
443
439
444
-
1. To change the registration type, select **On-demand** or **Log on blocking**, then select **Save**.
440
+
1. To change the registration type, select **On-demand** or **Register at log on**, then select **Save**.
445
441
446
442
1. To change the state, select **Inactive** or **Active**, then select **Save**.
447
443
@@ -451,7 +447,7 @@ Here's how to change a package's registration type and state using the [Az.Deskt
451
447
452
448
1. In the same PowerShell session, you can change the registration type and state by running the following commands:
453
449
454
-
1. Change the registration type by running the following command. Set `IsRegularRegistration` to `$true` for **Log on blocking** or `$false` for **On-demand**.
450
+
1. Change the registration type by running the following command. Set `IsRegularRegistration` to `$true` for **Register at log on** or `$false` for **On-demand**.
455
451
456
452
```azurepowershell
457
453
$parameters = @{
@@ -823,7 +819,7 @@ Here's how to change a package's registration type and state using the Azure por
823
819
824
820
1. Select the name of the MSIX package you want to change.
825
821
826
-
1. To change the registration type, select **On-demand** or **Log on blocking**, then select **Save**.
822
+
1. To change the registration type, select **On-demand** or **Register at log on**, then select **Save**.
827
823
828
824
1. To change the state, select **Inactive** or **Active**, then select **Save**.
829
825
@@ -852,7 +848,7 @@ Here's how to change a package's registration type and state using the [Az.Deskt
852
848
853
849
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`. Here are a couple of examples.
854
850
855
-
1. Change the registration type by running the following command. Set `IsRegularRegistration` to `$true` for **Log on blocking** or `$false` for **On-demand**.
851
+
1. Change the registration type by running the following command. Set `IsRegularRegistration` to `$true` for **Register at log on** or `$false` for **On-demand**.
Copy file name to clipboardExpand all lines: articles/virtual-desktop/app-attach-test-msix-packages.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,14 +4,14 @@ description: Learn how to mount disk images for testing and troubleshooting outs
4
4
ms.topic: how-to
5
5
author: dknappettmsft
6
6
ms.author: daknappe
7
-
ms.date: 01/25/2024
7
+
ms.date: 03/04/2024
8
8
---
9
9
10
10
# Test MSIX packages for app attach
11
11
12
-
This article shows you how to mount MSIX packages outside of Azure Virtual Desktop to help test your packages for app attach. The APIs that power app attach are available for Windows 11 Enterprise and Windows 10 Enterprise. These APIs can be used outside of Azure Virtual Desktop for testing, however there's no management plane for MSIX app attach or app attach outside of Azure Virtual Desktop.
12
+
This article shows you how to mount MSIX packages outside of Azure Virtual Desktop to help test your packages for app attach. The APIs that power app attach are available for Windows 11 Enterprise and Windows 10 Enterprise. These APIs can be used outside of Azure Virtual Desktop for testing, however there's no management plane for app attach or MSIX app attach outside of Azure Virtual Desktop.
13
13
14
-
For more information about MSIX app attach and app attach, see [MSIX app attach and app attach in Azure Virtual Desktop](app-attach-overview.md).
14
+
For more information about app attach and MSIX app attach, see [app attach and MSIX app attach in Azure Virtual Desktop](app-attach-overview.md).
15
15
16
16
## Prerequisites
17
17
@@ -208,7 +208,7 @@ Now that your MSIX package is registered, your application should be available f
208
208
209
209
## Deregister an MSIX package
210
210
211
-
Once you're finished with your MSIX package and are ready to remove it, first you need to deregister it. To deregister the MSIX package, run the following commands in the same PowerShell session. These commands get the disk's `DeviceId` parameter again, and removes the package using the `$msixPackageFullName` variable created in a previous section.
211
+
Once you're finished with your MSIX package and are ready to remove it, first you need to deregister it. To deregister the MSIX package, run the following commands in the same PowerShell session. These commands get the disk's `DeviceId` parameter again, and remove the package using the `$msixPackageFullName` variable created in a previous section.
Copy file name to clipboardExpand all lines: articles/virtual-desktop/authentication.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: virtual-desktop
5
5
author: Heidilohr
6
6
ms.service: virtual-desktop
7
7
ms.topic: conceptual
8
-
ms.date: 11/14/2023
8
+
ms.date: 03/04/2024
9
9
ms.author: helohr
10
10
---
11
11
# Supported identities and authentication methods
@@ -17,7 +17,7 @@ In this article, we'll give you a brief overview of what kinds of identities and
17
17
Azure Virtual Desktop supports different types of identities depending on which configuration you choose. This section explains which identities you can use for each configuration.
18
18
19
19
>[!IMPORTANT]
20
-
>Azure Virtual Desktop doesn't support signing in to Microsoft Entra ID with one user account, then signing in to Windows with a separate user account. Signing in with two different accounts at the same time can lead to users reconnecting to the wrong session host, incorrect or missing information in the Azure portal, and error messages appearing while using MSIX app attach.
20
+
>Azure Virtual Desktop doesn't support signing in to Microsoft Entra ID with one user account, then signing in to Windows with a separate user account. Signing in with two different accounts at the same time can lead to users reconnecting to the wrong session host, incorrect or missing information in the Azure portal, and error messages appearing while using app attach or MSIX app attach.
Copy file name to clipboardExpand all lines: articles/virtual-desktop/publish-applications-stream-remoteapp.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: How to publish applications with RemoteApp in Azure Virtual Desktop
4
4
author: dknappettmsft
5
5
ms.topic: how-to
6
6
ms.custom: devx-track-azurepowershell
7
-
ms.date: 12/08/2023
7
+
ms.date: 03/05/2024
8
8
ms.author: daknappe
9
9
---
10
10
@@ -178,7 +178,7 @@ Here's how to add applications to a RemoteApp application group using the [Az.De
178
178
New-AzWvdApplication @parameters
179
179
```
180
180
181
-
- To add an MSIX or Appx application from *MSIX app attach* or *app attach (preview)*, your MSIX package must already be [added and assigned to your host pool](app-attach-setup.md). Run the commands from one of the following examples:
181
+
- To add an MSIX or Appx application from *app attach* or *MSIX app attach*, your MSIX package must already be [added and assigned to your host pool](app-attach-setup.md). Run the commands from one of the following examples:
182
182
183
183
- For **MSIX app attach**, get the application details and store them in a variable:
Copy file name to clipboardExpand all lines: articles/virtual-desktop/session-host-status-health-checks.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Session host statuses and health checks in Azure Virtual Desktop
3
3
description: Learn about the different statuses and health checks for session hosts in Azure Virtual Desktop.
4
4
author: heidilohr
5
5
ms.topic: conceptual
6
-
ms.date: 09/11/2023
6
+
ms.date: 03/05/2024
7
7
ms.author: helohr
8
8
---
9
9
# Session host statuses and health checks in Azure Virtual Desktop
@@ -35,7 +35,7 @@ The health check is a test run by the agent on the session host. The following t
35
35
| Domain joined | Verifies that the session host is joined to a domain controller. | If this check fails, users won't be able to connect to the session host. To solve this issue, join your session host to a domain. |
36
36
| Geneva Monitoring Agent | Verifies that the session host has a healthy monitoring agent by checking if the monitoring agent is installed and running in the expected registry location. | If this check fails, it's semi-fatal. There may be successful connections, but they'll contain no logging information. To resolve this issue, make sure a monitoring agent is installed. If it's already installed, contact Microsoft support. |
37
37
| Side-by-side (SxS) Stack Listener | Verifies that the side-by-side stack is up and running, listening, and ready to receive connections. | If this check fails, it's fatal, and users won't be able to connect to the session host. Try restarting your virtual machine (VM). If restarting doesn't work, contact Microsoft support. |
38
-
| App attach health check | Verifies that the [MSIX app attach](what-is-app-attach.md) service is working as intended during package staging or destaging. | If this check fails, it isn't fatal. However, certain apps stop working for end-users. |
38
+
| App attach health check | Verifies that the [app attach or MSIX app attach](what-is-app-attach.md) service is working as intended during package staging or destaging. | If this check fails, it isn't fatal. However, certain apps stop working for end-users. |
39
39
| Domain trust check | Verifies the session host isn't experiencing domain trust issues that could prevent authentication when a user connects to a session. | If this check fails, it's fatal. The service won't be able to connect if it can't reach the authentication domain for the session host. |
40
40
| Metadata service check | Verifies the metadata service is accessible and returns compute properties. | If this check fails, it isn't fatal. |
description: Learn how to troubleshoot app attach in Azure Virtual Desktop, where you can dynamically attach applications from an application package to a user session.
4
4
author: dknappettmsft
5
5
ms.topic: troubleshooting
6
-
ms.date: 08/17/2023
6
+
ms.date: 03/05/2024
7
7
ms.author: daknappe
8
8
---
9
9
10
10
# Troubleshoot app attach in Azure Virtual Desktop
11
11
12
-
> [!IMPORTANT]
13
-
> App attach in Azure Virtual Desktop is currently in PREVIEW. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
14
-
15
12
If you're having issues when using app attach, use the information in this article to help troubleshoot.
16
13
17
14
## Check file share access
@@ -79,4 +76,4 @@ To validate that your session hosts have the necessary access to a file share co
79
76
80
77
## Next steps
81
78
82
-
[Test MSIX packages with MSIX app attach or app attach](app-attach-test-msix-packages.md).
79
+
[Test MSIX packages with app attach or MSIX app attach](app-attach-test-msix-packages.md).
0 commit comments