Teams not working in Windows 11 AVD + FSLogix
I am currently setting up and testing a Windows 11 AVD environment for future use, but I am having trouble with getting Teams to work properly. When a user logs in for the first time I am able to log into Teams. When keeping it open for a couple of minutes the client will start having problems, like crashing, restarting, staying on the "Waiting on Teams" screen or just showing a full white Teams application window. When signing off from the AVD Session Host and signing in again Teams is not working either anymore. I have found out that Teams appears to be working fine when I exclude the user profile from using FSLogix.This is not a solution however. The problem seems very similair toTeams for Vdi & Fslogix - Microsoft Q&A, unfortunately the mentioned registry key is already present. Further information about the current setup: Image: Windows 11 Enterprise multi session Applied VDOT:GitHub - The-Virtual-Desktop-Team/Virtual-Desktop-Optimization-Tool: The script and configuration files in this repository provide an easy method to customize and apply performance related settings to virtual desktop environments. FSLogix: tested with versions 2105 and 2015 HF_01 Teams: Latest version installed with ALLUSER=1 and in combination with AVD Optimisations (WebRTC) I am very curious if anyone else has experienced problems like this.
Assigning permissions when using Azure Files for FSLogix Profiles in WVD
My goal is to use a share in Azure Files to house the FSLogix profiles for users in a Windows Virtual Desktop (WVD) environment that is part of an Azure Active Directory Domain Services (AADDS) domain. I am following instructions athttps://docs.microsoft.com/en-us/azure/virtual-desktop/create-profile-container-adds. There are two places to set permissions to the fileshare -- within the Azure portal and at the virtual machine level. In the Azure portal, you assign permissions to an Azure AD identity. At the VM level, you assign permissions to an Active Directory object that exists within the AADDS domain. If you want to assign these permissions at theuserlevel, there doesn't seem to be a problem. But I want to assign permissions at agrouplevel, and I'm getting stuck. As far as I can tell, in the Azure portal you can only assign permissions to Security groups, not to Microsoft 365 groups. (When I go to the Role Assignments page and click Add, my Microsoft 365 groups do not appear.) But at the VM/domain level, you can only assign permissions to objects with an email address. Microsoft 365 groups have an e-mail address, but Security groups in Azure do not. Does this mean we have to maintain two groups for each set of WVD users with FSLogix profiles -- a matching pair of M365 and Security groups with the same membership?Announcing FSLogix 2201 hotfix 1 (2.9.8171.14983) has been released!
FSLogix Release Notes - FSLogix | Microsoft Docs Summary This update for FSLogix 2201 includes fixes to Cloud Cache and container redirection processes. No new features are included with this update. Changes IMPORTANT This is a **hotfix** for FSLogix 2201 (2.9.8111.53415). If you are using Cloud Cache or have experienced intermittent system crashes as a result of FSLogix, it is recommended to install this update. Resolved an issue with Cloud Cache where disk read / write blocking could potentially create a deadlock to the disk and cause the Virtual Machine to become unresponsive. Resolved an issue that would cause a Virtual Machine to crash while removing profile redirections during the sign out process. File Information Download the following package:Download FSLogix 2201 hotfix 1 (2.9.8171.14983)Announcing FSLogix 2201 hotfix 2 (2.9.8228.50276) has been released!
FSLogix Release Notes - FSLogix | Microsoft Docs Summary This update for FSLogix 2201 includes fixes to multi-session VHD mounting, Cloud Cache meta tracking files, and registry cleanup operations. Changes IMPORTANT This is a hotfixfor FSLogix 2201 (2.9.8111.53415) and includes all previous changes from v2201 hotfix 1 (2.9.8171.14983). It is recommended all customers update to this version. Resolved an issue that would cause a system crash while reading from meta tracking files in a Cloud Cache configuration. Resolved an issue where a logon would succeed even if when the disk failed to attach. Most commonly occurs in multi-session environments. Resolved an issue during profile cleanup where user registry hives would be removed regardless of the FSLogix local group exclusions. File Information Download the following package:Download FSLogix 2201 hotfix 2 (2.9.8228.50276)
User disconnects, signs back in and does not get their FSLogix profile
Hey everyone, I have an AVD environment with an FSLogix Azure file share joined to the domain. Sometimes users will just close their RDP session, putting their profile into a disconnected state. When they log back in, it does not give them their session back and locks their profile. This has been a huge headache - is this a known issue in AVD? I can enable multi-session writeback but I feel like that's a work around. I know there's a possible fix in the FSLogix preview but what is your experience with it?WVD + FSLogix (Azure Files) with 8 x D8S-v3 for 340 users - Major performance issues
Hello, We have this week gone live with a 340 user WVD with FSLogix deployment in Azure on8 x D8S-v3 size servers.We are having performance issues which we're not able to get to the bottom of. Server performance looks like it is OK via Azure Portal. Only thing that does look slightly high isNetwork,however, I'm not certain this this is the issue. Behaviour Users are logging in for the first - waiting a long time for the FSLogix profile to be created and hang on the Windows start until it is completed. Users who do have a profile are having sluggish behaviour, i.e. clicking on start the menu takes some time to open and opening an app seems to hang for a while then the app opens Users greeted by a black screen upon first creation of their profile, nothing changes, we need to delete the virtual Disk from the FSLogix storage pool. So they can signin again for it to create the profile. Outlook and OneDrive are taking a awful long time to set up. During testing about 2 weeks ago, we didn't have a single issue. However, I am not sure with Microsoft's networks being hammered is this perhaps related to performance of the servers (network any way) Or, it being +/- 280-300 users logging in causing the issues. Or, network throughput some how needs to be increased. We've raised a Critical support case as the project engineers and service desk are being hammered. However, our 2 hour SLA has not been met and still 5 hours later, nothing. I assume due to the increase in demand given the current situation of home isolation. Thank you for reading through this and welcome any feedback/guidance. Adam
FSLogix Profile Issues
All, Hoping someone here can help out with FSLogix issue. Environment = 250 + users, using Citrix Provisioning MCS, Single Session Windows 10 VDI (Windows 10 Version 1909) with FSLogix Version 2004 (2.9.7349.30108) being the profile manager. Below are the FSLogix GPO settings applied to Windows 10 Golden image, which then gets deployed to 250+ VDI. Policy definitions (ADMX files) retrieved from the central store.FSLogix Policy Setting Comment Days to keep log files Enabled Days to keep log files 14 Policy Setting Comment Enable logging Enabled All logs enabled Policy Setting Comment Enable logging: Profiles Enabled Policy Setting Comment Enable search roaming Enabled Single-user search Policy Setting Comment Path to logging files Enabled Path to logging files (\\local share host server 2016 server) FSLogix/Profile Containers Policy Setting Comment Dynamic VHD(X) allocation Enabled Policy Setting Comment Enabled Enabled Policy Setting Comment Profile type Enabled Normal direct-access profile Policy Setting Comment Set Outlook cached mode on successful container attach Enabled Policy Setting Comment Size in MBs Enabled Size in MBs 20000 Policy Setting Comment Store search database in profile container Enabled Single-user search Policy Setting Comment VHD location Enabled VHD location (\\localshare\%Username%) Policy Setting Comment Remove Orphaned OST Files On Logoff Enabled Policy Setting Comment VHDX sector size Enabled 512 bytes Policy Setting Comment Volume re-attach retry count Enabled Volume re-attach retry count 2 FSLogix/Profile Containers/Container and Directory Naming Policy Setting Comment Virtual disk type Enabled VHDX Issue: VHDX profile gets DISCONNECTED at exactly 10 Hours mark. Since the user profile is mounted to Windows 10 VDI upon log on, when the VHDX profile is disconnected, everything stops working. By everything i meant access to File explorer and all Applications stops and the VDI becomes completely unresponsive. If there were unsaved files, these would be lost. The only way to get around this is by getting user to sign out of the affected VDI. Start Menu and Task Manager remains functional, so users can click start and sign out. When they sign out, the VDI is automatically restarted and placed back to the VDI pool (Citrix MCS). When the same user starts another new session, they are assigned a new Windows 10 VDI and the countdown begins once again. On the server that is hosting VHDX, we can see sessions getting dropped as soon as they hit 10 hours. We narrowed down the issue by setting up a new Citrix UPM machine catalog, No FSlogix and the issue where profile gets disconnected after 10 hours does not occur. We have tried the following: • Able to replicate the issue with or without having any workload on VDI and by multiple users • Removed the last installed MS patch (November 10, 2020—KB4586786. This KB had some Kerberos ticket issues, which we suspect to be the root cause especially on FSlogix Profile environment, but then again no prove, other than Microsoft acknowledgement of Kerberos issue on KB4586786. We have not yet applied the December patch but we rollback to previous month snapshot, but the issue persists. • Stopped the Windows Search Service before the 10 hours mark as this one of the Service that stop as soon as the issue occurs • Restart Windows Search Service just before the 10 hours mark • Stopped Outlook Indexing We’re contemplating on whether to upgrade to FSlogix Version 2009, but we’re not sure if this would fix the issue. Please advise if you’ve come across this or similar FSLogix issue in the past. Thank you for your help in advance. Gonzalo_Reynaany suggestions please?
Windows Server 2022 and FSLogix profile roaming problems
Hello! Recently I've been tasked with enabling profile roaming between two Windows Server 2022 hosts, which are added to the same collection. Both of them are hosting internal developed app. After enabling fslogix on one of them, I've encountered some errors, users getting blocked from logging in. Those are the errors users are getting when trying to log in into the host that uses FSlogix: 1) Failed to acquire mutex for user: EXAMPLE-USER 2)Failed to acquired cleanup session registry lock for user EXAMPLE-USER (SID=S-1-5-21-1715567821-2139871995-725345543-32785) (Elapsed time: 60000) (The wait operation timed out.) User is from different domain that has Forest trust type set to Transitive. We have multiple domains accessing this VM and users from all of them are having the same problems when fslogix enabled on it. User has access to both VM and Azure Storage Account File share when profiles are being saved (both SMB and on Azure portal access) FSLogix policy is set like this: Policy Setting Comment Delete local profile when FSLogix Profile should apply Enabled Policy Enabled Enabled Policy Setting Comment Set Outlook cached mode on successful container attach Disabled Size in MBs Enabled Size in MBs 10000 Policy Setting Comment VHD location Enabled VHD location \\<example>.file.core.windows.net\profiles FSLogix/Profile Containers/Advancedhide Policy Setting Comment Keep local folder after user logs out Disabled Locked VHD retry count Enabled Locked VHD retry count 3 Policy Setting Comment Locked VHD retry interval Enabled Locked VHD retry interval 5 Policy Setting Comment Prevent login with failure Enabled Policy Setting Comment Prevent login with temporary profile Enabled Policy Setting Comment Redirect temporary file folders to local computer Enabled Redirect TEMP, TMP and INetCache to local drive Policy Setting Comment Remove Orphaned OST Files On Logoff Enabled FSLogix/Profile Containers/Container and Directory Naminghide Policy Setting Comment Swap directory name components Enabled Policy Setting Comment Virtual disk type Enabled VHDX Any ideas how to solve it or what might have caused it?
