Using the MBCA to Analyze Servers and Services
Microsoft offers several tools for analysis of the implementation of a product. Some are native and other optional:
Microsoft Baseline Configuration Analyzer (MBCA)
Extend, forms the basis for the analysis of various products such as SQL Server, System Center 2012 2012, Dynamics and other:
- MBCA- http://www.microsoft.com/en-us/download/details.aspx?id=16475
- SQL 2012 http://www.microsoft.com/en-us/download/details.aspx?d=29302
- Dynamics AX 2012- http://www.microsoft.com/en-us/download/details.aspx?id=28749
- SC 2012- http://www.microsoft.com/en-us/download/details.aspx?id=36796
- Prereq RSAT W8- http://www.microsoft.com/en-us/download/details.aspx?id=28972
Microsoft Baseline Security Analyzer
Tool to examine Windows security, Windows 2008 R2.
Was discontinued after Windows Server 2012
Best Practices Analyzer
Are native Windows 2008 R2 tools and Windows 2012
Installable Server Manager http://technet.microsoft.com/en-us/library/dd759260.aspx
Failover Cluster Validation
Native Failover Cluster feature
Run by MMC Cluster Failover
Several articles discuss the use of BPA and Cluster validator are native and MBSA has been discontinued for Windows Server 2012, so in this article we will address only the MBCA and its use with System Center 2012.
MBCA and Installation Packages
The installation of this product is very simple, just run the installer.
After installing the MBCA we install the tools, or analysis packages, allowing to open the MBCA let’s see a list of available analysis packages:
Running the System Center 2012 Configuration Analyzer
Note that when you open the menu does not have an option for the SCCA, since it is a plugin of the MBCA, as can be seen below:
The next step is to select the computers that will be validated. However, to validate some remote servers you may need to register with Setspn. If you don’t know how to use, can use the SCCA’s own statements, as shown in the topics:
The results are displayed in two tabs, being possible to see a summary or detail of the parsed data. In the example below I ran in a 2012 SCSM SP1 and the initial result is that there is achieving 100% implementation and allowing export the report that can be reviewed later after saved with the option "Open Report" on first pront.
Using the Collected Data it is possible to see the data used by SCCA to validate the SCSM:
Install the MBCA and the SCCA on a single server is useful to avoid installation in a server farm or even for machines with limited access. However, in some cases it is not possible to run the SCCA remotely having as a result the message below:
The Credssp function allows the server where the SCCA is installed has access to the server that is being analyzed, being simple to run and need for remote analyses.