Forum Discussion
MSIX app attach Azure portal integration public preview
MicheleVigilante , @elliottchandler and @schmidtp_duna-drava_hu, there are at least three other people reporting the same issue where you see this VHD mounting and after a while the dismounting from the logs.
I was lucky and at first I actually was able to have both MSIX using RemoteApp and MSIX using desktop publishing working for a short while but then something happened and assigned MSIX remoteapps vanished leaving only apps published from Start Menu.
Because everything worked fine for a short time there is no issue with any of below listed which I have offcourse also triple checked:
1) permissions (able to mount from share and computer account is able to access the share. Also in the logs "MSIX packages has been properly staged".
2) bad vhd (issue happens both with your provided vhds and own vhds where both work fine using scripts)
3) wrong version of agent and bootloader (My Session host WVD agent version is 1.0.2743.1300)
4) package is not active (Package is set to Active)
StephanK during a deployment last week of the new year a switch was flipped that blocked MSIX app attach. We flipped it back and all impacted host pools are working.
App attach is now working. But how can we now assign the apps in the desktop sessions to individual users/groups in a differentiated way?
- TomHickling
Microsoft
If you unpublish the apps from the Desktop App Group, and then create multiple RemoteApp Groups in the host pool. Then assign the specific apps and users to each of the RemoteApp groups, this will achieve the differentiation
I can confirm it is working now for me as well. 🙂
