Forum Discussion

Stefan Georgiev's avatar
Stefan Georgiev
Iron Contributor
Dec 14, 2020

MSIX app attach Azure portal integration public preview

MSIX app attach is an application layering solution that allows you to dynamically attach an application (that is an MSIX package) to a user session. Separating the application from the operating sys...
msix app attach
msxi
WVD
biginquebec130's avatar
biginquebec130
Copper Contributor
Dec 19, 2020

Stefan Georgiev 

hello, 

 

I still have this error The MSIX Application metadata expand request failed on all Session Hosts that it was sent to. Session Host: wvd-0, Error: Error accessing virtual disk at ≤\\http://disq.us/url?url=http%3A%2F%2Fstowvd.file.core.windows.net%3AbaMBd1fsU9jqGVMJMVBgv-L8_Rc&cuid=4572167\msix\bignotepadplusplus.vhd≥. (Code: 400)

 

As you can see, some stuffs are missing from the page  ADD MSIX PACKAGE (we should see msix package, package application, display name....)

Same problem after recreating the hostpool on another region.

 

 

 

  • biginquebec130's avatar
    biginquebec130
    Copper Contributor
    Dec 20, 2020

    Stefan Georgiev 

    hello Stefan

    I checked once again permissions for session host on both share (RBAC) and directory level (NTFS) but I still have this error : “...Error accessing virtual disk at…”

     

     

    Note that Host and storage account are joined to an Azure ADDS (not classic ADDS)

    -RBAC : my host has the role Storage File Data SMB Share Contributor on the Storage account

    (it’s also a member of an Azure AD group with this role)

     

    -NTFS level : my Host has -modify- on the storage account’ Share

    Note that the host can access and mount this vhd \\stoxxx.file.core.windows.net\msix\GoogleChrome_68.46.66.0_x64__74vyvr5aw93s6.vhdx

     

    I tried put the vhd on a local share and it works like a charm.

    Please help me to find where is my mistake with Azure File permissions in the Azure ADDS scenario.

     

    Best regards

    • nbird22's avatar
      nbird22
      Iron Contributor
      Dec 21, 2020

      biginquebec130 

      Pretty sure this isnt supported. Games a bogey with AAD DS as there is no hybrid join capability so no writing back the devices to AAD. You're giving the Managed Identity of the VM access to FileShare, this isnt the AD object for which it'll determine has the correct NTFS permissions. 
      Keen to get confirmation/roadmap item for this scenario though as we have a few environments that use standalone AAD DS as opposed to classic ADDS with Synchronization.

      • biginquebec130's avatar
        biginquebec130
        Copper Contributor
        Dec 21, 2020
        You´re probably right ; but note that I could give NTFS rights to AADDS host -
        so the problem could be that there is no writeback to AAD...

Resources