Forum Discussion
Stefan Georgiev
Microsoft
MicrosoftMSIX 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...
Hey DBR14,
no, that’s exactly the problem with msix 😞
I would guess that the success rate of repackaging into msix is around 50%, maybe 60%?!?! 😞
That’s why nearly all of my customers where I have done a POC stepped back to SCCM or similar 😞
But...maybe I‘m wrong 😉
no, that’s exactly the problem with msix 😞
I would guess that the success rate of repackaging into msix is around 50%, maybe 60%?!?! 😞
That’s why nearly all of my customers where I have done a POC stepped back to SCCM or similar 😞
But...maybe I‘m wrong 😉
Stefan Georgiev and TomHickling
can you please tell me what agent version is needed for msix app attach in the portal?
background for this question: I have a customer who is whitelisted since January, but had huuuge problems with agent version 2848, every single session hosts was in state "Needs assistance"
we turned off the validation environment, so the agent went back to 2800, and ALL session hosts went green and were available *TOP*
But...next problem...we went through the portal and attached a few msix packages, but none of them were available for a user 😞
is it because we are on 2800, or because we turned off the VE?
thanks guys
can you please tell me what agent version is needed for msix app attach in the portal?
background for this question: I have a customer who is whitelisted since January, but had huuuge problems with agent version 2848, every single session hosts was in state "Needs assistance"
we turned off the validation environment, so the agent went back to 2800, and ALL session hosts went green and were available *TOP*
But...next problem...we went through the portal and attached a few msix packages, but none of them were available for a user 😞
is it because we are on 2800, or because we turned off the VE?
thanks guys
Stefan GeorgievJochen Berners its not just about the agent version. 1 host must in in validation environment (as even the right agent version) in non-validation will not work. right now the version for agent is anything pas 2800.
- I would put them in VE and then remove all the app packages from your MSIX portal and DAG and then reboot the SessionHost OR just restart the Bootloader & Agent service and see if it fixes it. Could do it one by one and restart the services and see if it works. I was fighting the unavailable issue for a few weeks because of a stupid bad package.
Could also try removing the SH from the HostPool by removing the WVD Agent/Bootloader AGent/Geneva Agent and SxS module. Then reinstall the bootloader and wvd agent with a new valid registration key and bring them back into the Pool.- Thanks @DRB14 for the reply, but unfortunately we have done that, without success. That was the reason why we went back to turn off the VE. It also doesn't depend on attaching a package or not, the SH went "Needs assistance" a few minutes after turning on the VE and get the newest agent (I think it was 2848 or so-...)
- Have you looked at this doc and checked if any of the errors seen in EV align? https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-agent#step-2-remove-the-session-host-from-the-host-pool
