Event 1065 on SBS 2011 Server

We have a SBS2011 server acting as domain controller for about 30 PCs (mix of XP and Win7). The server system event log is filling up with this error:

The processing of Group Policy failed. Windows could not evaluate the Windows Management Instrumentation (WMI) filter for the Group Policy object CN={F671C9D6-38B4-42A1-B887-4F7525586B39},CN=POLICIES,CN=SYSTEM,DC=EAGLE,DC=LOCAL. This could be caused by RSOP being disabled or Windows Management Instrumentation (WMI) service being disabled, stopped, or other WMI errors. Make sure the WMI service is started and the startup type is set to automatic. New Group Policy objects or settings will not process until this event has been resolved.

We have done all the following per search recommendations:

- Ensured the Windows Management Instrumentation (WMI) service is enabled and configured for automatic startup (currently running, restarted it to be sure)

- Ensured the path, %Systemroot%\System32\Wbem, is included in the PATH system environment variable

- Ensured the computer can evaluate WMI queries. (wbemtest.exe  connects fine and I can run queries)

 - ran wmimgmt.msc on server and right-clicked WMI Control (Local),  selected properties. No errors are shown

Any additional troubleshooting ideas greatly appreciated.
zicemanAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Emmanuel AdebayoGlobal Windows Infrastructure Engineer - ConsultantCommented:
Good morning,

Have you check out what that group policy is (the one identified by: CN={F671C9D6-38B4-42A1-B887-4F7525586B39},CN=POLICIES,CN=SYSTEM,DC=EAGLE,DC=LOCAL). Look at the WMI filter in that group policy, see if it is needed, modify accordingly.

Also, have you, recreated the WIM files located at %SystemRoot%\System32\Wbem\Repository folder, it might be corrupted.

Regards
zicemanAuthor Commented:
Emmanuel - thanks for your reply.

How exactly can I find that group policy? Where and with what do I search for that CN string?

If the WMI is corrupted, can recreate the folder without breaking the existing / functioning operations?

Other log events the occur repeatedly are:

DCOM was unable to communicate with the computer Lesley.eagle.local using any of the configured protocols.
DCOM was unable to communicate with the computer Claire.eagle.local using any of the configured protocols.
DCOM was unable to communicate with the computer LARRY.eagle.local using any of the configured protocols.
Emmanuel AdebayoGlobal Windows Infrastructure Engineer - ConsultantCommented:
Yes, you can query the GUID using Active Directory Users and Computer. Please check http://www.giveandtake638.com/it-system-administration/how-to-find-the-gpo-name-with-an-guid

Also, if WMI is corrupted, you can recreate the folder without breaking the existing / functioning operations?
http://normesysadmin.blogspot.co.uk/2012/11/wmi-error-1065-processing-group-policy.html

regards
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

compdigit44Commented:
Have you view the WMI query in question? Has anything changed in your environment to cause it to fail?
zicemanAuthor Commented:
Have not been able to view WMI query.

Tried to query the GUID using the methods that Emmanuel had suggested above, but could not get them to work.  It AD Users & Computers, doing a custom / advanced search on {F671C9D6-38B4-42A1-B887-4F7525586B39} returned nothing (with or without the brackets).  The command Get-GPO was not recognized in Powershell.

The only possible cause might be an ungraceful shutdown by the machine a few weeks ago with UPS went bad.
compdigit44Commented:
If you do not have many GP you could open each on and check the GUID manaully

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
zicemanAuthor Commented:
OK. I have determine the that GUID {F671C9D6-38B4-42A1-B887-4F7525586B39} matches the GPO for the SBS Windows Firewall. We have the firewall disabled for public and private networks currently, as this machine really does not access the internet.

So - knowing the GPO in question, what would you advise is the next step?  

Also, is any of these errors related? :

DCOM was unable to communicate with the computer Lesley.eagle.local using any of the configured protocols.
DCOM was unable to communicate with the computer Claire.eagle.local using any of the configured protocols.
DCOM was unable to communicate with the computer LARRY.eagle.local using any of the configured protocols.
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.