We migrated to a Server 2016 based RD system a while back and in increasing frequency, users who log off or time out when they disconnect (it happens in both cases, possibly more so in the latter) don't have their profile accessible.
Using the "Sidder" app I can see that the users profile .vhdx file is locked and appears in use on one of the RD hosts, but the user is not logged in when viewing directly on the server or via the RD broker server.
By closing the open files on the profile drive server that stores those profiles, the user can usually then log in, but in some cases - if they get the same server they used last in the RD host pool - that server still refuses to load the profile, and I have to manually shut down logins on that server to steer them to another host, where their profile finally attaches.
This is, obviously, making my users furious. This kind of song and dance to log in when they go to do work is not appreciated, nor does our IT people enjoy the wasted time troubleshooting this stuff.
Does anyone have any suggestions on what could be causing this unreliability? Is the only answer really to get a third party profile management system to fix this into a usable state? We tried classic roaming profiles on an earlier generation system and had all the fun roaming profile problems so going back in time is not an option.
