Application Processes remain open on Multi-Session Workstation after closing App

%3CLINGO-SUB%20id%3D%22lingo-sub-2824118%22%20slang%3D%22en-US%22%3EApplication%20Processes%20remain%20open%20on%20Multi-Session%20Workstation%20after%20closing%20App%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2824118%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20setup%20FSLogix%20profiles%20for%20our%20client%E2%80%99s%20AVD%20Environment.%26nbsp%3B%20We%20are%20using%20Azure%20storage%20to%20store%20the%20profile%20disks.%26nbsp%3B%20We%20have%20found%20an%20issue%20when%20users%20connect%20to%20the%20multi-session%20workstations.%26nbsp%3B%20Every%20time%20a%20user%20opens%20an%20application%20such%20as%20Microsoft%20Word%20%2F%20Excel%20%2F%20Google%20Chrome.%26nbsp%3B%20The%20process%20remains%20in%20the%20background%20even%20after%20the%20user%20has%20closed%20out%20word.%26nbsp%3B%20These%20processes%20cannot%20be%20killed%20by%20an%20administrator%20and%20the%20machine%20requires%20a%20reboot%20to%20get%20rid%20of%20them.%26nbsp%3B%20Has%20anyone%20else%20come%20across%20this%20scenario%3F%26nbsp%3B%20(32%20Bit%20Office%202019%20%2F%20Chrome%20manually%20installed%20on%20workstation%20image).%3C%2FP%3E%3CP%3EWe%20ran%20a%20Proof%20of%20Concept%20storing%20the%20FSLogix%20profiles%20on%20an%20Azure%20created%20file%20server%20(rather%20than%20Azure%20Files)%20and%20we%20did%20not%20have%20this%20issue.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2827165%22%20slang%3D%22en-US%22%3ERe%3A%20Application%20Processes%20remain%20open%20on%20Multi-Session%20Workstation%20after%20closing%20App%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2827165%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F399672%22%20target%3D%22_blank%22%3E%40Jeff_Paulsen%3C%2FA%3E%26nbsp%3BIssue%20appears%20to%20be%20tied%20to%20the%20use%20of%20the%20Office%20Container%20in%20FSLOGIX.%26nbsp%3B%20Using%20just%20the%20Profile%20container%20appears%20to%20resolve%20the%20issue.%26nbsp%3B%20Looking%20for%20best%20practices%20guide%20for%20implementing%20AVD%20%2F%20Multisession%20W10%20%2F%20FSLOGIX%20%2F%20Profile%20Container%20%2F%20Office%20Container%20%2F%20Search%20indexing.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

We have setup FSLogix profiles for our client’s AVD Environment.  We are using Azure storage to store the profile disks.  We have found an issue when users connect to the multi-session workstations.  Every time a user opens an application such as Microsoft Word / Excel / Google Chrome.  The process remains in the background even after the user has closed out word.  These processes cannot be killed by an administrator and the machine requires a reboot to get rid of them.  Has anyone else come across this scenario?  (32 Bit Office 2019 / Chrome manually installed on workstation image).

We ran a Proof of Concept storing the FSLogix profiles on an Azure created file server (rather than Azure Files) and we did not have this issue.  

2 Replies

@Jeff_Paulsen Issue appears to be tied to the use of the Office Container in FSLOGIX.  Using just the Profile container appears to resolve the issue.  Looking for best practices guide for implementing AVD / Multisession W10 / FSLOGIX / Profile Container / Office Container / Search indexing.

This issue may have been caused by the M365 Office Activation being set to "Per User" rather than "Shared Computer" in the W10 Multi-Session environment. (Eliminating the Office Container in FSLOGIX eventually produced the same issues)