Forum Widgets
Latest Discussions
FSLogix FontSmoothing Issue
I'm running into an issue where I can't get the fontsmoothing option to stay on when running FSLogix. If I stop both FSLogix services on the golden image of the VM then it stays but once I turn the FSLogix services back on that setting is reverted back. Anyone else run into this issue or have a solution?
Profile Containers GPO Managed Settings
I am sure this must have been raised before, but are there any plans to make the GPO settings for FSLogix Profile Containers managed settings? I have had to troubleshoot multiple environments where previous admins have removed settings, not realising that this doesn't remove the values from the registry.
Failed to attach VHD (The semaphore timeout period has expired) on 3 out of 5 RDS servers
Hi, We have 5 RDS 2019 servers in a farm and 3 of them are having this timeout issue. The servers are on the same network, accessing the same file share. Having the same Microsoft updates, Same policies. FSLogix profile type 3. Equally load balanced. Tried upgrading FSLogix to latest version (2010 Hotfix2). Still some users that are landing on these specific 3 servers are having this issue. When they keep the failing session open and start a new one they can successfully logon to the farm. Not sure but we think all users are occasionally affected. The first complaints from users started first half august. Any ideas how to troubleshoot this issue?
Citrix Profile Migrated to FsLogix - Disk Compaction fails - Ran out of time and bypassed operation
We have used David Otts script to migrate Citrix UPM profiles across to FsLogix and this is working great, with profiles now operating in a VHDx container. We have enabled Disk Compaction via FsLogix group policy, however this does not seem to run at all. To test, we had a profile that had 5GB of data, being able to expand to a maximum of 50GB. Copied 10Gb of files into the profile then deleted them and logged out, leaving the disk expanded at ~15GB. I Looking at logs, the error is Disk was not compacted, Reason: Ran out of time and bypassed remaining operation Am i missing something here? I couldn't find much on this error, but the log out process takes ~ 10 seconds and im unsure why it thinks it ran out of time. EDIT: we are using FsLogix v2.9.8884.27471
Azure VDI - Outlook Stuck on 'Loading Profile'
Issue occurs every morning and we have been chasing this up with the Microsoft support team as well. We've tried a lot of things but switching to and from VDI's seems to eventually get people logged in. We've rebuilt mail profiles, safe mode, resetnavpane, disabled add-ins, updating Office, restarted VDIs, deleted duplicate user profiles on the VDI, deleted OSTs and temp files within AppData, cleared credential manager. One thing which seemed to help was running Microsoft SaRA. It said we had modern authentication setup on our tenant and the VDIs were using legacy. It performed the fix and sorted the issue right away. It looked to calm the problem for some time but more people started getting this again. Something to note is this usually happens in the mornings or just when someone starts work. I know a lot of people experience the same issue but not come across a reliable fix so far.
FSLogix - Search issues
Hello, Does anyone know what happens when an FSL server reboots when there are current connections using the containers? I'm beginning to suspect that this is what's causing search issues. I've been testing logging off vmware sessions while the server is online and it picks up the index as 'complete'. I'm noticing after the reboot, for anyone that had a session running, it resets the index back to 0 and has to rebuild it from scratch. I currently have a single windows server (ntfs) for ODFC (no profile) containers.
FSLogix not compacting VHDX
Hi Wondering if someone can tell me what I am doing wrong/not understanding? My understanding is that a VHDX is compacted if: The VHDX is over 1GB There is 20% whitespace free You are using type 0, nothing else Right? So what am I missing, why does FSLogix think that compaction should not be run on this VHDX? Log says: Disk size results: WasCompacted:false, MaxSupportedSize: 31456214528, MinSupportedSize: 591281664, SizeOnDisk (Before: 1212153856 - After: 1212153856), Space Saved: 0, Compaction took: 235 Disk was not compacted, Reason:Not enough recoverable space for compaction. Looking at the content of the VHDX, there is around 495MB of data in the container. The log above shows min size is 591MB, so almost 100MB more than the actual data, but ok... The current size is 1212MB, which is over 1024MB/1GB. Tick! So we should be able to free up 621MB, which is more than 20%, its 50%. Tick! So why no compaction? I havemanuallycompacted the VHDX and it is now 612MB... I need to understand why it thinks it shouldn't compact the VHDX because I have a few other containers that are similar. Thanks!
VHD Compact Disk - Deleting whole profile
"Disk was compacted: true. Logoff time increased by 34375 milliseconds. Disk size reduced by 81792 MB. (VHDPath: \\*.file.core.windows.net\fslogix\profiles\*.VHDX)" Not sure why this is happening, Just wipes the entire profile during the compaction process, No obvious cause
