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

Server 2008 R2 - Best Practices Analyzer scan has failed

I am getting a "Best Practices Analyzer scan has failed" error message when I try and check the best practices for the Active Directory Domain Services role on any of my 2008 R2 domain controllers. On two DCs I have successfully run this best practices scan in the past. There are no related error messages in the Application or System logs. The error appears to have started after promoting a 3rd 2008 R2 DC, although it may be unrelated.  Any help would be appreciated. Thanks!

Failure message
1 Solution
Mike KlineCommented:
I haven't seen this error on my boxes, saw some KBs that were close to this but not exactly it so I didn't post.  You will find those if you search "best practice analyzer scan has failed"

Have you tried re-installing BPA   http://www.microsoft.com/en-us/download/details.aspx?id=1460


Nick RhodeIT DirectorCommented:
That occurs with an improper installation.  I would recommend reinstalling it as stated above
mmmfgAuthor Commented:
Searching online this was the closest thing I could find: http://social.technet.microsoft.com/Forums/windowsserver/en-US/bb3e8f6e-e61f-480d-905d-9e0af2296bb2/best-practices-analyzer-scan-failed-with-parser-error

Thanks for the recommendation. I downloaded the update. I did already have it installed so I uninstalled it, rebooted, installed the update, rebooted, and got the same error again when running BPA.
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.

mmmfgAuthor Commented:
Thanks! I hadn't seen that. I found an & and removed it. Now the BPA scan works!

The odd thing is that this OU has been named like that for probably 7 years - since the forest was 2000 level - and I just now started having a problem with it.
mmmfgAuthor Commented:
Great find! Thanks!
mmmfgAuthor Commented:
A domain controller was moved from the Domain Controllers OU to an OU below the OU with the &. This caused the BPA to look at the OU with the & for the first time, and throw the error.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

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