Hyper-V Server
Best Practice Analyzer (BPA)
Hyper-V Manager and System Center Virtual Machine Manager have always been tools for managing virtual machines. However, no tool can directly indicate whether your Hyper-V configuration complies with Microsoft's recommended best practices. To understand this information, you must use a Better environment management tool--HYPER-V Best Practices Analyzer.
First, using the GUI interface to configure BPA
Many friends are using Hyper-V without noticing the existence of the HPYER-V Best Practice Analyzer Tool. To access the Hyper-V Best Practices Analyzer in Windows Server 2012, simply open Server Manager, select the Hyper-V container, and then scroll the mouse to the Best Practices Analyzer section. As shown in the following:
650) this.width=650; "height=" 319 "title=" clip_image002 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" clip_image002 " Src= "http://s3.51cto.com/wyfs02/M01/77/3F/wKioL1ZmJZDyJ7FzAAB4Nj4M4lw145.jpg" border= "0"/>
Use the best Practice Analyzer to meet the criteria:
1. Windows hypervisor must be in a running state
2. Hyper-V Virtual Machine Management Service is running
3. Hyper-V Network Management Service is in a running state
4. Hyper-V Image Management Service is in a running state
The Best Practices Analyzer is blank by default: requires an administrator to initialize a best-practice scan. In order to enable scanning, you need to select the Turn on BPA scan option in the Task drop-down list at the top right of the analyzer. As shown in the following:
650) this.width=650; "height=" 161 "title=" clip_image004 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" clip_image004 " Src= "http://s3.51cto.com/wyfs02/M02/77/3F/wKioL1ZmJZHAld8bAABINXyYV5A666.jpg" border= "0"/>
Here you need to select the "Start BPA Scan" server, click on our current server click on the "Start scan":
650) this.width=650; "height=" 484 "title=" clip_image006 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" clip_image006 " Src= "http://s3.51cto.com/wyfs02/M00/77/41/wKiom1ZmJSSgUpHTAADAKRhuOa4930.jpg" border= "0"/>
Wait for the scan to finish and the scan results will be displayed under the Best Practices Analyzer:
650) this.width=650; "height=" 442 "title=" clip_image008 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" clip_image008 " Src= "http://s3.51cto.com/wyfs02/M00/77/3F/wKioL1ZmJZejnGyPAADvwvdN0yY177.jpg" border= "0"/>
Click on one of the scanned results options and click on the title "At least once a week to back up the virtual machine", which will return problems, effects, and corresponding solutions:
650) this.width=650; "height=" 313 "title=" clip_image010 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" clip_image010 " Src= "http://s3.51cto.com/wyfs02/M01/77/41/wKiom1ZmJSqg2-HtAACwJyvQGrA020.jpg" border= "0"/>
Ii. use of PowerShell Hyper-V (BPA)
1. Run PowerShell as an administrator and type the following command
Invoke-bpamodel–bestpracticesmodelid microsoft/windows/hyper-v
650) this.width=650; "height=" 149 "title=" clip_image012 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" clip_image012 " Src= "http://s3.51cto.com/wyfs02/M01/77/3F/wKioL1ZmJZrTfw-AAABIjWYJwxA519.jpg" border= "0"/>
2. Output Hyper-V BPA results using the following command
Get-bparesult–bestpracticesmodelid microsoft/windows/hyper-v
650) this.width=650; "height=" 381 "title=" clip_image014 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" clip_image014 " Src= "http://s3.51cto.com/wyfs02/M02/77/41/wKiom1ZmJSyQcErSAACVJ0jc5ms321.jpg" border= "0"/>
650) this.width=650; "height=" 306 "title=" clip_image016 "style=" Border-top:0px;border-right:0px;background-image: none;border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "alt=" clip_image016 " Src= "http://s3.51cto.com/wyfs02/M02/77/40/wKioL1ZmJZ7xO0NLAAB-pVrJlng196.jpg" border= "0"/>
The Hyper-V Best Practices Analyzer is useful for ensuring that hyper-V hosting servers follow Microsoft's best practices. However, not all reports imply problems, and when analyzing the results detected by BPA, we need to use some attempts to determine if there is a real problem.
Windows server BPA can not only check the Hyper-V server can also configure DNS, DHCP and other servers, the specific steps here do not elaborate, interested friends can study!
This article is from the "Wu Yuzhang Microsoft blog" blog, make sure to keep this source http://wuyvzhang.blog.51cto.com/9992636/1720601
Hyper-V Server Best Practices Analyzer (BPA)