I could really really use some help with this one.
I have 3 terminal servers. All run 2008 R2. The domain is a mix of 2008 (R1) and 2003 servers. It runs at a 2003 Functional Level if that makes any difference.
Our users have a Terminal Services profile attached to their user account. So whenever they sign off one of our 3 terminal servers and onto a different one their settings follow them around.
For the last few weeks we have been having terrible problems with users getting the message when they sign in "You have been logged into a temporary profile"
This of course causes all kinds of problems for our users. Their desktop icons get completely re-arranged (they have redirected desktops and mydocs, so they at least GET their icons, they're just out of order). They lose their exchange configuration, so they can't open up Outlook. In some instances their login script doesn't run correctly so they sometimes (not always) don't get their drive mappings, which is necessary to run many of their applications.
No matter what we've tried we cannot solve this problem. Sometimes a reboot to the server will enable users to get back on to their genuine profile. I've tried all of the fixes regarding the HKLM\Software\Microsoft\Windows NT\Current Version\ProfileList registry settings and the .bak keys that are created.
Sometimes deleting a user from the profile list, or renaming their .bak profile entry will let them get their real profile, but not always. Sometimes the user will log off and back on and it will work randomly. Some users seem to get temp profiles more often than others. Nothing about any of this really makes sense to me.
If I can provide any additional information to clarify, please let me know and I will do so. These problems started very suddenly after a power outage at our facility where the servers were offline for a couple of hours. Other than that I don't really know why this started. They were fine up until that day. One of the servers had a bad memory chip that got replaced a few days after that, but that's the only hardware malfunction I believe to be associated with the power outage / hard shutdown