We currently run xp on the desktop, and user profiles are working normally. However, I am testing windows 7 and have been able to get roaming profiles to work. When the user logs in for the first time they get an erro saying that; You have been logged on with a temporary profile.’ You cannot access your files and files created in this profile will be deleted when you log off. To fix this, log off and by try logging on later. Please see the event log for details or contact you system administrator. When the user logs out a folder called profile.v2 is created in the home folder, which it should be creating one called profile according to what has been set in the users AD user object. If I log back in with the user the same error appears, and none of the previous changes to the users profile have been saved. The applications event log has two warning; 1. Windows has backed up this user profile. Windows will automatically try to use the backup profile the next time this user logs on. 2. Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.The server side is 2008r2, and the desktop is Windows 7 Pro. Does anyone have any suggestions.

Hi College Guy, Seems like Windows can't find or can't open the user profile itself. I would look to removing the possibly offending profile and and recreating it.. o at the very least looking at possible file corruption or something else in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList key of the registry. Hopefully you get it sorted out, @calwell

I ran into this exact same issue. Using Calwell's advice, I removed the profile for my username and all worked as it should.In my case, I used Sysprep to create an image of a 2008 R2 server. When I loaded the image onto a new server, I received the error that College Guy did. If you go to the registry key that Calwell showed, you can select the key and look to the right side and in ProfilesImagePath it will show you the username that this profile corresponds to. I think the cause then (at least in my case) is that I did not correctly clean up my user profile before performing the sysprep. In earlier versions of windows, the best practices were always to delete user profiles before sysprepping but, it never seemed to matter. Apparently, Microsoft made some kind of change...

Thanks. This has worked for me as well - I just deleted out the profile GUID under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList key of my RDS server.