• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 334
  • Last Modified:

Group Policy Wont Apply

Put a few new PC's out on the floor today and on after rollout they did not receive map drives or printers.  this is usually done with group policy.

We are running server 2008R2 for domain controllers and the end users have

When I attempted to run gpupdate /force I receive the following error:
The processing of Group Policy failed. Windows attempted to read the file \\domain.root\SysVol\domain.root\Policies\{B86483ED-285A-438A-9B17-9011BDE2F16D}\gpt.i
ni from a domain controller and was not successful. Group Policy settings may no
t 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.
Computer policy could not be updated successfully. The following errors were enc
ountered:

C:\Users\userguy>gpresult /h gpreport.html
INFO: The user does not have RSOP data.
0
Snip3r6659
Asked:
Snip3r6659
  • 6
  • 6
2 Solutions
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Are these new pc's located under the right OU in AD?
0
 
Snip3r6659Author Commented:
Correct the new PC's are loaded under the correct OU.  same OU as the previous.  the GPO for drives is a user policy.  and the user has not changed location.
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Are the policies created for a group of users or plain authenticated users?
0
When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

 
Snip3r6659Author Commented:
Just authenticated users
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
The machines are domain Jorinde, have correct DNS servers assigned and are authenticated by the correct DC?     Run.      Set logonserver.     To check
0
 
Snip3r6659Author Commented:
This is correct.  even tried removing and rejoining the domain
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Can these machine navigate to \\domain.root\SysVol\domain.root\Policies\{B86483ED-285A-438A-9B17-9011BDE2F16D}\gpt.ini?
0
 
Snip3r6659Author Commented:
correct they can navigate here.
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Did you check the logonserver and if you can browse that particulair sysvol folder?
0
 
Snip3r6659Author Commented:
grrr...  ok can browse to it,  but not access anything in it.  simple permission fix,  and the 2 machines I've tested so far have run the policies!

Interesting how it only affects a handful of users....
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Are you barking at me? :)
0
 
Snip3r6659Author Commented:
That moment when you realize that one more mouse click and you would have found the issue!  

Thanks for the help!
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

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