FSLogix builds a search index for our non persistent desktops. A good article from James Kindon explains it well

https://jkindon.com/2020/01/06/fslogix-containers-search-index-considerations-and-troubleshooting/

I created Disk space alerts via Perf Mon (I will show this in later blogs) for FSlogix disk space thresholds. In this example this user the alert fell below the 10% threshold and upon further investigation we found the see this edb file is quite large…

Depending on the size of the file you can defrag and reduce it based on the MS article

https://docs.microsoft.com/en-us/troubleshoot/windows-client/shell-experience/larger-windowsdotedb-file

EsentUtl.exe /d %AllUsersProfile%\Microsoft\Search\Data\Applications\Windows\Windows.edb

If successful you will see this…

However, there may be times when the container simply does not have enough space….

Based on the JK article listed above one can delete the FRXOutlook_XXXX folder. When we do that the profile needs to be offline or not in use.

Delete the folder in the

%username%\AppData\Roaming\FSLogix\WSearch\FrxOutlook_xxxx

When the user logs back into the desktop the folder will be recreated and the space can be reclaimed

The other option is to expand the user’s VHDX file which I will show how to in a later blog

.\trevor