FSLogix - 48v35 error at Microsoft login prompt in AVD
I'm resposting from this thread to hopefully create more attention for this problem: https://answers.microsoft.com/en-us/outlook_com/forum/outlk_win-outtop_new-outsub_ofb/outlook-error-message-somehting-went-wrong-48v35/97d7ff71-8a58-40c8-8726-adf3d1f095b8 Me and other admins (from reposted thread) have specific users who experience M365 authentication problems after upgrading to the latest FSLogix version(s) that offers support for New Teams. The error occurs in the Azure Virtual Desktop environment, when a user tries to open a Microsoft application (Outlook, OneDrive etc.). Not all users have the problem that they need to reauthenticate, or can't authenticate at all, with the 48v35 error. The users who do however, repeatedly get the same error after a few days or a week. We tried multiple things, like removing the Microsoft.AADBrokerPlugin directory or creating a completely new FSLogix profile, but the problem stays for these users. In my case I am using the FSLogix setting RoamIdentity=1. Is there any news from FSLogix on this issue? Or does anyone have workarounds to share? I would like to update more customer environments to use the New Teams, but with these issues I would rather wait.
FSLogix - Automatically fix RW.vhdx corruption
When the RW.vhdx is corrupt, the user ends up with an read only profile. Manual intervention is required to remove the RW file which can't be merged into the base profile to restore R/W access to the profile. The following error is logged in the event viewer: "Open vDisk Failed, file:<path to RW.vhdx> (The chain of virtual hard disks is corrupted) There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk." Feature Request: Automatically remove a corrupt RW file when detected. As it can't be recovered anyway, deleting the corrupt file will at least restore functionality (R/W access to profile).
Bug with profile picture on AVD / Windows 11 Multi-User
My organization has seen multiple occurrences where a different user's profile picture/icon is shown besides their own. This has been seen in the OS under Start (lower left corner) as well as in Settings -> Accounts. No issues have been seen with Teams or Outlook only the profile picture shown within the OS. Have not seen anything similar with our on-premise Citrix machines. Not a high priority issue obviously but would like to raise awareness. If anyone has ideas, please let me know what information I can gather to start troubleshooting! Thank you.FSLogix - Option to change path C:\Users\local_%username% to another disk
I'd like to improve user profile performance with FSLogix on Azure by optionally moving the C:\Users\local_%username% folder (used for redirections.xml) to the temp 😧 drive on Azure VMs with a temp disk. e.g. D:\Users\local_%username% I'm not referring to the C:\Users\%username% but the C:\Users\local_%username% folders. Currently this isn't configurable but it's referenced at HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Profiles\Sessions\[SID]\LocalProfilePath This would offload IOPs from the OS disk and also make some user profile operations much faster, e.g. Teams cache could be redirected and offloaded to speed up Teams. The temp disk is generally much more performant than Azure Premium disks. It also sorts the issue of those local_%username% folders not getting cleaned up after an unexpected reboot/crash. If they're on the temp disk they'll get wiped out after a reprovision instead of having to script the cleanup. Cloud Cache paths can be customised to use the 😧 drive but it would be nice to move the redirections to that too. Regards, DavidFSLogix - Add the ability to exclude specific files from ODFC containers
The ability to exclude specific files/directories from ODFC containers like we can with Profile containers. We’ve discovered some pretty severe bloat occurring (specifically the issue with %APPDATA%\Microsoft\Teams\Service Worker\Cache Storage) and the ability to exclude that from the ODFC container would save a huge amount of disk space when multiplied by our thousands of users.FSLogix - Set Outlook cached mode to specific number of days if the profile fails to attach
Add ability to set Outlook cache to a specific number of days if the profile fails to attach. Currently, FSLogix can set Outlook to online mode if the VHDx container fails to attach to the session. A new registry key to allow FSLogix set the sync period in Outlook and keep Outlook in cached mode. Right now we use the “Set Outlook cached mode on successful attach” but this is a simple on/off and in some of our sites Outlook is too slow when running in online only mode, it would be nice to be able to set the cache to 30/60/90 days or whatever on successful attach but leave the fallback position to be something like 3 days.
