Forum Discussion
MicrosoftMSIX app attach Azure portal integration public preview
Stefan Georgiev I could not add any MSIX package or image. Tried to add network fileshare path, Azure file share path, file URL, etc. Keep getting the error:
I got the "No MSIX packages could be retrieved from the image path" error. Error type is "aap contains untrusted signature". I am trying to use the chome msix package provided. I can't do anything with the CRT certificate on github, it says invalid. Please advice Stefan Georgiev Thank you.
- TomHickling
You can go back up a level at https://github.com/stgeorgi/msixappattach/find/master . Then install into Local Computer > Trusted People
- I already tried this but got an error: The file is invalid for use as the following: Security Certificate.
grobersoSame here. Any feedback you can provide?
Stefan GeorgievThis is a known issue. We are trying to deploy a fix tomorrow (today 12/18). However, if you have an alternative sub we can whitelist it and circumvent the bug.
- Stefan Georgiev
Edmond Chou the error you are describing is due to the session host in your host pool not having the certificate added to trusted people. That is the same certificate that has been used to package the application.
- Stefan Georgiev
Edmond Chou Apologies, I do not recall putting cert on GitHub can you share the URL (the cert in the documentation is from my OneDrive)
Stefan Georgiev Hi Stefan,
I was trying to use the crt file from here
it was included in one of the post that you shared.
Thank you
RahulKumar1987Please Copy and add the Certificate to the Local Trusted Root of each WVD Session host machine where the MSIX App Attach should be published. This will resolve your issue
Anyone know why this is happening? UNC path is 110% correct... I made a adobereaderdc.vhd and its in the Azure File Share.
- Does the computer account have smb reader access in iam (cant remember the excact name of the role)
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. - Stefan GeorgievDid you setup permissions for hte machine accounts?
- Am getting the same with one app. I packaged it exactly the same way as I packaged notepadplusplus, but it won't have it - empty error as above. All logs from the WVD session host say it appeared to mount and scan the VHDX but I still end up with the above. No idea why as ofc it's all masked in the portal. Yet, I can Add-AppXPackage from the source MSIX fine. I generated the VHDX using MSIXMGR so what else can I do to diagnose...? 😞
- We gave up on MSIX App Attach because frankly, it's worthless right now. We know how to do it and make it work, but wasting time "packaging" stuff only to have it fail in most cases for other programs is a waste of effort. Until a vendor decides to utilize MSIX themselves there's little value. I have no use for attaching VLC and Notepad++ or other rinkydink programs that have little value if any in our production environment. I mean Microsoft doesn't even have their own product installers made into MSIX... Give me an Office Suite in MSIX and I'll be impressed.
- Stefan GeorgievHi, on each machine in the session host you must import the cert (used to digitally sign the msix app) in trusted people
I PM'd you my business sub ID.
I have the cert install via the image does that matter or does it need to be done per session host individually? Im guessing Im fine since I did get past part of my issues. For some reason 2 days later the UNC paths just magically worked after I changed nothing as far as the VHDs.
However now if we make CPU-Z/NotePad++/VLCPlayer a remote app, they show in the RD Client but when we launch them it just opens up Documents on my machine -- very odd.
When I add the apps to the DAG nothing happens. No apps snap in, nothing.... I followed Christian Brinkhoff's guide bit by bit and this doesn't work.
I can't even continue testing right now because ever since this new agent 1.0.2839.400 got pushed my SessionHosts go to Unavailable. If I remove the agents, and sxs module, remove it from the host, then reinstall the agent downloading from MSFT docs which is an older version its fine and is available UNTIL this new agent installs then its back to Unavailable. This was occurring across all my Session hosts, even ones that were 2-3 images behind so I could see if something weird happened between tests.
I'm quite stuck and confused.
In order to test this MSIX App Attach my hostpool has to be in a validation environment HOWEVER when put in this mode it downloads this WVD AGENT 1.0.2839.400 which almost immediately breaks my host into Unavailable and that seems to prevent other parts of this from working stating that the Hostpool doesn't have any available VMs
Well I put my hostpool back into non-validation environment and rebooted my SessionHosts and VIOLA they downloaded WVD AGENT v1.0.2800.2700 and the SessionHosts are now available.
Can someone explain how this is supposed to work if its required to be in validation but validation then breaks the SessionHosts availability?
