Assumptions To limit the scope of material in this guide, the following assumptions have been made: This design is for use in a production environment. It is expected that a test environment will also be created to mirror the configuration of the production environment. The reader is familiar with Microsoft infrastructure solutions. This guide does not attempt to educate the reader on the features and capabilities of Microsoft products. The product documentation covers that information. The supporting infrastructure requirements for Active Directory® Domain Services (AD DS), Domain Name System (DNS), and domain space naming described in “Supporting Infrastructure” at have been reviewed and met. Operations Manager Design Process The that follow represent the most critical design elements in a well-planned Operations Manager design: Step 1: Define the Project Scope and Requirements Step 2: Determine the Number of Management Groups Step 3: Design the Operations Manager Management Server Infrastructure Step 4: Design the Operational Database Step 5: Design the Data Warehouse and Reporting Server Step 6: Design the ACS Database Server Step 7: Design the Notification System Step 8: Design the Network Connections Some of these items represent decisions that must be made. Where this is the case, a corresponding list of common response options is presented. Other items in this list represent tasks that must be carried out. These types of items are addressed because their presence is significant to complete the infrastructure design. Figure 2 provides a graphic overview of the steps involved in designing an Operations Manager infrastructure. Figure 2. The Operations Manager infrastructure decision flow Installing Operations Manager creates a management group. The management group is the basic functional unit of an Operations Manager infrastructure that can perform monitoring. Each management group contains a Microsoft SQL Server® database server to host the operational database, one or more management servers, one or more consoles, and the agents and other resources that are managed. It can also contain additional management servers and gateway servers, as well as Audit Collection Services (ACS) components. At a minimum, a management group consists of a management server, the operational database, and the data warehouse database. The management server is the focal point for administering the management group and communicating with the database. When the Operations console is opened and connected to a management group, this connects to a management server for that management group. Depending on the size of the computing environment, a management group can contain a single management server or multiple management servers.
Provide a description of a sample transaction. Assess the impact of the failure on the business. Is long-term data collection required for capacity planning, performance tracking, or trend analysis? What are the availability requirements for the monitoring infrastructure? Does the organization have any external or internal requirements for security auditing? If so, has the organization implemented a security auditing solution that satisfies these requirements? Step 1. Use Table A-2 to record the answers asked of the technical decision makers to determine the scope and requirements of the project. Table A-2. Technical Requirements Question Answer Will Microsoft System Center Virtual Machine Manager be used, with reporting enabled? What native management packs (if any) will be used? What third-party management packs (if any) will be used? What custom management packs (if any) will be used? How will they be procured? What Orchestrator integration packs (if any) will be used? Step 1. Use Table A-3 to record the answers asked of the business to determine the capacity requirements of the project. Table A-3. Capacity Requirements Type Number Location Agent-monitored computers Agentless Exception Monitoring (AEM) computers Agentless-managed computers UNIX- or Linux-based computers Network devices .NET applications monitored via Application Performance Monitoring (APM) Step 2. Use Table A-4 to record one management group. Add others only if needed for specific scenarios. A-4. Determining the Need for Additional Management Groups Scenario Yes/no Number Scaling
René Scholten – Capgemini Tigran Shahbazian – Microsoft Satya Vel – Microsoft Reza Wajih – Hewlett-Packard Editors: Laurie Dunham – Xtreme Consulting Group Dave Field – Studio B Productions Ruth Preston – Volt Technical Services Pat Rytkonen – Volt Technical Services Feedback Please direct questions and comments about this guide to .