Hands on with the Hyper-V BPA (Best Practices Analyser)
Make sure you have the Hyper-V BPA hotfixes installed:
- http://support.microsoft.com/kb/2485986 (If using SP1, especially when using Dynamic Memory)
You can use Windows Update or Windows PowerShell (shown below as it should appear) to check if you have the updates installed.
Once the scan is complete, the results will be displayed. Double-click any of the entries to see more detail.
Ok, so I’m not compliant. Why? Well I didn’t realise the Windows XP processor issue was the case, I thought Windows XP took two vCPUs like Windows Server 2003 – Obviously that is not the case. Also, I only have one NIC in this server. It’s a lab, I can get away with it, but don’t do that in a production environment.
Now for the fun stuff. Maybe you want to schedule the BPA to run periodically and email you if it fails. That’s when you use PowerShell!
Start by importing the Best Practices Module:
To get a list of commands available in the module, use get-command:
The get-bpamodel cmdlet can be used to get a list of best-practices scanners available on the server:
The Invoke-BPAModel cmdlet can be used to run a best practice scan. Just pass in one of the Ids listed when from the get-bpamodel cmdlet:
The Get-BPAResult cmdlet will allow you to see to see the results of the analysis.
It can be a little bit of information overload, so you best combine it to a few select, sort and format statements:
This could easily be built into a larger script that performs the actions previously mentioned.