Forum Discussion

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...

Copper Contributor

Dec 22, 2020

Maybe some assistance from me (got it working). Please check following:

- Try to deploy a "local" share through a server

- Enable validation hostpool

- Install the Certificate on all VMs in the hostpool you want to deploy the App (Cert -> Trusted People)

- Install the Hyper-V role / Hyper-V powershell ( Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All) on all VMs in the hostpool

- Add the package in the hostpool (pay attention: only the UNC path is accepeted: \\fileserver\Example\ExampleApp.vhd)

- Wait about 2-3 minutes before connecting to the host. It takes some time till the settings are published to the hosts in the hostpool and the app is visible

schmidtp_duna-drava_hu

Copper Contributor

Dec 22, 2020

EddyCC

Thanks for the effort!

- Try to deploy a "local" share through a server

--> I stayed with NetApp Files. The share is readable for everyone, so no permission problems can persist, and I have the profile in the same place, so the share is proven to be working.

- Enable validation hostpool

--> I do only have validation host pools.

- Install the Certificate on all VMs in the hostpool you want to deploy the App (Cert -> Trusted People)

--> Done from the first moment.

- Install the Hyper-V role / Hyper-V powershell ( Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All) on all VMs in the hostpool

--> That was missing, thanks for the hint! However, nothing changed when I switched the Hyper-V features on, even not after a few minutes and a few reboots. I tried also switch Inactive/Active the added MSIX applications, hoping it helps to "trigger" the mount of VHDs, but nothing.

- Add the package in the hostpool (pay attention: only the UNC path is accepeted: \\fileserver\Example\ExampleApp.vhd)

--> That is OK, there is no other way to succeed, the portal is checking thorougly the package before adding.

- Wait about 2-3 minutes before connecting to the host. It takes some time till the settings are published to the hosts in the hostpool and the app is visible.

--> Yeah, I did, as mentioned, also rebooted the VM a few times.
I do really appreciate your helpfulness, despite of the result.

TomHickling
Microsoft
Dec 22, 2020
Hyper-v is only required to get the new-vhd command and hyper-v service required to create new vhd(x) that are part of the expansion process of getting the msix expanded to a vhd file. This is not a requirement for the mounting to a session host. What version of the WVD agent is installed?
- michaelgooding
  Copper Contributor
  Dec 22, 2020
  TomHickling Hi Tom - along the same lines, is this section in the MS Docs applicable to the session hosts that will receive MSIX App Attach packages, or for VMs/etc. that need to be used to create the packages? https://docs.microsoft.com/en-us/azure/virtual-desktop/app-attach-azure-portal#turn-off-automatic-updates-for-msix-app-attach-applications
- EddyCC
  Copper Contributor
  Dec 22, 2020
  TomHickling
  
  Strange, after I installed the Hyper-V module everything worked fine on the session hosts. Before no apps were visible.
  - Stefan Georgiev
    Iron Contributor
    Dec 28, 2020
    This is strange never had this issue during development or testing. What is your hostpool name?
- schmidtp_duna-drava_hu
  Copper Contributor
  Dec 22, 2020
  TomHickling
  Not sure which one I should choose. 🙂
  - TomHickling
    Microsoft
    Dec 22, 2020
    Try publishing the desktop app group to an ad group rather than user accounts. There was an issue with this previously