Windows server 2008 r2 best practices analyzer download free.Running and Filtering Scans in Best Practices Analyzer
Looking for:
Windows server 2008 r2 best practices analyzer download free.Update for the AD DS Best Practices Analyzer rules in Windows Server 2008 R2 |
Using the Microsoft SQL Server R2 Best Practice Analyzer.Download Hyper-V Best Practices Analyzer (BPA) – Hello
In Windows management, best practices are guidelines that are considered the ideal way, under typical circumstances, to configure a server as defined by experts. For example, it is considered a best practice for most server applications to keep open only those ports required for the applications to communicate with other networked computers, and block unused ports.
Although best practice violations, even crucial ones, are not necessarily problematic, they indicate server configurations that can result in poor performance, poor reliability, unexpected conflicts, increased security risks, or other potential problems.
BPA can help administrators reduce best practice violations by scanning roles that are installed on managed servers that are running Windows Server or Windows Server R2, and reporting best practice violations to the administrator.
You can also instruct BPA to exclude or ignore scan results that you do not want to see. Performing Best Practices Analyzer scans on roles. BPA works by measuring a role's compliance with best practice rules in eight different categories of effectiveness, trustworthiness, and reliability.
Results of measurements can be any of the three severity levels described in the following table. The following table describes the best practice rules categories against which roles are measured during a Best Practices Analyzer scan.
In Windows Server R2 and Windows Server , some roles prompt you to specify additional parameters, such as the names of specific servers or shares that are running parts of the role, or the IDs of submodels, before starting a BPA scan. Scanning roles by using Windows PowerShell cmdlets. Running BPA scans from a role or group page scans all roles that are installed on servers in that group. Depending on the number of rules that are evaluated for the role or group you selected, the BPA scan can require a few minutes to finish.
The procedures in this section do not show all BPA cmdlets and parameters. To run Windows PowerShell as an administrator from the start screen, right-click the Windows PowerShell tile in the Apps results, and then on the app bar, click Run as administrator.
To run Windows PowerShell as an administrator from the desktop, right-click the Windows PowerShell shortcut in the taskbar, and then click Run as Administrator. There is no need to import or load the BPA cmdlet module. Enter one of the following commands to start the BPA scan for a specific role. For multiple roles, separate model IDs with commas. You can also start a scan on a specific role from the results of step 3 by piping the results of the Get-BPAmodel cmdlet into the Invoke-BPAmodel cmdlet as shown in the following example.
Running this cmdlet without specifying a model ID pipes all models that are returned by the Get-BPAmodel cmdlet into the Invoke-BPAmodel cmdlet, starting scans on all models that are available on servers that have been added to the Server Manager server pool.
Open a Windows PowerShell session with elevated user rights, if one is not already open. See the preceding procedure for instructions. When the scan is complete, Windows PowerShell returns results similar to the following, for each role that was scanned. When you select a result in the tile, a preview pane in the tile displays result properties, including an indication of whether the role is compliant with the associated best practice.
If a result is not compliant, and you want to know how to resolve the problems described in the result properties, hyperlinks in error and warning result properties open detailed resolution help topics on the Windows Server TechCenter. BPA scan results are not automatically saved or archived. Running a new scan on a model or submodel overwrites the results of the last scan. Results can be included again at any time. When you exclude results, they are also excluded from view on managed servers.
Other administrators cannot see excluded results on managed servers. To exclude results from view in a local Server Manager console only, create a custom query instead of using the Exclude Result command. The Exclude setting is persistent; results that you exclude remain excluded in future scans of the same model on the same computer, unless they are included again.
As in the Best Practices Analyzer tile in Server Manager, you can exclude individual result objects, or you can also exclude a set of results whose fields category, title, and severity, for example are equal to or contain specified values.
For example, you can exclude all Performance results from a set of scan results for a model. In the Best Practices Analyzer tile for the role or server group, right-click a result in the list, and then click Exclude Result.
To view excluded results in the GUI, run the built-in Excluded results query. Click Saved Search Queries , and then click Excluded results. After running the Excluded results query, note that the tile subheading text, a description of the results that are displayed in the list, changes to Excluded results.
Only excluded results are displayed in the list. The second section of the command filters the results of the Get-BPAResult cmdlet to retrieve only those scan results for which the value for a result field, represented by Field Name , matches the text in quotation marks. The final section of the command, following the second pipe character, excludes the results that are filtered by the previous section of the cmdlet.
When you want to view scan results that were excluded, you can include those scan results. The Include setting is persistent; included results remain included in future scans of the same model on the same computer. In the Best Practices Analyzer tile for the role or server group, right-click an excluded result in the Excluded results query list, and then click Include Result.
The result is no longer displayed in the list of excluded results. Clear the query by clicking Clear All to view the included result in the list of all included results.
Include specific results from a model scan by typing the following command, and then pressing Enter. The preceding command retrieves BPA scan result items for the model represented by model Id.
The second part of the command, after the first pipe character filters the results of the Get-BPAResult cmdlet to retrieve only those scan results for which the value of the result field, represented by Field Name , matches the text in quotation marks. The final part of the command, after the second pipe character, includes results that are filtered by the second part of the cmdlet, by setting the value of the -Exclude parameter to false.
To view and manage scan results by using Windows PowerShell cmdlets, see the following procedures. Before you can use any of the following procedures, run at least one BPA scan on at least one model or submodel. Get the results of the most recent scan for a specified model ID. You can get results for multiple model IDs by separating the model IDs with commas. To format BPA results in a table, run the following cmdlet, adding the result properties that you want to see from the preceding example.
To format BPA results in a GUI-based grid viewer, with a text-string filter, and column headings that can be clicked to sort results, run the following cmdlet. To export BPA results to an HTML file that can be archived or sent to email recipients, run the following cmdlet, where path represents the path and file name to which you want to save the HTML results.
To export BPA results to a comma-separated values CSV text file, run the following cmdlet, where path represents the path and text file name to which you want to save the CSV results. CSV results can be imported into Microsoft Excel, or other programs that display data in spreadsheets or grids.
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. Skip to main content. Contents Exit focus mode.
This topic contains the following sections. How BPA works BPA works by measuring a role's compliance with best practice rules in eight different categories of effectiveness, trustworthiness, and reliability. Severity level Description Error Error results are returned when a role does not satisfy the conditions of a best practice rule, and functionality problems can be expected.
Information Information results are returned when a role satisfies the conditions of a best practice rule. Warning Warning results are returned if the results of noncompliance can cause problems if changes are not made.
The application might be compliant as operating currently, but may not satisfy the conditions of a rule if changes are not made to its configuration or policy settings. For example, a scan of Remote Desktop Services might show a warning result if a license server is unavailable to the role, because even if no remote connections are active at the time of the scan, not having the license server prevents new remote connections from obtaining valid client access licenses.
Rule categories The following table describes the best practice rules categories against which roles are measured during a Best Practices Analyzer scan. Category Name Description Security Security rules are applied to measure a role's relative risk for exposure to threats such as unauthorized or malicious users, or loss or theft of confidential or proprietary data.
Performance Performance rules are applied to measure a role's ability to process requests and perform its prescribed duties in the enterprise within expected periods of time given the role's workload.
Configuration Configuration rules are applied to identify role settings that might require modification for the role to perform optimally. Configuration rules can help prevent conflicts in settings that can result in error messages or prevent the role from performing its prescribed duties in an enterprise. Policy Policy rules are applied to identify Group Policy or Windows registry settings that might require modification for a role to operate optimally and securely.
Operation Operation rules are applied to identify possible failures of a role to perform prescribed tasks in the enterprise. Predeployment Predeployment rules are applied before an installed role is deployed in the enterprise. They let administrators evaluate, before the role is used in production, whether best practices were satisfied. Postdeployment Postdeployment rules are applied after all required services have started for a role, and after the role is running in the enterprise.
Prerequisites Prerequisite rules explain configuration settings, policy settings, and features that are required for a role before BPA can apply specific rules from other categories. A prerequisite in scan results indicates that an incorrect setting, a missing program, an incorrectly enabled or disabled policy, a registry key setting, or other configuration has prevented BPA from applying one or more rules during a scan.
A prerequisite result does not imply compliance or noncompliance. It means that a rule could not be applied, and is not therefore part of the scan results. On the Windows taskbar, click the Server Manager button. On the start screen, click the Server Manager tile. In the navigation pane, open a role or group page.
Scanning roles by using Windows PowerShell cmdlets Use the following procedures to scan one or more roles by using Windows PowerShell cmdlets. Note The procedures in this section do not show all BPA cmdlets and parameters. Note BPA scan results are not automatically saved or archived.
Note When you exclude results, they are also excluded from view on managed servers. Note You must run at least one BPA scan on a model before you can use procedures in this section. Is this page helpful? Yes No. Any additional feedback? Skip Submit. Submit and view feedback for This product This page. View all page feedback.
Comments
Post a Comment