FSLogix, OneDrive for Business Cache, Non-Persistent VDI Issues

Scott Glossop 6

I'm currently trying to figure out how to keep our FSLogix OneDrive cache folder in a clean state (i.e. use Storage Sense on our non-persistent VDI's to automatically "dehydrate" any OneDrive cached files that haven't been used in 14 days). So far Storage Sense does not appear to be "dehydrating" any OneDrive cached files that haven't been accessed in that time frame (for testing I set it to 1 day old OneDrive cached files to be removed), and there also appears to be no way to trigger Storage Sense to run at an exact time. I have set all the relevant group polices and running Storage Sense manually appears to be "dehydrating" the files, just not automatically.

What are others doing to try and keep their FSLogix Office container VHDX's as small as possible?

chris borms 1 Reputation point

2022-03-01T12:47:48.81+00:00

Hi, were you ever able to solve this issue?
I have the same dehydration issue on my non-persistent VDI's.

The files that are offline availble in Onedrive in the FSlogix disk have an "accessed" date/time of the logontime.
The files that are only available online don't have the a new timestamp.
It looks like the explorer.exe process is doing this.
I think this is why the dehydration is not working as it looks like the files have been opened/changed today.
The dehydration scheduled task starts normally after the computer has been idle for 10 minutes
Scott Glossop 6 Reputation points

2022-03-02T00:52:49.253+00:00

Here is what solution I ended up implementing.

I found through online guides that Windows 10 has a built-in tool called attrib.exe, which can be used to set OneDrive file states (Always available, Locally available and Online-only). I haven't had the time to create a script that can set OneDrive files to "Online-only" after a set time of not being accessed, but I did manage to create a script that sets all OneDrive for Business files to "Online-only" mode on each logoff (Which avoids profiles becoming bloated by old/unused OneDrive cached files).

get-childitem $env:OneDriveCommercial -Force -File -Recurse | where Attributes -eq 'Archive, ReparsePoint' | foreach {attrib.exe $_.fullname +U -P /s}

This script gets the OneDrive for Business folder path of the logged on user and gathers all the file information, then it filters the results for just the files that have been set to "Locally Available" (e.g. downloaded to the users OneDrive for Business cache), finally it uses the attrib.exe tool to set those files to "Online-only" (which removes the files from the OneDrive for Business cache).

I then have this set as a PowerShell logoff script in group policy.

I also use the Invoke-FslShrinkDisk script from GitHub to run each night to compact the VHDX files to reclaim the whitespace that is left behind.
Bracko Ewald 21 Reputation points

2022-12-14T22:08:42.11+00:00

Try the following in a Powershell script:

$CutoffTime = (Get-Date).AddDays(-14)

get-childitem $env:OneDriveCommercial -Force -File -Recurse | where Attributes -eq 'Archive, ReparsePoint' | where LastAccessTime -le $CutOffTime | foreach {attrib.exe $_.fullname +U -P /s}

That should do the trick I think.

And many thanks for checking out the attrib part. That helped me a lot!

1 answer

Nick Panaccio 81 Reputation points

2021-12-14T19:38:49.66+00:00

James Rankin wrote a blog article on configuring Storage Sense for OneDrive, FWIW. I have my environment (CVAD 1912 LTSR CU3, W10 20H2) configured the same way, and the last time I checked, it appeared to work. A scheduled task actually kicks off the Storage Sense function. Also, are you shrinking your containers on a routine basis? In my environment, the initial OneDrive run with Files On Demand enabled still bloating my own container to 11GB in size. I run Jim Moyle's FSL shrink script nightly, which brought it back down to 800MB or so. That has made the biggest difference in my environment for more than just OneDrive.
Please sign in to rate this answer.
Martijn Kools 146 Reputation points

2022-12-15T09:01:59.953+00:00

New fslogix version supports auto compact at logoff. That should get rid of the script and make things a lot more easy.

Also I found another article here: https://virtualwarlock.net/configure-storage-sense-in-windows-server-2019/

Which says:

Storage Sense group policy support was added in Windows 10 v1903, so with any Windows version before v1903 it’s not possible to configure Storage Sense via GPO. As you probably know Windows Server 2019 is based on Windows version 1809.

So for RDSH you probably need Windows 2022.

Azim 26 Reputation points

2023-10-27T18:09:17.2033333+00:00

hey @Nick Panaccio

I'm curious to know about how you run the FSL shrink script nightly. Do you setup a schedule/task schedule within the AVD environment?

For myself I'm running twice a week manually for a pool of 100+ users. It does get difficult doing these routines tasks.
Sign in to comment

Share via

FSLogix, OneDrive for Business Cache, Non-Persistent VDI Issues

1 answer