Three VMs:
DC01 - Windows Server 2012, all Windows Updates installed
SQL01 - Windows Server 2012 with SQL 2012 SP1, all Windows Updates installed
- Instance Name: SCOM2012
- dynamic ports off, firewall rule for 1433 TCP Inbound is in place, 1434 UDP open in and out opened, can telnet to 1433
SCOM01 - Windows Server 2012, all Windows Updates, SCOM 2012 SP1 ISO
http://technet.microsoft.com/en-us/library/jj656654.aspx
Minimum Software Requirements
Operations Manager server features require a supported operating system. For a list of the supported operating systems for each server feature, see the Requirements by Feature section in this document.
We recommend that you check for updates and hotfixes for SQL Server. Note the following database considerations for Operations Manager:
- SQL Server 2008 R2 and SQL Server 2012 are available in both Standard and Enterprise editions. Operations Manager will function with both editions. -check
- Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server. -check
- Using a different version of SQL Server for different Operations Manager features is not supported. The same version should be used for all features. -check
- 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. - check
- The SQL Server Agent service must be started, and the startup type must be set to automatic. -check
- Side-by-side installation of System Center Operations Manager 2007 R2 reporting and System Center 2012 Service Pack 1 (SP1), Operations Manager reporting on the same server is not supported. -check
- The db_owner role for the operational database must be a domain account. If you set the SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on the operational database, the Data Access service will not be able to start. For information about how to resolve the issue, see System Center Data Access Service Start Up Failure Due to SQL Configuration Change -check
- If you plan to use the Network Monitoring features of System Center 2012 – Operations Manager, you should move the tempdb database to a separate disk that has multiple spindles. For more information, seetempdb Database. - check
I am unsure what's missing?
Thanks