Using a desktop and remote application group to granularly control access to MSIX app attach

%3CLINGO-SUB%20id%3D%22lingo-sub-2103561%22%20slang%3D%22en-US%22%3EUsing%20a%20desktop%20and%20remote%20application%20group%20to%20granularly%20control%20access%20to%20MSIX%20app%20attach%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2103561%22%20slang%3D%22en-US%22%3E%3CH1%20id%3D%22toc-hId-1268083091%22%20id%3D%22toc-hId-1268083084%22%3E%3CSTRONG%3EOverview%3C%2FSTRONG%3E%3C%2FH1%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20of%20the%20writing%20of%20this%20article%2C%20Windows%20Virtual%20Desktop%20(WVD)%20supports%20one%20desktop%20application%20group%20(DAG)%20per%20host%20pool.%20This%20means%20that%20all%20users%20granted%20access%20to%20the%20DAG%20with%20MSIX%20app%20attach%20will%20see%20all%20applications.%20For%20example%2C%20if%20both%20Sales%20and%20HR%20users%20need%20a%20remote%20desktop%20but%20we%20must%20not%20allow%20Sales%20users%20to%20access%20HR%20applications%20we%20need%20to%20create%20a%20separate%20host%20pool.%3C%2FP%3E%0A%3CP%3EThis%20document%20provides%20an%20overview%20of%20how%20DAG%20and%20remote%20application%20groups%20(RAG)%20can%20be%20used%20together%20to%20isolate%20applications%20in%20remote%20desktop%20scenarios.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3ENote%3A%20%3C%2FSTRONG%3EThis%20process%20has%20the%20side%20effect%20of%20displaying%20the%20remote%20apps%20in%20the%20user%20feed.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22fig.png%22%20style%3D%22width%3A%20457px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F250009i9D53E15CBA9B1E03%2Fimage-dimensions%2F457x517%3Fv%3D1.0%22%20width%3D%22457%22%20height%3D%22517%22%20role%3D%22button%22%20title%3D%22fig.png%22%20alt%3D%22fig.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3EFigure%201%3A%3C%2FSTRONG%3E%20MSIX%20app%20attaches%20and%20application%20isolation.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId--539371372%22%20id%3D%22toc-hId--539371379%22%3E%3CSTRONG%3ESample%20scenario%3C%2FSTRONG%3E%3C%2FH1%3E%0A%3CP%3ETo%20better%20understand%20MSIX%20app%20attach%20and%20WVD%20capabilities%20we%20will%20follow%20the%20scenario%20below.%3C%2FP%3E%0A%3CP%3EAll%20our%20users%20(Sales%2C%20HR%2C%20and%20Eng)%20must-have%20a%20remote%20desktop.%20They%20all%20need%20access%20to%20Teams%20and%20Edge.%20Sales%20need%20additional%20access%20to%20Whiteboard%20and%20To%20Do.%20HR%20needs%20access%20to%20Power%20Bi.%20Eng%20needs%20access%20to%20Visual%20Studio%20Code%20(VSC).%20We%20cannot%20allow%20users%20to%20have%20access%20to%20apps%20besides%20those%20to%20which%20they%20do%20not%20have%20permission.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CTABLE%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3E%3CSTRONG%3ECommon%20Apps%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3E%3CSTRONG%3ESales%20Apps%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22150%22%3E%3CP%3E%3CSTRONG%3EHR%20Apps%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3E%3CSTRONG%3EEng%20Apps%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3E%3CSTRONG%3ESales%20(Pieter)%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3ETeams%3C%2FP%3E%0A%3CP%3EMicrosoft%20Edge%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3EWhiteboard%3C%2FP%3E%0A%3CP%3EToDo%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3E%3CSTRONG%3EHR%20(Adam)%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3ETeams%3C%2FP%3E%0A%3CP%3EEdge%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3EPower%20Bi%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3E%3CSTRONG%3EEng%20(Stefan)%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3ETeams%3C%2FP%3E%0A%3CP%3EEdge%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22130px%22%3E%3CP%3EVSC%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CH1%20id%3D%22toc-hId-1948141461%22%20id%3D%22toc-hId-1948141454%22%3E%3CSTRONG%3ESetting%20up%20MSIX%20app%20attach%3C%2FSTRONG%3E%3C%2FH1%3E%0A%3CH2%20id%3D%22toc-hId--1656264361%22%20id%3D%22toc-hId--1656264368%22%3ERequirements%3C%2FH2%3E%0A%3CP%3ETo%20complete%20this%20scenario%2C%20we%20must%20have%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EWVD%20deployment%20with%20MSIX%20app%20attach%3C%2FLI%3E%0A%3CLI%3EMSIX%20share%20with%20correct%20permissions%3C%2FLI%3E%0A%3CLI%3EApplication%20dependencies%20are%20included%20in%20the%20master%20image%3C%2FLI%3E%0A%3CLI%3EMSIX%20image%20for%20each%20app%20uploaded%20to%20the%20MSIX%20share%3C%2FLI%3E%0A%3CLI%3EMSIX%20packages%20have%20been%20added%20to%20the%20host%20pool%20and%20are%20set%20to%20active%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH2%20id%3D%22toc-hId-831248472%22%20id%3D%22toc-hId-831248465%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22q.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F249987iBB9A77C9C20CD93B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22q.png%22%20alt%3D%22q.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CH2%20id%3D%22toc-hId--976205991%22%20id%3D%22toc-hId--976205998%22%3EThe%20wrong%20way%3C%2FH2%3E%0A%3CP%3ETo%20complete%20the%20MSIX%20app%20attach%20we%20must%20add%20the%20MSIX%20applications%20to%20a%20DAG%20or%20RAG.%20In%20our%20scenario%2C%20we%20must%20use%20a%20DAG%20and%20not%20RAG.%20If%20we%20assign%20all%20the%20apps%20in%20the%20DAG%20that%20will%20break%20the%20app%20isolation%20requirement.%20%3CEM%3EWe%20cannot%20use%20a%20RAG%20as%20that%20will%20not%20grant%20remote%20desktop%20access.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAll%20MSIX%20applications%20are%20assigned%20to%20a%20DAG.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22stge.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F250010iE067CC345D629481%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22stge.png%22%20alt%3D%22stge.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EUsers%20for%20the%20different%20departments%20assigned%20to%20the%20DAG.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F249982i468BEFB24E48CED6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%222.png%22%20alt%3D%222.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20verify%20this%2C%20we%20can%20log%20in%20as%20Pieter.%20Pieter%20has%20all%20the%20apps%20showing%20in%20his%20Start%20Menu%20(they%20were%20intentionally%20pinned).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22verify.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F250012iD650E7017E11BBA8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22verify.png%22%20alt%3D%22verify.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20can%20see%20that%20this%20was%20not%20what%20our%20scenario%20prescribes%20as%20an%20outcome.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1511306842%22%20id%3D%22toc-hId-1511306835%22%3EThe%20%E2%80%9Cright%E2%80%9D%20way%3C%2FH2%3E%0A%3CP%3EWe%20do%20not%20need%20to%20change%20our%20MSIX%20images%20and%20them%20being%20assigned%20to%20the%20host%20pool.%20We%20need%20to%20change%20our%20DAG%20and%20create%20three%20new%20RAGs%20(Remote%20Application%20Group).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3ENote%3A%20%3C%2FSTRONG%3Ethis%20scenario%20can%20be%20implemented%20only%20if%20the%20users%20are%20fully%20logged%20off%20(session%20disconnected)%20from%20all%20session%20hosts.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20need%20to%20leave%20only%20the%20common%20apps%20Teams%20and%20Edge%20in%20the%20DAG.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22r1.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F250016iFF280B3FE283667D%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22r1.png%22%20alt%3D%22r1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20then%20create%20three%20RAGs%20name%20SalesApps%2C%20HRApps%20and%20EngApps.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22r2.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F250017iCDCCF82613F099C6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22r2.png%22%20alt%3D%22r2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20each%20RAG%20we%20will%20add%20the%20corresponding%20MSIX%20applications%20and%20assign%20the%20corresponding%20users.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3ENote%3A%20%3C%2FSTRONG%3EAll%20users%20must%20remain%20assigned%20to%20the%20DAG.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22e.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F249976iAE3D70BFF2DB8044%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22e.png%22%20alt%3D%22e.png%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22ee.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F249977i286F8D8E17189BFF%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22ee.png%22%20alt%3D%22ee.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3ENote%3A%20%3C%2FSTRONG%3EThe%20Showinwebfeed%20option%20will%20allow%20for%20the%20two%20application%20icons%20to%20be%20suppressed%20however%20this%20is%20not%20enabled%20in%20WVD%20currently.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESalesApps%20RAG%20has%20been%20configured%20as%20per%20our%20scenario.%3C%2FP%3E%0A%3CP%3EWhen%20Sales%20user%20(Pieter)%20signs%20in%20the%20feed%20will%20show%2C%20the%20DAG%20and%20the%20apps%20assigned%20to%20the%20RAG.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22sal.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F249965i9E2158DC68C24C8C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22sal.png%22%20alt%3D%22sal.png%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22sales.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F249966i69211FCC196970A5%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22sales.png%22%20alt%3D%22sales.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--2093098980%22%20id%3D%22toc-hId--2093098987%22%3ESales%20user%20experience%3C%2FH3%3E%0A%3CP%3EWhen%20Sales%20user%20(Pieter)%20signs%20in%20the%20feed%20will%20look%20like%20this.%3C%2FP%3E%0A%3CDIV%20id%3D%22tinyMceEditorStefan%20Georgiev_12%22%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22123.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F250018iB06AC98B09A68BAC%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22123.png%22%20alt%3D%22123.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20remote%20desktop%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ESame%20host%20pool%3C%2FLI%3E%0A%3CLI%3EEdge%2C%20Teams%2C%20Whiteboard%2C%20and%20Todo%20are%20available%3C%2FLI%3E%0A%3CLI%3EVSCode%20is%20not%20available%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH3%20id%3D%22toc-hId-394413853%22%20id%3D%22toc-hId-394413846%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22z.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F249971iEC77AF4F338484DD%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22z.png%22%20alt%3D%22z.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FH3%3E%0A%3CH3%20id%3D%22toc-hId--1413040610%22%20id%3D%22toc-hId--1413040617%22%3EEng%20user%20experience%3C%2FH3%3E%0A%3CP%3E%3CSTRONG%3ENote%3A%20%3C%2FSTRONG%3EIf%20users%20have%20not%20been%20logged%20off%20during%20the%20reassignment%20of%20application%20to%20app%20groups%20please%20make%20sure%20to%20fully%20log%20off%20(session%20disconnected)%20users%20from%20all%20session%20hosts.%3C%2FP%3E%0A%3CP%3EWhen%20Eng%20user%20(Stefan)%20signs%20in%20their%20feed%20shows.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22eng.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F249970i4641093877C7CE61%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22eng.png%22%20alt%3D%22eng.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EOn%20remote%20desktop%20they%20can%20see%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ESame%20host%20pool%3C%2FLI%3E%0A%3CLI%3EEdge%2C%20Teams%2C%20and%20VS%20(Visual%20Studio)%20code%20are%20available.%3C%2FLI%3E%0A%3CLI%3EWhiteboard%20is%20not%20available%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CUL%3E%0A%3CLI%3EAll%20three%20apps%20are%20running%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22333.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F249958iCB3B0848F5AEA9C6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22333.png%22%20alt%3D%22333.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-379308744%22%20id%3D%22toc-hId-379308737%22%3EView%20from%20session%20host%20as%20admin%3C%2FH3%3E%0A%3CP%3EWhen%20we%20access%20the%20session%20host%20virtual%20machine%20directly%2C%20we%20can%20see%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3Ewhen%20Sales%20user%20(Pieter)%20and%20Eng%20user%20(Stefan)%20sign%20they%20intentionally%20end%20up%20on%20the%20same%20machine.%3C%2FLI%3E%0A%3CLI%3EHostname%3C%2FLI%3E%0A%3CLI%3EAll%20mounted%20Virtual%20Hard%20Disks%20(VHDs)%20part%20in%20Disk%20Management%3C%2FLI%3E%0A%3CLI%3ESee%20staged%20packages%20on%20the%20machine%20using%20%3CSTRONG%3EGet-AppxPacakge%20*%3CPACKAGENAME%3E*%20-AllUsers%3C%2FPACKAGENAME%3E%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3ENote%3C%2FSTRONG%3E%3A%20the%20switch%20-%3CSTRONG%3EAllUsers%20%3C%2FSTRONG%3Eindicates%20that%20the%20package%20is%20staged%20for%20all%20users%20on%20the%20machine%2C%20but%20only%20those%20users%20that%20have%20it%20registered%20can%20use%2Fsee%20it.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22123.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F249956i96A7971EA9E7553A%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22123.png%22%20alt%3D%22123.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CDIV%20id%3D%22tinyMceEditorStefan%20Georgiev_17%22%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Overview

 

As of the writing of this article, Windows Virtual Desktop (WVD) supports one desktop application group (DAG) per host pool. This means that all users granted access to the DAG with MSIX app attach will see all applications. For example, if both Sales and HR users need a remote desktop but we must not allow Sales users to access HR applications we need to create a separate host pool.

This document provides an overview of how DAG and remote application groups (RAG) can be used together to isolate applications in remote desktop scenarios.

 

Note: This process has the side effect of displaying the remote apps in the user feed.

 

fig.png

Figure 1: MSIX app attaches and application isolation.

 

Sample scenario

To better understand MSIX app attach and WVD capabilities we will follow the scenario below.

All our users (Sales, HR, and Eng) must-have a remote desktop. They all need access to Teams and Edge. Sales need additional access to Whiteboard and To Do. HR needs access to Power Bi. Eng needs access to Visual Studio Code (VSC). We cannot allow users to have access to apps besides those to which they do not have permission.

 

 

Common Apps

Sales Apps

HR Apps

Eng Apps

Sales (Pieter)

Teams

Microsoft Edge

Whiteboard

ToDo

 

 

HR (Adam)

Teams

Edge

 

Power Bi

 

Eng (Stefan)

Teams

Edge

 

 

VSC

Setting up MSIX app attach

Requirements

To complete this scenario, we must have:

  • WVD deployment with MSIX app attach
  • MSIX share with correct permissions
  • Application dependencies are included in the master image
  • MSIX image for each app uploaded to the MSIX share
  • MSIX packages have been added to the host pool and are set to active

q.png

The wrong way

To complete the MSIX app attach we must add the MSIX applications to a DAG or RAG. In our scenario, we must use a DAG and not RAG. If we assign all the apps in the DAG that will break the app isolation requirement. We cannot use a RAG as that will not grant remote desktop access.

 

All MSIX applications are assigned to a DAG.

 

stge.png

 

Users for the different departments assigned to the DAG.

 

2.png

 

To verify this, we can log in as Pieter. Pieter has all the apps showing in his Start Menu (they were intentionally pinned).

 

verify.png

 

We can see that this was not what our scenario prescribes as an outcome.

The “right” way

We do not need to change our MSIX images and them being assigned to the host pool. We need to change our DAG and create three new RAGs (Remote Application Group).

 

Note: this scenario can be implemented only if the users are fully logged off (session disconnected) from all session hosts.

 

We need to leave only the common apps Teams and Edge in the DAG.

 

r1.png

 

We then create three RAGs name SalesApps, HRApps and EngApps.

 

r2.png

 

For each RAG we will add the corresponding MSIX applications and assign the corresponding users.

 

Note: All users must remain assigned to the DAG.

 

e.pngee.png

 

Note: The Showinwebfeed option will allow for the two application icons to be suppressed however this is not enabled in WVD currently.

 

SalesApps RAG has been configured as per our scenario.

When Sales user (Pieter) signs in the feed will show, the DAG and the apps assigned to the RAG.

 

sal.pngsales.png

Sales user experience

When Sales user (Pieter) signs in the feed will look like this.

 

123.png

 

In remote desktop:

  • Same host pool
  • Edge, Teams, Whiteboard, and Todo are available
  • VSCode is not available

z.png

Eng user experience

Note: If users have not been logged off during the reassignment of application to app groups please make sure to fully log off (session disconnected) users from all session hosts.

When Eng user (Stefan) signs in their feed shows.

eng.png

On remote desktop they can see:

  • Same host pool
  • Edge, Teams, and VS (Visual Studio) code are available.
  • Whiteboard is not available
  • All three apps are running

333.png

View from session host as admin

When we access the session host virtual machine directly, we can see:

  • when Sales user (Pieter) and Eng user (Stefan) sign they intentionally end up on the same machine.
  • Hostname
  • All mounted Virtual Hard Disks (VHDs) part in Disk Management
  • See staged packages on the machine using Get-AppxPacakge *<packageName>* -AllUsers

 

Note: the switch -AllUsers indicates that the package is staged for all users on the machine, but only those users that have it registered can use/see it.

 

123.png

 

 

 



0 Replies