Cannot Update Roaming Profile-Access Denied

[longlivegoku]

We are getting an error message on multiple machines that is stated up in the subject line. The machines cannot update the roaming profiles we use...this is a known problem by Microsoft but from what I read SP2 should have fixed this problem. Anyone else have any input?

Thanks.

 

[FilthPig]

Find their profile folder on the network, open the properties on it. Go to the Security tab, click Advanced. On the Owner tab, make Administrators the owner and check replace ownership on all subcontainers and objects. Apply. On the permissions tab, make sure Administrators and the user whos profile it is have full control, Check Reset permissions on all child objects and apply. Marc Creviere

 

[mritorto]

I am having the same problem here is the error message


Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 5/21/2002
Time: 8:18:25 AM
User: INTERNAL\tammy.leung
Computer: WS061JC
Description:
Windows cannot copy file C:\Documents and Settings\TEMP\ntuser.ini to location \\filecluster1\private_profiles$\tammy.lueng\ntuser.ini. Contact your network administrator.

DETAIL - The process cannot access the file because it is being used by another process.

 

[mritorto]

The user has full control to the profile and they are still getting errors

 

[mritorto]

This is the latest message:


Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 5/17/2002
Time: 7:19:44 PM
User: NT AUTHORITY\SYSTEM
Computer: WS060RD
Description:
Windows cannot update your roaming profile. Contact your network administrator.

DETAIL - The process cannot access the file because it is being used by another process.

 

[Niavlys]

I had that problem last week. Check out if disk quotas are enabled on your volume. If the specified user has past over the limit, even if you are not denying the write access, the profile will not be updated on the server.

Weird hein...

 

[rjbj]

Try this link:

http://search.support.microsoft.com...dType=ALL&Titles=false&numDays=&maxResults=25

It seems that this problem has something to do with a group policy.