Forum Discussion

Stefan Georgiev's avatar
Stefan Georgiev
Former Employee
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
mjzout's avatar
mjzout
Copper Contributor
Jan 29, 2021

Thogjo 

i use AADDS.

the session host has the SMB Reader role on the storage account and for NTFS i've configured read permissions for the session host.

 

Only thing missing is the certificate, gonna try that one 🙂 

Thogjo's avatar
Thogjo
Copper Contributor
Jan 29, 2021

mjzout 

 

I actaully posted this question in another forum and got som answers you might find usefull, ill attach screenshot....

 

 

 

  • mjzout's avatar
    mjzout
    Copper Contributor
    Feb 09, 2021

    Thogjo 

    I'm lost......

     

    computeraccounts has SMB Share reader rights and NTFS read permissions on the share.

    Certificates added to "trusted people" on the hosts.

    Azure file share mounted with SAS key on the hosts

     

    Still getting the error below;

    {"code":"400","message":"ActivityId: Error: Could not get MSIX applications for Host Pool '≤<name>-Test≥' from image '≤\\\\<storageaccount>\\msix\\GoogleChrome.vhdx≥'. Check inner exception for details."}

     

    What am I doing wrong?

    • Thogjo's avatar
      Thogjo
      Copper Contributor
      Feb 09, 2021

      mjzout 

       

      deploying my images with the hyperv role installed, actually made it work

      • DBR14's avatar
        DBR14
        Iron Contributor
        Feb 10, 2021

        Thogjo So you deployed a new session host with an image where hyper v role was enabled?

         

        I can't figure out why I'm getting this... \\storageaccount.file.core.windows.net\fileshare\.adobereaderdc.vhd

         

        I was getting the "Unable to reach virtual disk" and I found I forgot to turn on Validation environment, now I'm getting this...

         

    • Thogjo's avatar
      Thogjo
      Copper Contributor
      Feb 09, 2021

      mjzout 

       

      I'm not sure that VHDX is supported - all mine are VHD's

       

      I get them mounted in the c:\program files\windows Apps folder,  but not registered - I can do the register manually, but thats not how its suppose to work as i understand it.

  • mobilejon's avatar
    mobilejon
    Copper Contributor
    Feb 07, 2021

    I have the same issue. 

    Stefan can you provide exact instructions for how we achieve this on AAD DS? I used SAS Key connection to the share as you alluded to:

    $connectTestResult = Test-NetConnection -ComputerName synfslogix.file.core.windows.net -Port 445
    if ($connectTestResult.TcpTestSucceeded) {
    # Save the password so the drive will persist on reboot
    cmd.exe /C "cmdkey /add:`"synfslogix.file.core.windows.net`" /user:`"Azure\synfslogix`" /pass:`"SASKEY`""
    # Mount the drive
    New-PSDrive -Name Z -PSProvider FileSystem -Root "\\synfslogix.file.core.windows.net\sharename" -Persist
    } else {
    Write-Error -Message "Unable to reach the Azure storage account via port 445. Check to make sure your organization or ISP is not blocking port 445, or use Azure P2S VPN, Azure S2S VPN, or Express Route to tunnel SMB traffic over a different port."
    }

     

    I still have issues where it cannot connect despite all permissions being added.

    Thogjo Stefan Georgiev 

    • Stefan Georgiev's avatar
      Stefan Georgiev
      Former Employee
      Feb 08, 2021

      mobilejon Once mapped did you grant ntfs permissions to the machine accounts?

      • mobilejon's avatar
        mobilejon
        Copper Contributor
        Feb 08, 2021

        Stefan Georgiev I'm guessing you're referring to doing this?

         

        $connectTestResult = Test-NetConnection -ComputerName SHARENAME.file.core.windows.net -Port 445
if ($connectTestResult.TcpTestSucceeded) {
    # Save the password so the drive will persist on reboot
    cmd.exe /C "cmdkey /add:`"synfslogix.file.core.windows.net`" /user:`"SYNTEREX\COMPUTERNAME`" /pass:`"SASKEY`""
    # Mount the drive
    New-PSDrive -Name Z -PSProvider FileSystem -Root "\\SHARENAME.file.core.windows.net\FOLDERNAME" -Persist
} else {
    Write-Error -Message "Unable to reach the Azure storage account via port 445. Check to make sure your organization or ISP is not blocking port 445, or use Azure P2S VPN, Azure S2S VPN, or Express Route to tunnel SMB traffic over a different port."
}