I have a terminal server farm (running RDS on 2008R2) which is configured using guides and best practices from various Microsoft sources. I notice nothing wrong with the server farm when using it myself, but many regular users often (but not always) get logged in with temporary profiles (default profiles) instead of getting their roaming profile downloaded and applied. To alleviate this somewhat, I've applied folder redirection (which works flawlessly) for some important folders like the Desktop, and GPOs to make sure all users always get the correct printers and whatnot.
However, I would really like to fix the actual problem instead of trying to work around it, but as the only error given is a 1060, there is really no proper clue as to what the issue really is.
Now, before some of you redirect me to the article pertaining to Event ID 1060, YES, I've read it. None of it applies to my system. The file server (and session broker) hosting the profiles (and the redirected folders) is properly set up, the profile and
redirected-folder shares both have best-practices permissions and folders get created correctly for new users. There is definitely no network issue (the farm is running in a VMware cluster in which every other 2008R2 server has no issue whatsoever), and all
users get the same and correct path to the roaming profile share through a RDS GPO applied to the server. It is also not a permission issue since folders get created correctly for new users, both the roaming profile share and the redirected-folders share have
the same permissions and the folder redirection never fails.
When I log in (as an administrator), I ALWAYS get my roaming profile. I have NEVER gotten an Error 1060. I have also tested with a freshly created regular user and get it's roaming profile 99 times out of 100. But MOST users get their roaming profile maybe
3 times out of 10, which is insanely frustrating as it pops up a "you have been logged in with a temporary profile" tooltip and litters the Event Log of each server in the farm with 50-100 1060 errors daily that are, as far as I can tell, completely
lacking a logical reason. They manifest as an error for the user, but there is NO reason why this error should appear in the first place on this system.
Any help in troubleshooting this would be most appreciated, as I've read pretty much everything on the subject and have fought with this for several months trying different approaches, but still being nowhere closer to a solution or even a plausible explanation, since everything is correctly set up and none of the MS-suggested reasons for the 1060 error have proven applicable in this case.