Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 279
  • Last Modified:

Windows Server Roaming Profile Problem

Hi,

I am experiencing a strange problem after we format all of our computer on the network to Windows 7 from Windows Vista.

When I create a new user account in the AD, lets say user adam, i set the profile path to \\profileServer\profile\adam and I leave the home folder as Local path.

When login on Windows 7 Machine #1, it created the adam.V2 without problem. All the folders (i.e. desktop, my documents, downloads) are there. I hit log off.

Now when I try the same login without any setting change on Windows 7 Machine #2, it gives me an error

"The Group Policy Client service failed the logon - Access is Denied"

I then try the login on Machine #1 and it works fine. I try to create a file on desktop and log off, i check on the server, i can see the file is being copied to profileServer properly.

Any ideas why?

***** Additional Notes #1 *****
Its the same problem when I try first logon on Machine #2 then Machine #1. In this case, the Machine #2 will work properly but not Machine #1.

In general, the problem is I can logon 1st time a specific computer. Afterwards, only the computer I logged on with will function properly and all other machines will just show
"The Group Policy Client service failed the logon - Access is Denied "

***** Additional Note #2 *****
The user is a Member of Domain Users

***** Additional Note #3 *****
AD is running on Windows Server 2008 Enterprise
Workstation is running Windows 7 Business Edition
All firewall has been dropped for testing
All computers able to ping each other
All workstation can see the profileServer without problem

Anyone know what's the problem and how to resolve it?

Thanks
0
geoffryf
Asked:
geoffryf
  • 4
  • 2
1 Solution
 
Ernie BeekExpertCommented:
If you check the folder properties on the server, does the user have all the correct right and is he/she the owner?
0
 
geoffryfAuthor Commented:
yes, the user have the correct permission. Also, to simplify the problem, i tried to set it to "Everyone" and the user have full access right. This still didn't help the situation.

Thanks
0
 
Ernie BeekExpertCommented:
Anything showing up in the event logs (server/workstation?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
geoffryfAuthor Commented:
After reinstall the windows and rejoin the network, it seems to be fine now.

Thank you everyone
0
 
geoffryfAuthor Commented:
Always look at the event logs :)
0
 
geoffryfAuthor Commented:
thanks for telling me to look at the event log, this solved the problem. Apparently, some file are corrupted and some registry key is missing.

Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now