In an effort to keep this thread active I'd just like to describe our current situation.
We have recently deployed FSLogix in our environment. As discussed in this thread, in our case, it seems to be that when a user is logged off due to inactivity (set to 8 hours in our environment) then two things happen, one is that sometimes the profile disk will stay attached on that machine until it is administratively removed. The second issue I'm finding, through reading the ODFC logs, is that when the user is logged off due to inactivity the following logs are displayed when trying to detach the container, saying that the "User is not a member of the include group" even though it they definitely are (and had been using FSLogix during that session).
[12:32:12.701][tid:00000dac.00001abc][INFO] ===== Begin Session: Detach Outlook Data Folder Container: George
[12:32:12.701][tid:00000dac.00001abc][INFO] Configuration Read (DWORD): SOFTWARE\Policies\FSLogix\ODFC\Enabled. Data: 1
[12:32:12.701][tid:00000dac.00001abc][INFO] Include group SID: S-1-5-21-2421605326-1487003826-3486927839-16969
[12:32:12.701][tid:00000dac.00001abc][INFO] Exclude group SID: S-1-5-21-2421605326-1487003826-3486927839-16970
[12:32:12.701][tid:00000dac.00001abc][INFO] Reason set to 1: User is not a member of the include group
[12:32:12.701][tid:00000dac.00001abc][INFO] Reason set to 1: User is not a member of the include group
[12:32:12.701][tid:00000dac.00001abc][INFO] User is not a member of the include group
[12:32:12.716][tid:00000dac.00001abc][INFO] Do not handle this session
[12:32:12.716][tid:00000dac.00001abc][INFO] ===== End Session: Detach Outlook Data Folder Container: George
Once this has happened I've found that I'm having to go into the registry and remove the session key for that users SID and then the next time they log in it will work as normal. Otherwise it will say a log message similar to "The container is already connected to another session" and the profile will not load.
Today we've implemented a workaround in the way of a scheduled task that polls the server every 30 minutes to see if there is any profile disk attached to the machine for a user that's not currently logged in, if there is then it detaches the disk. It also clears out the Session registry keys for any user that isn't currently logged on. I'll let you know how I get on with this script and whether or not it stops the issues occurring.