MSIX RemoteApp Possible rights issue

%3CLINGO-SUB%20id%3D%22lingo-sub-1767716%22%20slang%3D%22en-US%22%3EMSIX%20RemoteApp%20Possible%20rights%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1767716%22%20slang%3D%22en-US%22%3E%3CP%3EFollowed%20a%20few%20guides%20to%20stage%20and%20register%20apps%20from%20a%20network%20share%20everything%20works%20perfectly%20within%20the%20WVD%20host%20as%20remote%20desktop%20user%20can%20launch%20the%20app%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20try%20to%20add%20the%20app%20to%20Remote%20applications%20the%20guides%20suggest%20creating%20a%20lnk%20shortcut%20which%20would%20link%20to%20a%20path%2C%20you%20then%20put%20the%20lnk%20shortcut%20in%26nbsp%3B%20c%3A%5Cprogramdata%5Cmicrosoft%5Cwindows%5CStart%20Menu%5CPrograms%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ei.e%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20shortcut%20to%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3BC%3A%5CProgram%20Files%5CWindowsApps%5CVLCplayer_3.0.11.0_x64__6kpxaaedanasr%5CVFS%5CProgramFilesX64%5CVideoLAN%5CVLC%5Cvlc.exe%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20where%20I%20get%20the%20problem%20with%20Remote%20Apps%2C%20I%20can%20only%20launch%20this%20from%20an%20admin%20account%20%2F%20normal%20accounts%20will%20not%20launch%20this%20app%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20sure%20if%20this%20is%20normal%20but%20I%20notice%20from%20powershell%2C%20again%20I%20can%20browse%20to%20that%20path%20and%20launch%20the%20exe%20from%20and%20admin%20account%26nbsp%3B%20%26nbsp%3Bbut%20not%20from%20a%20standard%20user%20account.%3C%2FP%3E%3CP%3Eone%20thing%20I%20did%20notice%20is%20from%20that%20path%20I%20can%20launch%20a%20txt%20file%20or%20some%20other%20file%20formats%20but%20not%20exe's%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1768685%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20RemoteApp%20Possible%20rights%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1768685%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F827482%22%20target%3D%22_blank%22%3E%40timmybeer%3C%2FA%3E%26nbsp%3B%20Ive%20answered%20my%20own%20question%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESeems%20to%20be%20the%20ApplyACL%20part%20of%20msixmgr%26nbsp%3B%20that%20creates%20bad%20ACLs%20for%20the%20folder%3C%2FP%3E%3CP%3EI'll%20write%20up%20a%20blog%20post%20about%20it%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Followed a few guides to stage and register apps from a network share everything works perfectly within the WVD host as remote desktop user can launch the app etc.

 

If I try to add the app to Remote applications the guides suggest creating a lnk shortcut which would link to a path, you then put the lnk shortcut in  c:\programdata\microsoft\windows\Start Menu\Programs 

 

i.e 

 

A shortcut to

 

 C:\Program Files\WindowsApps\VLCplayer_3.0.11.0_x64__6kpxaaedanasr\VFS\ProgramFilesX64\VideoLAN\VLC\vlc.exe

 

This is where I get the problem with Remote Apps, I can only launch this from an admin account / normal accounts will not launch this app

 

Not sure if this is normal but I notice from powershell, again I can browse to that path and launch the exe from and admin account   but not from a standard user account.

one thing I did notice is from that path I can launch a txt file or some other file formats but not exe's

 

 

1 Reply
Highlighted

@timmybeer  Ive answered my own question

 

Seems to be the ApplyACL part of msixmgr  that creates bad ACLs for the folder

I'll write up a blog post about it