Few suggestions which I did in my environment hope that helps
.Antivirus Exclusions for FSLogix
Exclude files:
%ProgramFiles%\FSLogix\Apps\frxdrv.sys
%ProgramFiles%\FSLogix\Apps\frxdrvvt.sys
%ProgramFiles%\FSLogix\Apps\frxccd.sys
Exclude file type:
%TEMP%*.VHD
%TEMP%*.VHDX
%Windir%\TEMP\*.VHD
%Windir%\TEMP\*.VHDX
\\storageaccount.file.core.windows.net\share\*.VHD
\\storageaccount.file.core.windows.net\share\*.VHDX
Note: replace " storageaccount.file.core.windows.net\share " with correct path to your storage location
Exclude processes:
%ProgramFiles%\FSLogix\Apps\frxccd.exe
%ProgramFiles%\FSLogix\Apps\frxccds.exe
%ProgramFiles%\FSLogix\Apps\frxsvc.exe
3.Set CleanupInvalidSessions Reg Key
SET IN: [HKLM\Software\FSLogix\apps\CleanupInvalidSessions]
Available in FSLogix release 2009 or later
Type: DWORD
Default Value=1
At times a Windows Session may suffer an inelegant termination, in these cases FSLogix is not provided an appropriate event to trigger the dismount of the VHD(x) file for Profile Container and Office Container. By setting CleanupInvalidSessions to 1, additional FSLogix logic is triggered to make this scenario less likely. Setting CleanupInvalidSessions will cause the functionality to be utilized for both Profile Container and Office Container. KNOWN ISSUE: at this time CleanupInvalidSessions should not be used in conjunction with Cloud Cache when concurrent sessions (e.g utilizing ProfileType/VHDAccessMode) are in use.
4.Set time limit for disconnect session
Configure Timeout and Reconnection Settings for Remote Desktop Services Sessions
Open Group Policy Console in your AD
Then navigate to the following location as the below given instructions and set to 20 or 30 minutes:
Local Computer Policy
=> Computer Configuration
=> Administrative Templates
=> Windows Components
=> Remote Desktop Services
=> Remote Desktop Session Host
=> Session Time Limits