[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

GPResult showing inaccessible. The GPO name it wants doesn't exist. Help?

The GPResult shows it's looking for {EAAD54C2-7530-4859-A038-1D1CE63B1438} while the GPO it has linked to it is {BA0CD540-B951-4481-960E-AB0DE32C7EB4}.  In fact, there is no {EAAD54C2-7530-4859-A038-1D1CE63B1438} in sysvol.

I'm not really sure how to begin to look at it.  I have a hunch I can copy the BAO folder and rename it to match the EEAD folder, but I'd rather fix the issue than work around it.

 I'm not sure how much other information is needed, but this is an account on our local directory and a machine on the local directory.  The machine is Windows7, the DCs are Server2008r2.
0
MU-IT
Asked:
MU-IT
1 Solution
 
MU-ITAuthor Commented:
This turned out to be a WINS issue, or perhaps NetBIOS.  If I remove the IP for one of our WINS servers, All is well.  So.... I know what to fix to make GPO work, but what could be wrong on WINS to affect GPO?
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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