This message was deleted.

Guessing you are asking this? If the session ends or get lost and the VHDX is still mounted. The key will clean that up and ensure or suppose to ensure a user can use the VHDX again without locks.

So what's the difference in behaviour with a standard disconnect? Does it force a logoff and potentially lose user data?

No I don't believe so. Because the session is still established and the backend is running(VDA) I am not sure how it triggers it. But I know for example if I am in a session and lets say it gets rebooted or my VDA/RDSH end somehow. Upon next log in it's supposed to release it and cleanup. The is a simplied explanation of how I understand it.

Hmmm, sounds like it might cause more issues than it fixes

Maybe others will chime in and help. I used it a couple of times. I did not see any issues, but it was just a basic profile container.

We have used this to prevent the local_%username% folders from sticking around. No issues noticed.

its meant to fix issues where you have ghost sessions where it leaves the session in HKLM\software\Fslogix\profiles\sessions HKLM\software\polices\Fslogix\ODFC\sessions and the users VHDX's mounted