Forum Discussion
MSIX app attach Azure portal integration public preview
Anyone know why this is happening? UNC path is 110% correct... I made a adobereaderdc.vhd and its in the Azure File Share.
Did you add the certificate to your session host?
Stefan Georgiev just released this troubleshooting methodology
https://github.com/stgeorgi/msixappattach/blob/master/Troubleshooting%20methedology%20v2.pdf
If above does not work, refer to Stefans PDF in the git link.
Thogjo the issue was the .vhd -- in this case the AdobeReader package created by MSIX packager failed.
I then made one with Notepad++ and it worked! So the error I was getting is indicative of a bad .vhd/MSIX packaging.
I then immediately tried CPU-Z a super basic program, and it also failed just like Adobe Reader....
So I can only conclude at this point that this MSIX Packager is a total POS and its what is causing me headaches. If a basic program like CPU-Z can't be packaged and exported and attached then there is 0% hope right now a much more complex one will.
I'm going to give VLC player a try since that was one I saw in a demo video, but that doesn't do much for my progression to production WVD with this.
- DBR14 are you using the MSIX packaging tool to create an MSIX out of CPU-Z? Secondly, how are you creating the VHD, please try this tool https://techcommunity.microsoft.com/t5/windows-virtual-desktop/simplify-msix-image-creation-with-the-msixmgr-tool/td-p/2118585 to avoid badly structured VHDs.
Lastly we have a troubleshooting guide for MSIX app attach here you may find useful https://github.com/stgeorgi/msixappattach/blob/master/Troubleshooting%20methedology%20v2.pdf - So VLC also failed with the same error.
Oddly enough when I put in the previously working file path for the working Notepad++ vhd IT ALSO does this error now... \\mystorageaccount.file.core.windows.net\myfileshare\notepadplusplus.vhd and now it says this which Im not totally worried about because that TestHost-3 is irrelevant, but I don't get why it trips now and didn't before.
{"code":"400","message":"ActivityId: 7d376443-4102-49fc-be01-db92282a28e1 Error: The MSIX Application metadata expand request failed on all Session Hosts that it was sent to. Session Host: TestHost-3, Error: App contains untrusted signature."} YET... that same path has been unchanged and the VHD is the same ONE that worked under an hour ago.
So now I'm really lost as to what the issue is, this seems outlandishly inconsistent and troubleshooting seems fruitless...- Have you included that certificate with which the app was packaged in the trusted people location on your host pool TestHost-3?
- I have pointed that out numerous times earlier, but yes - you are correct
AADDS Is ‘no go’ with app attachWill AAD-DS be supported by the time this goes GA? Any potential way for it to be so like hosting the VHDs on a server domain joined to AAD-DS? I'm asking because if we will never get this I may need to shift from WVD to Horizon on Azure
