Hi all, At work we've recently deployed Windows 7 on machines that formerly had Windows XP. Most of our end users have roaming profiles. Every morning when a user logs into his or her computer they receive a message saying that their profile could not be loaded, and that a previously saved local profile was loaded instead. The users don't have access to their files on the server, or to their e-mail settings, etc. To remedy this I have to remove the computer from the domain, as well as from Active Directory and DHCP, then put the computer back into the domain - after performing those steps the roaming profile loads fine. Obviously this is a major waste of time and cause for headaches, and I haven't found any suitable answers on the forums yet. I'm hoping that someone can help me out with this!

Windows 7 machines are migrated with USMT with their previous profile? when there are errors while loading profile, check event veiwer and see for any errors. what happens when you create new roaming profiled user ? i guess it works. its the issue with old ones. it could be permissions issue on old profile. Thanks Uday Kiran, Senior Consultant Cyquent Technology Consultants, Dubai Please Mark as answer if it helps you

All the roaming profiles were converted to .V2 profiles, actually, so they're all brand-spanking-new.

In my event viewer I get a 1521 event: Windows cannot find a copy of your roaming profile on the server and has attempted to load a local profile (I'm translating the message from French so I might be a bit off). When I try to connect to the server and see my .V2 profile I can't connect; I can connect to any other part of the server just fine, but I can't connect to the place where the profiles are stored.

Sam, it looks like its permission issue on that roaming profile. please look at below article and configure root folder permissions and user profiles permissions http://technet.microsoft.com/en-us/library/bb490855.aspx#EKAA ALso in the same article look at the troubleshooting part loggingThanks Uday Kiran, Senior Consultant Cyquent Technology Consultants, Dubai Please Mark as answer if it helps you

I don't think it's a permission issue. The roaming profiles DO work on occasion, and the solution that I outlined in my original post does work, temporarily. I can also get the profile to work if I delete the SID, delete the folder in C:\Users, and take the machine out of the domain and back in again 3-4 times (which is time consuming and counter-productive in a work environment). Has no one else experienced this issue? I find that really hard to believe. Oh, and I forgot to mention that we use a Windows Server 2003 domain.

I have the problem with my roaming profile and I am administrator across the domain, so I have my doubts that it's a permission issue... but I'll take a look. UPDATE: I deleted the SID of the offending profiles in the registry, and now the profiles all log in as Temporary Profiles - it seems I'm worse off than when I started! Can someone tell me how I can reverse this?

Hi, According to your description, you could not access the roaming profile folder in server. It sound like a permission issue, you may try to check the security configuration of roaming profile folder: Security Recommendations for Roaming User Profiles Shared Folders Meanwhile, if you configure folder redirection, try to disable the folder redirection policy to see how it works. Also, try to create a new test profile and specify the correct UNC path. Hope it helps. Alex ZhaoPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Being the good sport that I am, I checked the permissions on the folders on the server; users have total control permissions on their own server-side profiles (obviously), and myself as an Administrator I also have total control permissions on all profiles. So we can now be absolutely, 200% sure that this is not a permissions issue! :) Is there anyone else who can provide a clue as to how to resolve this issue?

I hate to sound stubborn, but a permissions issue doesn't happen randomly. If it was a permission issue, the user wouldn't be able to access their profile on the server, EVER. However, the users CAN access their roaming profiles, SOMETIMES and seemingly RANDOMLY. Even this morning, a user didn't have access to their profile. I took the machine out of the domain, put it back in, and poof! it worked again. The same user had access to their profile all of last week without issue. Finally, we don't use Folder Redirection.

Alrighty, it seems that we've fixed our problem. Our DNS was saturated and many computers were sharing IP addresses. We cleaned up the computers and IP addresses that shouldn't be there anymore (in DNS, DHCP and Active Directory). The crucial thing to do is to reserve the machine's IP address for the MAC address in the DHCP, for every machine you want to use roaming profiles on. Once that is done, restart the computer and voilà! Your roaming profile works again. Hopefully this will serve for the next person who has this issue.