Domain computer profile wont sync

[RaidoR]

Hello,

I have problem with one client computer profile. Profile wont sync. For example when I delete items from desktop, server syncs them back.

Here is event log output that I think is related to that problem.

The processing of Group Policy failed. Windows attempted to read the file \\metec.local\sysvol\metec.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.

What can I do to resolve this problem.

 

[GokAy]

Is the time on client matching the DC?

 

[RaidoR]

Yes

 

[RaidoR]

Any other ideas?

 

[GokAy]

You already checked the possible causes listed in your first post, right?

 

[ComputerGeek]

In general, a couple things come to mind

Use gpresult and check result for the local computer and the user account with the problem. Does gpresult have the same failure? Is it consistent?

Use Explorer and the UNC path to the file. Can you access and then open the gpt.ini file from the local computer user account? (gpt.ini is a text file. Try opening it with notepad). Check permissions on the file

 

[RaidoR]

a) Name Resolution/Network Connectivity to the current domain controller. - computer resolves DC name
b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). - I have only one DC.
c) The Distributed File System (DFS) client has been disabled. - Don't know about that.

 

[GokAy]

The Distributed File System - Windows 7 Tutorial

The service on client DFS Namespace Client Driver - Windows 7 Service - batcmd.com check a working client for the service startup and state.

Try running in cmd as admin (just in case):

sfc /scannow