System Architecture:
I have 5 Windows Server 2012 R2 Standard instances running a Remote Desktop Services Session Collection.
Server #1 is the Connection Broker, and hosts the share for central User Profile disks.
Servers #1 - #5 are load balanced under the Session Collection.
---
Problem:
1. New user (has not logged in before) RDPs to Server #1. Load balancing redirects to another Server (say Server #5).
2. Login is way too instant. An inspection reveals that the user profile has been logged in with a temporary profile.
3. User logs out fully (as opposed to disconnecting).
4. User logs in again, gets load balanced again to Server #5, this time the loading takes longer, it appears the .VHDX user profiledisks is being created. On inspection, user is using actual profile, no longer using a temporary profile.
---
This is readily reproducible by me. In one instance, it took logging off and then back on two times before the user profile disk was created.
---
An inspection of the logs gives the same error every time:
Remote Desktop Services could not apply a user desktop for a user account with a SID of S-1-5-21-3954512987-845256609-1816244978-2710. A temporary profile was enforced for the user. Verify that the user profile disk settings are correct. The error code
is 0x21.135
All online searches of this error all lead to the same hacky "fix" given by Microsoft of deleting a registry key of the profile. None even attempt at the source of the problem. Example article:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/734fae1e-9a47-415c-b53e-e1cdbdd8c38d/windows-2008-r2-you-have-been-logged-on-with-temp-profile
---
These Windows Server 2012 R2 instances are all brand new and have not been subjected to odd changes over time - they are pretty much out of the box OS instances.
This is obviously pretty important to fix. Any ideas?