Forum Discussion
MSIX 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:
tch0704 Use UNC naming format. Eg: \\tchfs.file.core.windows.net\wvdnewshare... etc
- This is an HTTPS path. Those are not supported. Must be an UNC path \\tchfs.file.core.*\wvdshare\*
tch0704
Please remove https: and replace "/" with "\"
For eg:-The file share path should be in this format:-
\\storageaccount.file.core.windows.net\msixshare\appfolder\MSIXimage.vhd
Thanks
tch0704 we do not support HTTP/S paths must be an SMB resolvable path
- TomHickling
Microsoft
tch0704 The path needs to be entered in UNC format i.e. \\server\share\folder\file.vhd
- Dear Tom,
I already tried with "\\wvd-dc\appshare\...vhd" but still didn't work. Thanks.- TomHickling
tch0704 I would suggest you check the permissions on the storage, both the Share and NTFS permissions and the cert is installed on the session host as described in this article
- I used the chrome and edge vhdx's and WVD said there were no packages in the vhdx. I do have Az Files joined to the Domain.
- Can you PM me with little more details on the error?
groberso do you have the actual error displayed by the portal?
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.
- Hi, 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.
Anyone know why this is happening? UNC path is 110% correct... I made a adobereaderdc.vhd and its in the Azure File Share.
- 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...? 😞
Please 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
