Group Policies with multiple domains errors

Soldato
Joined
12 Jun 2012
Posts
3,918
Location
West Yorkshire
Hey guys need your help. Definatly stuck on this one.

So I am getting the following error:

The processing of Group Policy failed. Windows attempted to read the file \\domain.uk\SysVol\domain.uk\Policies\{17602F4E-76E1-4485-94C9-39FEBE818250}\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.

Detailed event log:

+ System

- Provider

[ Name] Microsoft-Windows-GroupPolicy
[ Guid] {AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}

EventID 1058

Version 0

Level 2

Task 0

Opcode 1

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2013-06-18T14:34:34.503925800Z

EventRecordID 27639

- Correlation

[ ActivityID] {A23CEFED-2660-4322-9D2F-1041041086DF}

- Execution

[ ProcessID] 1204
[ ThreadID] 5112

Channel System

Computer LD1W7L007.PUPL.UK

- Security

[ UserID] S-1-5-21-2192668076-2316841241-3330230698-9508


- EventData

SupportInfo1 4
SupportInfo2 816
ProcessingMode 0
ProcessingTimeInMilliseconds 609
ErrorCode 1396
ErrorDescription Logon Failure: The target account name is incorrect.
DCName \\domain.PUPL.UK
GPOCNName cn={17602F4E-76E1-4485-94C9-39FEBE818250},cn=policies,cn=system,DC=Domain,DC=UK
FilePath \\domain.UK\SysVol\domain.UK\Policies\{17602F4E-76E1-4485-94C9-39FEBE818250}\gpt.ini

Basically when since around 2-3 weeks ago when users log on, their already mapped drives do not show in their mycomputer. When I do a gpupdate /force manually it gives me the same error.

I tried doing a run command and pointing to the grp.ini file. Which worked until about 30 minutes ago. Now I cannot see that on this laptop. Although I can on the DC and all the security permissions are set to allow.

Ive googled and googled but none of the fixes seem to work. Have you guys seen this before? I read some where that its because the new DC's local password needs changing? (This is a new DC which was put in around the same time when the problem started).

Thanks.
 
Back
Top Bottom