Error adding MSIX app attach to Azure VD from storage account

Martijn Kools 0 Reputation points
2023-11-28T09:27:38.7933333+00:00

Hello,

Adding a VHDX (MSI-X app attach to AVD from a storage account gives me this error:

ActivityId: b151955e-6902-43a5-b399-7a009cea11b1 Error: The MSIX Application metadata expand request failed on all Session Hosts that it was sent to. Session Host: vmweupocavd01, Error: Error accessing virtual disk at ≤\\saseapocavd01.file.core.windows.net\msix\FRF-P_1.0.0.0_x64__rt6ps99bwbnfa.vhdx≥. (Code: 400)

AVD session hosts are added as SMB storage contributor. NTFS permissions are set for the computer accounts as well. When I use a local share in our DC it works fine. When I open a CMD as localsystem (with psexec) on the AVD, I can't map the share (I get asked for a user/pass) so something is wrong although all permissions are ok.

Any idea how to fix this?

Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,216 questions
Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,892 questions
Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,438 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Amira Bedhiafi 19,056 Reputation points
    2023-12-01T15:56:20.4433333+00:00

    Your issue seems to be related to the access or permissions for the VHDX file stored in Azure Files

    Ensure that Azure Files SMB shares are properly set up with the required permissions. Since you mentioned that NTFS permissions are set for the computer accounts, also verify that the Azure Files share has the appropriate SMB ACLs configured.

    I found this old thread : https://www.alexandrumarin.com/azure-msix-app-attach-code-400-error/

    Hope it helps :)

    0 comments No comments

  2. Sumarigo-MSFT 45,316 Reputation points Microsoft Employee
    2023-12-05T14:52:01.51+00:00

    @Martijn Kools Adding more information to the above response!

    The first issue is related to accessing the SMB share from the AVD session hosts, and the second issue is related to accessing the MSIX application metadata from the storage account.

    For the first issue, it's possible that the LocalSystem account does not have the necessary permissions to access the SMB share. When you open a CMD as LocalSystem, it uses the LocalSystem account to authenticate to the SMB share. Make sure that the LocalSystem account has the necessary permissions to access the SMB share. You can also try using a different account to authenticate to the SMB share to see if that resolves the issue.

    For the second issue, it's possible that there is an issue with the MSIX application metadata or the storage account. Check the storage account to ensure that the virtual disk is present and accessible. You can also try accessing the virtual disk directly from the Session Host to see if there are any issues with the network or authentication.

    The error message you are seeing indicates that there was an issue accessing the virtual disk for the MSIX application metadata. The error message specifically mentions that there was an issue accessing the virtual disk at \\saseapocavd01.file.core.windows.net\msix\FRF-P_1.0.0.0_x64__rt6ps99bwbnfa.vhdx.

    Here are some possible causes and solutions for this issue:

    Network connectivity issue: The error message indicates that there was an issue accessing the virtual disk over the network. Check your network connectivity to ensure that you can access the file share at \\saseapocavd01.file.core.windows.net. You can also try accessing the virtual disk directly from the Session Host to see if there are any issues with the network.

    Authentication issue: The error message indicates that there was an issue accessing the virtual disk due to authentication. Check your authentication settings to ensure that the Session Hosts have the necessary permissions to access the file share. You can also try accessing the virtual disk directly from the Session Host to see if there are any issues with authentication.

    File share issue: The error message indicates that there was an issue accessing the virtual disk on the file share. Check the file share to ensure that the virtual disk is present and accessible. You can also try accessing the virtual disk directly from the file share to see if there are any issues with the file share.

    1. MSIX application issue: The error message indicates that there was an issue with the MSIX application metadata. Check the MSIX application to ensure that it is properly configured and deployed. You can also try redeploying the MSIX application to see if that resolves the issue.

    Here are some steps you can take to troubleshoot and potentially resolve the issue:

    Check SMB Share Permissions: Ensure that the SMB share on your DC has the correct permissions. Confirm that the AVD session hosts have been added as SMB storage contributors with the appropriate access rights.

    Verify NTFS Permissions: Double-check the NTFS permissions on the shared folder. Ensure that computer accounts associated with AVD session hosts have the necessary read and write permissions.

    Network Connectivity: Confirm that there are no network connectivity issues between the AVD session hosts and the SMB share. Check for any firewalls, network policies, or routing issues that might affect connectivity.

    LocalSystem Account Permissions: Ensure that the LocalSystem account on the AVD session hosts has the necessary permissions to access the SMB share. This might involve adjusting NTFS permissions specifically for the LocalSystem account.

    MSIX Package Integrity: Verify the integrity of the MSIX package you are trying to access. Ensure that it's not corrupted and can be successfully opened and accessed.

    Storage Account Configuration: Check the configuration of your Azure Storage Account. Ensure that the account is properly configured, and there are no issues with the storage itself.

    1. Logs and Diagnostics: Examine logs and diagnostics on both the AVD session hosts and the DC. Look for any error messages or events that might provide more details about the issue.

    If the issue persists, you may need to redeploy the MSIX application or contact Microsoft support for further assistance.

    0 comments No comments