Setting up and using the new System Center 2012 SP1 Configuration Analyzer
The System Center (SC) 2012 SP1 Configuration Analyzer was recently released on February 22, 2012. The new Configuration Analyzer is a diagnostics tool to evaluate configuration settings for computers running any of the System Center 2012 SP1 components.
This tool replaces the previous release of the Configuration Analyzer that required separate Best Practice Analyzers for each of the System Center components.
To use the Configuration Analyzer, you will need the following:
- Operating System supported by System Center 2012 SP1 (Windows 2008 R2 SP1, Windows 2012) http://technet.microsoft.com/en-us/library/jj628205.aspx
- Microsoft Baseline Configuration Analyzer (MBCA) 2.1 http://www.microsoft.com/en-us/download/details.aspx?id=16475 (Not sure why the title says 2.0, but this is the right MBSA to use…)
- The System Center 2012 SP1 Configuration Analyzer http://www.microsoft.com/en-us/download/details.aspx?id=36796
The first thing I did in my lab is created a new Hyper-V VM running Windows 2012. To create the VM, I used a simple RunBook I created in SCO, takes about 10 sec for inputs then I wait for the new VM to be created. (good time to grab some ice cream )
On my new VM, since it is running Windows 2012, I need to install the .NET 3.5. The MBSA does require .NET 2.0 which is included in .NET 3.5.
Installation of the MBCA is pretty simple, just run MBCA_Setup64_Win8.msi and accept all the defaults.
Next install the System Center 2012 SP1 Configuration Analyzer, just run SC2012SP1CA.msi and accept all the defaults.
Using the tool
When setup is complete, run the MBCA and select System Center 2012 SP1 –Configuration Analyzer under "Select a Product", then Start Scan.
On the Enter Parameters screen, enter the server name of the server you want to run the the Configuration Analyzer against. The first System Center server I will be checking is my SC 2012 SP1 VMM Server, run under my logon account.
When finished, I only had one issue with my VMM server with SPNs, instructions provided on how to correct within the tool.
Everything else was OK
On to my Operation Manager Server
For Operations Manager, the Configuration Analyzer came back with errors right away.
The analyzer said I needed had to run the following commands on the servers;
On my Operations Manager Server, from a PowerShell administrative shell –
Enable-WsManCredssp -Role Server
On my Configuration Analyzer Server, from a PowerShell administrative shell –
Enable-WSManCredSSP -Role Client –DelegateComputer LABSCV0OM [target machine name]
After running the PowerShell commands, I started the scan again. This time the scan ran successfully. Only issue was for an un-supported SQL version. I am running SQL 2012 CU3, the tool is looking for CU2.
Everything else passed
On to my Orchestrator Server
For Orchestrator, I received a warning on the BPA log purge results is set to the default value which could affect performance.
Everything else passed
On to Configuration Manager, here is where things start to get weird, not sure what is going on but there is not much being checked with Configuration Manger. I would expect more checks to be performed but only Cube-processing jobs were successful. No issues found with this check but there is not anything else being checked like WSUS, SQL, etc. The tool seems kind of weak on ConfigMgr.
The System Center SP1 Configuration Analyzer allows you to perform some basic configuration checks on System Center 2012 SP1 servers in your environment. Here are my thoughts on the tool;
What I liked;
· You can run from a single server to any SC 2012 SP1 server
· Configuration was pretty straight forward and easy to setup
· If there is an issue, instructions on how to correct are provided
What I did not like;
· Can only export reports within the tool to XML
I like the idea of Microsoft providing a quick and simple tool to check basic configuration issues with System Center 2012 SP1. I think the ConfigMgr check is a little weak; however, most of the other checks seem to provide enough information that if something was wrong, they could be corrected using the information provided in the tool. I don’t have DPM nor Service Manger installed so I was not able to evaluate the checks.
Hope you get a chance to use it in you next System Center 2012 SP1 deployment!