I have a RDS farm consisting of several Server 2012 R2 session hosts. I'm utilizing user profile disks and folder redirection.
The problem is as follows:
When a user logs off a session on one of the RDS session hosts, an eventID 1530 is logged, followed by an eventID 1533. The user's locally cached profile remains on C:\User of the session host with only the links to the folders that are specified in the user profile disk configuration (everything checked in "store only the following folders on the user profile disk").
Running process monitor (on the RDS session host) after the user has logged off the session host shows that svshost.exe still had open handles to the top level folders in the user's temporary profile:
So, the result of this behavior is that the next time the user connects to that RDS session host, a new local profile directory is created "c:\users\username.000", "c:\users\username.001", etc.
This is quite problematic because we are utilizing Google's G-Suite Outlook Sync connector and it would appear that at least some of the configuration for that points to hard-coded paths starting with "c:\users\username\", so if the cached profile is mounted in another folder, like "c:\users\username.000" Outlook cannot load the G-Suite profile.
I don't understand what is causing these handles to remain open after the user logs out of the session. The handles that remain open include:
c:\users\username\Appdata\Local
c:\users\username\Appdata\Roaming
c:\users\username\Desktop
c:\users\username\Documents
The only way to actually delete the local cached profile folder is to either force these handles closed (via process explorer) or reboot the RDS session host server, after which the locked folder can be deleted.
Has anybody else encountered this behaviour? It makes the setup with user profile disks unusable.