So I’ve spent most of this week working on an infrastructure plan and design for System Center 2012 R2 and I wanted to share with you the resources that I found helpful in this endeavor.
The initial plan focuses around Configuration Manager and Operations Manager only, and rather than dump everything into a single post I’ve decided to break them up; so stay tuned for future posts on this topic. Once SCCM and SCOM have been implemented I’ll likely be exploring the other System Center products as well and will continue the series accordingly.
Everyone’s environment is different so I won’t make any specific recommendations, but hopefully this will serve as a useful resource to help you plan your own System Center deployments.
This first post in the System Center 2012 R2 Infrastructure Planning series focuses on Operations Manager and a few SQL Server references that I found handy.
In no particular order….
System Requirements/Firewall Exceptions
“Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server.”
“SQL Server collation settings for all databases must be one of the following: SQL_Latin1_General_CP1_CI_AS; Latin1_General_100_CI_AS, // EN, IT, DE, PT-BR, NE, PT-PT; French_CI_AS; French_100_CI_AS; Cyrillic_General_CI_AS; Chinese_PRC_CI_AS; Chinese_Simplified_Pinyin_100_CI_AS, // CN simplified; Chinese_Traditional_Stroke_Count_100_CI_AS, // CN traditional, CN-HKJapanese;_CI_AS; Japanese_XJIS_100_CI_AS; Traditional_Spanish_CI_AS; Modern_Spanish_100_CI_AS; or Latin1_General_CI_AS; Cyrillic_General_100_CI_AS, // RU; Korean_100_CI_AS; Czech_100_CI_AS; Hungarian_100_CI_AS; olish_100_CI_AS; and Finnish_Swedish_100_CI_AS. No other collation settings are supported.”
“If you plan to use the Network Monitoring features of System Center 2012 R2 Operations Manager, you should move the tempdb database to a separate disk that has multiple spindles.”
Distributed Deployment of Operations Manager
Single Server Deployment of Operations Manager
Considerations for High Availability and Disaster Recovery
“You should always have two management servers in ANY environment. A second management server allows for failover and easy restore, and a second management server can take on the load if one fails. All management servers are members of the All Management Servers Resource pool, which balances the monitoring load of your management group as new management servers are added, and provides automatic failover for monitoring. The impact of failure of a management server in a distributed environment is minimized, but it increases the workload on additional management servers in the management group until the failed management server is restored.”
System & Database Sizing Helper Tool
Audit Collection (ACS) Database Size Calculator
Operations Manager and VMware…
“Microsoft supports running all System Center 2012 – Operations Manager server features in any physical or virtual environment that meets the minimum requirements that are stated in this document. However, for performance reasons, we recommend that you store the operational database and data warehouse database on a directly attached physical hard drive, and not on a virtual disk. Specifically, virtual computers that are running any Operations Manager server feature must not use any functionality that does not immediately commit all activity on the virtual computer to the virtual hard drive. This includes making use of point-in-time snapshots and writing changes to a temporary virtual hard drive. This is true for every virtualization technology that is used with Operations Manager.”
Understanding and modifying Data Warehouse Retention and Grooming
How to Configure Grooming Settings for the Reporting Data Warehouse Database
Database Size Limits…
Network Bandwidth Utilization for OpsMan 2007
Audit Collection Services Capacity Planning
Collecting Security Events Using Audit Collection Services in Operations Manager
How to Install the Operations Manager Reporting Server
Management Packs Installed with Operations Manager
Hardware and Software Requirements for Installing SQL Server
Managing SQL Server Workloads with Resource Governor
Considerations for Installing Reporting Services