Everyone knows (I hope so) about Configuration Analyzer for System Center SP1.Previously, we had to download and use separate BPA analyzer for each SC component.But now, it’s the single model for testing System Center configuration. According with technet, main requirements are: Microsoft Baseline Configuration Analyzer 2.0 and operation system required for SC SP1. In my opinion, requirements are not accurate.
After successful installation BCA 2.0 and CA fo SC SP1 you can receive following errors:
The BPA cannot connect to the VMM management server __. Please start the service and try again
Cmdlet Invoke-MbcaModel reported warning …. cannot be loaded because running scripts is disabled on this system.
To fix errors you should run cmdlet Set-Execution:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
To prevent errors during analyzing remote servers:
Enable-PsRemoting -Force
So, additional requirements :
your system able to receive Windows PowerShell remote commands that are sent by using the WS-Management
you can run downloaded powershell scripts by trusted publisher
demo\scom.aa – Action service account
demo\scom.dw – Data Writer
demo\scom.dr – Data Reader
demo\scom.das – Data Action Service Account
Prepare SQL Server:
SCOM requires at least SQL Server 2008 R2 (for SCOM 2012) and 2008 R2 SP1 (SCOM 2012 SP1)
Using a different version of SQL Server for different Operations Manager features is not supported
SQL Server collation settings for all databases must be one of the following: SQL_Latin1_General_CP1_CI_AS, French_CI_AS, Cyrillic_General_CI_AS, Chinese_PRC_CI_AS, Japanese_CI_AS, Traditional_Spanish_CI_AS, or Latin1_General_CI_AS. No other collation settings are supported
For SCOM Operational Database you must have:
Supported version of SQL Server
Installed Database Services with SQL Server Full Text Search feature!
For SCOM Reporting:
Supported version of SQL Server
Installed and configured Reporting Services
Important: if you planning SCOM Reporting component you MUST install one locally on SQL Server with Reporting services. Don’t try to install Reporting remotely to SQL instance. (honestly, I tried :)). You will receive: NO SSRS Instances on SCOM MS Server.
I won’t show you how to install SQL Server. Just don’t forget to meet all requirements above.
Prepare SCOM server:
1) Install supported server OS (in my case, server 2012 Std)
2) Join to domain
Basically, SCOM uses the management server action account (scom.aa) and System Center Data Access service account (scom.das). You can use one account for both services, but Microsoft recommends to use two separate accounts for the best security. If you install Reporting SCOM component , you are prompted for two additional accounts, the Data Warehouse Write account (scom.dww) and the Data Reader account (scom.dr). Scom.aa and scom.das must be added to the local Administrators group on Management server and Operational Database. Scom.dww and scom.dr must have logon rights on SQL server where operational and reporting databases located.
6) I believe you already installed SQL Server instance and we are ready to add some changes for supporting communication between SCOM and SQL. The main goal my article to show you how we can use powershell and why it’s so cool. The first answer is we can do evertything without additional connections (RDP or something) to management servers. Just create Powershell remote session and go!go!go! 🙂 .
7) Create firewall rules on SQL Server. Standart ports pack for SQL Server : 1433- database service, 1434 – sql browser, 4020 – sql broker. Additionally, we have to enable on WMI-WINMGMT-In-TCP rule. Then we add SCOMLocaladm group to Administrators group on SQL Server and create SQL logins for SCOM Data reader and SCOM Data Write accounts