Hello I have recently rolled out brand new Dell Optiplex 780 machines on the network with Windows 7 installed on them. The users on Active Directory used to have XP and now when they have logged into Windows 7 there is a V2 profile created. Everything works fine, Users can print, connect to share etc...until randomly different users at different times of the day suddenly cant access their home user drive which is mapped as H:. Their Drive shows up as a red X through it, but the other shares mapped for the user can be accessed fine. When the user logs of it displays a message about the profile not being able to synchronize. When the user logs back in all is back to normal...until the next day when it happens again. The users also lose the ability to print, their printers are greyed out I have tried setting the reg key autodisconect to -1 I have created a new profile for a user I have checked the permisions are all ok I have checked power settings are on high performance I have even given a user a local only profile, but issue still occurs! Any help or ideas would be gratefully appreciated. Adam.

Please check the disk space that the romaing prolie uses, ensure it has enough space to update the roaming profile. Best Regards Dale Please 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.

I think I have nailed it. When the problem occured the other day rather than rebooting to fix the Issue, I had a mess around on the user's machine with no group policy enabled. I tried to get to the \\servername shares and it came up with the same error as when the user tries to double click on their home drive. As the home drive relies on that share to work, I then tried the \\IPADDRESS of the server and this worked great... I then tried the \\servername.FQDN and this worked fine as well!!! WTF? I even pinged the server name without the FQDN and it resolved fine! I have now edited the host file on the PC so the IP is pointing to the FQDN and it works fine now. This never used to happen on XP.. Windows 7 is wracked..

I have this same issue however there is plenty of space on the target share. The problem doesn't affect desktop users. Only Laptops. I can use a standard UNC path to get to the server and all other shares. eg: home share is U: (\\server\users\%username%) \\server\whatevershareIwant works just fine specifically the user path doesn't work unless it's accessed as \\server.FQDN\user\%username%

Nick, I am trying to get a Win7pro laptop to access our file server. What is the differdnce btw the home share and the user path?

in my case... the spelling What I meant was the share that the user profiles are stored to (includes redirected folders)