System Center Management Pack for SharePoint Server 2013

This Management Pack enables operators and administrators to manage Microsoft SharePoint 2013 Products including SharePoint Server, Project Server, and Search Server.

File name:	Date Published:
Microsoft.Sharepoint.Server.ManagementPacks.msi	11/8/2012
Version:	File size:
15.0.4425.1000	1.2 MB

System Requirements

Supported Operating System

Windows Server 2008 R2

• Other Software: System Center Operations Manager 2007 R2 or later

Install Instructions

1. Download the MSI.
2. Double click the MSI to install.
3. View the Management Pack Guide for importing and configuration instructions.

http://www.microsoft.com/en-us/download/details.aspx?id=35590

System Center Management Pack for Windows Server Operating System

The System Center Management Pack for Windows Server Operating System provides the fundamental monitoring basics for computers running the Windows 2000 Server and Windows Server 2003, 2003 R2, 2008, 2008 R2 and 2012 Operating System.

File name:	Date Published:
OM_MP_WindowsOS.docx	5/6/2013
Version:	File size:
6.0.7026.0	146 KB

The System Center Management Pack for Windows Server Operating System consists of the following management packs: Microsoft Windows Server Library, Microsoft Windows Server 2012 Discovery, Microsoft Windows Server 2012 Monitoring, Microsoft Windows Server 2008 Discovery, Microsoft Windows Server 2008 Monitoring, Microsoft Windows Server 2008 R2 Monitoring BPA, Microsoft Windows Server Clustered Shared and Volume Monitoring, Microsoft Windows Server 2003, and Microsoft Windows 2000 Server. The System Center Monitoring Pack for Windows Server Operating System monitor the performance, health, and availability of Windows Server 2012, Windows Server 2008, 2008 R2, 2003and Windows 2000 Server.

By detecting, alerting on, and automatically responding to critical events and performance indicators, these management packs reduce resolution times for issues and increase the overall availability and performance of your systems running the Windows Server operating systems, thereby helping to reduce the total cost of ownership.

Feature Summary
• Availability
• Key Operating System Services: Required services are checked for status (for example, running, not running, or paused)
• Storage: Logical hard drives are checked for availability, sufficient free space, and integrity of the NTFS partition.
• Network: Network adapters are checked for connection health, name and IP address conflicts.
• Performance
• Processor: System processor(s) performance is checked system-wide. Processors can optionally be monitored on a per processor basis.
• Memory: Memory consisting of physical memory and virtual memory (also known as page files) is monitored using the following performance indicators:
• Available memory (in MB)
• Pages per second
• Page file percent usage
• Disks and Partitions: Logical disks/partitions and physical disks are monitored, and performance data is collected for average disk seconds per read, disk seconds per write, and disk seconds per transfer. Monitoring is also provided for fragmentation of logical disks. Depending on which version of the operating system is being monitored, either logical or physical monitoring is enabled by default. Refer to the MP guide for more detail.
• Network Adapter: Network adapters are monitored for the number of bytes received per second, the number of bytes sent per second, and the total bytes per second. In addition, the health state of the network adapter is evaluated and is set to Healthy if connected and Critical if disconnected.

The System Center Monitoring Pack for Windows Server Operating System consists of the following five management packs: Microsoft Windows Server Library, Microsoft Windows Server 2012 Discovery, Microsoft Windows Server 2012 Monitoring, Microsoft Windows Server 2008 Discovery, Microsoft Windows Server 2008 Monitoring, Microsoft Windows Server 2008 R2 Monitoring BPA, Microsoft Windows Server Clustered Shared and Volume Monitoring, Microsoft Windows Server 2003, and Microsoft Windows 2000 Server. The Microsoft Windows Server management packs monitor the performance, health, and availability of Windows Server 2012, Windows Server 2008, 2008 R2, 2003 and Windows 2000 Server.

By detecting, alerting on, and automatically responding to critical events and performance indicators, these management packs reduce resolution times for issues and increase the overall availability and performance of your systems running the Windows Server operating systems, thereby helping to reduce the total cost of ownership.


• Availability
• Key Operating System Services: Required services are checked for status (for example, running, not running, or paused)
• Storage: Logical hard drives are checked for availability, sufficient free space, and integrity of the NTFS partition.
• Network: Network adapters are checked for connection health, name and IP address conflicts.
• Performance
• Processor: System processor(s) performance is checked system-wide. Processors can optionally be monitored on a per processor basis.
• Memory: Memory consisting of physical memory and virtual memory (also known as page files) is monitored using the following performance indicators:
• Available memory (in MB)
• Pages per second
• Page file percent usage
• Disks and Partitions: Logical disks/partitions and physical disks are monitored, and performance data is collected for average disk seconds per read, disk seconds per write, and disk seconds per transfer. Monitoring is also provided for fragmentation of logical disks. Depending on which version of the operating system is being monitored, either logical or physical monitoring is enabled by default. Refer to the MP guide for more detail.
• Network Adapter: Network adapters are monitored for the number of bytes received per second, the number of bytes sent per second, and the total bytes per second. In addition, the health state of the network adapter is evaluated and is set to Healthy if connected and Critical if disconnected.
Known Issue: If the BPA monitor is enabled, then there will be an error in the PowerShell script which is a know issue in the Agent. This has been fixed in Operations Manager next update which is coming up.

Release History:

• 5/6/2013 - Update release, version 6.0.7026.0
• 9/25/2012 - Update release, version 6.0.6989.0
• 6/6/2012 - Update release, version 6.0.6972.0
• 10/18/2011- Update release, version 6.0.6958.0
• 9/30/2011 - Update release, version 6.0.6957.0
• 3/19/2010 - Updated release, version 6.0.6794.0, to resolve an issue with discoveries failing to query the Win32_PowerPlan WMI class.
• 9/18/2009 - Updated release, version 6.0.6667.0, introduced support for the Windows Server 2008 R2 Operating System and made a series of updates. Refer to the MP guide for further details.
• 10/20/2008 – Updated release, version 6.0.6321.35. Refer to the MP guide for further details.
• 7/27/2008 - Updated version, 6.0.6278.22: Introduced support for the Windows Server 2008 Operating System and addressed some issues from the previous release. Refer to the MP guide for further details.
• 5/27/2008 – Same version as released on SP1 media, version 6.0.6278.0, and released on Microsoft Download Center.
• 2/22/2008 - Updated release, version 6.0.6278.0, and released on SP1 media
• 1/15/2008 - Updated MP Guide - same version
• 11/8/2007 - Updated MP Guide - Software version still 6.0.5000.25
• 10/23/2007 - Updated MP Guide - Software Version still 6.0.5000.25
• 9/28/2007 - Updated release, version 6.0.5000.25
• 3/23/2007 - Initial Release, version 6.0.5000.0

System Requirements

Supported Operating System

Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012

Other Requirements: All management packs (MPs) included in this download are supported on System Center Operations Manager 2007 (SP1, R2).

The following should be considered when importing the management packs into a management group which does not have OpsMgr SP1 installed:

• The Library, Windows 2000 Server and Windows Server 2003 specific management packs can be imported into a management group that does not have OpsMgr 2007 SP1.
• The Windows Server 2008 specific management packs are not supported, and will not import, into a management that does not have OpsMgr 2007 Service Pack 1 installed. This is due to the fact that monitoring of Windows Server 2008 is not supported without Service Pack 1.
The Windows Server Operating System Management Pack for Operations Manager 2007 is designed to monitor the following versions of the base Operating System:


• Microsoft Windows Server 2012
• Microsoft Windows Server 2008
• Microsoft Windows Server 2008 R2
• Microsoft Windows Server 2003
• Microsoft Windows Server 2003 R2
• Microsoft Windows 2000 Server

NOTE:

• You need to install the English MP before you import localized language packs.
• Note that the localized language packs are not updated with this release, and will not import on Operations Manager 2012. The language packs will be updated in an upcoming release.
• The Microsoft.Windows.Server.Reports Management Pack will only import on systems that use SQL Server 2008 as the Database and is not currently supported on SQL Server 2005.

All support is subject to Microsoft’s overall support lifecycle (http://go.microsoft.com/fwlink/?Linkid=26134) and the Operations Manager 2007 SP1 Supported Configurations (http://go.microsoft.com/fwlink/?Linkid=90676) document.


http://www.microsoft.com/en-us/download/details.aspx?id=9296
 

System Requirements: System Center 2012 SP1 - Operations Manager

This document provides information about the operating systems, hardware configurations, software requirements, installation combinations, and security configurations for Operations Manager in System Center 2012 Service Pack 1 (SP1). This document focuses on the system requirements, and it mentions unsupported configurations only when necessary. If operating systems, hardware configurations, software requirements, installation combinations, and security configurations are not presented here, they have not been tested and are not supported.

Note
For system requirements across all components of System Center 2012 SP1, see System Requirements for System Center 2012 SP1.

The Prerequisites checker is no longer a separate option in Setup. However, you can begin the installation process to check the hardware and software prerequisites, and then cancel installation after the required prerequisites have been determined.
We recommend that you also review the key concepts of Operations Manager. Documents to review include the following:

• Release Notes for Operations Manager in System Center 2012 SP1 identifies any changes that could affect planning for a new deployment of Operations Manager in System Center 2012 SP1.
  
• Deploying System Center 2012 - Operations Manager provides detailed information about the security-related features and settings in Operations Manager that can affect your deployment.
  

This document contains the following sections:

• Operations Manager Virtualization Support
  
• Minimum Screen Resolution Requirements
  
• Minimum Hardware Requirements
  
• Minimum Software Requirements
  
• Requirements by Feature
  
  
  • Management Server
    
  • Operations Console
    
  • Web Console
    
  • Operational Database
    
  • Operations Manager Agent – Windows-Based Computers
    
  • Operations Manager Agent – UNIX- or Linux Computers
    
  • Operations Manager Reporting
    
  • Operations Manager Data Warehouse
    
  • Operations Manager Gateway Server
    
• Supported Firewall Scenarios
  
• Minimum Network Connectivity Speeds
  
• Supported Cluster Configurations
  
• Monitored Item Capacity
  
• Operations Manager Feature Firewall Exceptions
  
• Support for Languages in Addition to English
  
• Supported Network Monitoring Scenarios
  
• Application Performance Monitoring Requirements
  

Operations Manager Virtualization Support

Microsoft supports running all 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.

Minimum Screen Resolution Requirements

Operations Manager is optimized for screen resolutions of 1280 x 1024 or larger. The minimum supported screen resolution is 1024 x 768.

Minimum Hardware Requirements

Use the Operations Manager Sizing Helper to determine hardware requirements for each Operations Manager server feature. If you want to install more than one feature on the same computer, use the higher of the recommended hardware requirements for any of the combined features.
Supported Processors, Memory, and Disk Space

Note
Operations Manager does not support installing the 32-bit agent on a 64-bit operating system. Operations Manager provides native support for x86-based computers for agents and consoles, and x64-based computers for all server features and support for agents on computers with 64-bit Itanium processors.

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.
Installing Operations Manager in System Center 2012 SP1 on Windows Server 2012 Core requires Windows 32-bit on Windows 64-bit (WoW64) support, .NET 4.5, Windows PowerShell 3.0, and Server-Gui-Mgmt-Infra (the Minimal Server Interface). If you attempt to install Operations Manager without WoW64 support installed, the bootstrapper will present an error message indicating the side-by-side configuration is incorrect.
We recommend that you check for updates and hotfixes for Microsoft 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.
  
• Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server.
  
• Using a different version of SQL Server for different Operations Manager features is not supported. The same version should be used for all features.
  
• 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.
  
  
  
  The Operations Manager data warehouse installer will always install the data warehouse with SQL_Latin1_General_CP1_CI_AS regardless of the SQL Server collation. Until this issue is resolved, always install the Operations Manager data warehouse on a SQL Server with the SQL_Latin1_General_CP1_CI_AS collation. There are some compatibility issues when the Temp database on the data warehouse SQL Server instance is anything other than SQL_Latin1_General_CP1_CI_AS and the data warehouse database is SQL_Latin1_General_CP1_CI_AS. For more information about SQL Server collation setting impact and installation requirements in System Center 2012 Service Pack 1 (SP1) between Operations Manager and Service Manager, see Clarification on SQL Server Collation Requirements for System Center 2012.
  
  
  
• The SQL Server Agent service must be started, and the startup type must be set to automatic.
  
• Side-by-side installation of System Center Operations Manager 2007 R2 reporting and Operations Manager in System Center 2012 SP1 reporting on the same server is not supported.
  
• 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
  
• 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, see tempdb Database.
  

If you want to install more than one Operations Manager feature on the same computer, you must install the prerequisite software for all of the combined features.

Requirements by Feature

Management Server

• Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
  
• Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server 2012 Core Installation.
  
• Processor Architecture: must be x64.
  
• Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell version 3.0.
  
• Windows Remote Management: Windows Remote Management must be enabled for the management server.
  
• .NET Framework 4 is required. For more information, see the following document:
  
  
  • .NET Framework 4 redistributable package
    

Operations Console

• Microsoft Report Viewer 2010 Redistributable Package
  
• Disk space: %SYSTEMDRIVE% requires at least 512 MB free hard disk space.
  
• File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
  
• Server Operating System: must be Windows 7, Windows 8, Windows Server 2008 R2 SP1, or Windows Server 2012.
  
• Processor Architecture: must be x64 for servers and x64 or x86 for a client computer.
  
• Windows Installer version: at least Windows Installer 3.1.
  
• Windows PowerShell version: Windows PowerShell version 2.0. Windows PowerShell version 3.0 is required to use Windows PowerShell cmdlets for administration of UNIX and Linux computers.
  
• .NET Framework 4 is required. For more information, see the following document:
  
  
  • .NET Framework 4 redistributable package
    

Web Console

• Operating System: Windows Server 2008 R2 SP1, or Windows Server 2012.
  
• Processor Architecture: must be x64.
  
• Web browsers: Internet Explorer 8, Internet Explorer 9, Internet Explorer 10, Silverlight 5.0
  
• Internet Information Services (IIS) 7.5 and later versions, with the IIS Management Console and the following role services installed:
  
  
  • Static Content
    
  • Default Document
    
  • Directory Browsing
    
  • HTTP Errors
    
  • HTTP Logging
    
  • Request Monitor
    
  • Request Filtering
    
  • Static Content Compression
    
  • Web Server (IIS) Support
    
  • IIS 6 Metabase Compatibility
    
  • ASP.NET (both the 2.0 and 4.0 versions of ASP.NET are required.)
    
  • Windows Authentication
    
• Selected website for web console: requires a configured http or https binding.
  
  

  Important
  Installing the web console on a computer that has Microsoft SharePoint installed is not supported.

  
  
• .NET Framework 4 is required for Setup to run. For more information, see the following documents:
  
  
  • .NET Framework 4 redistributable package
    

Note
Installation of the web console requires that ISAPI and CGI Restrictions in IIS are enabled for ASP.NET 4. To enable this, select the web server in IIS Manager, and then double-click ISAPI and CGI Restrictions. Select ASP.NET v4.0.30319, and then click Allow.

Important
You must install IIS before installing .NET Framework 4. If you installed IIS after installing .NET Framework 4, you must register ASP.NET 4.0 with IIS. Open a Command prompt window by using the Run As Administrator option, and then run the following command: %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -r

Operational Database

• Disk space: The operational database must have at least 1024 MB free disk space. This is enforced at the time of database creation, and it will likely grow significantly. For information about SQL Server Planning, see Installing SQL Server 2008 or Installing SQL Server 2008 R2.
  
• File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
  
• Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server 2012 Core Installation.
  
• Processor Architecture: x64.
  
• Windows Installer version: at least Windows Installer 3.1.
  
• Microsoft SQL Server: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server 2012, SQL Server 2012 SP1.
  
• SQL Server Full Text Search is required.
  
• .NET Framework 4 is required. For more information, see the following document:
  
  
  • .NET Framework 4 redistributable package
    

Operations Manager Agent – Windows-Based Computers

• File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
  
• Operating Systems: Windows Server 2003 SP2, Windows Server 2008 SP2, Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Server 2012, Windows XP Professional x64 Edition SP2, Windows XP Professional SP3, Windows Vista SP2, Windows 7, POSReady, Windows XP Embedded Standard, Windows XP Embedded Enterprise, Windows XP Embedded POSReady, Windows 7 Professional for Embedded Systems, Windows 7 Ultimate for Embedded Systems, Windows 8 Pro or Windows 8 Enterprise.
  
• Processor Architectures: x64, x86, or IA64.
  
• Windows Installer version: at least Windows Installer 3.1.
  
• Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required for the Operations Manager agent.
  
• Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell version 3.0.
  
  

  Note
  Windows PowerShell is required for agents that will be monitored by a management pack that uses Windows PowerShell scripts.

  
  

Operations Manager Agent – UNIX- or Linux Computers

Supported operating systems:

• CentOS 5 and 6 (x86/x64)
  
• Debian Linux 5 and 6 (x86/x64)
  
• HP-UX 11i v2 and v3 (PA-RISC and IA64)
  
• IBM AIX 5.3, AIX 6.1 (POWER), and AIX 7.1 (POWER)
  
• Novell SUSE Linux Enterprise Server 9 (x86), 10 SP1 (x86/x64), and 11 (x86/x64)
  
• Oracle Solaris 9 (SPARC), Solaris 10 (SPARC and x86), and Solaris 11 (SPARC and x86)
  
• Oracle Linux 5 and 6 (x86/x64)
  
• Red Hat Enterprise Linux 4, 5, and 6 (x86/x64)
  
• Ubuntu Linux Server 10.04 and 12.04 (x86/x64)
  

Operations Manager Reporting

• Disk space: The %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
  
• Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server 2012 Core Installation.
  
• Processor Architecture: x64.
  
• Microsoft SQL Server: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server 2012, SQL Server 2012 SP1.
  
• The Remote Registry service must be enabled and started.
  
• Microsoft SQL Server Reporting Services: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server 2012, SQL Server 2012 SP1.
  
• System Center 2012 – Operations Manager supports SQL Server Reporting Services in native mode only; do not use SharePoint integrated mode.
  
• .NET Framework 4 is required. For more information, see the following document:
  
  
  • .NET Framework 4 redistributable package
    

Operations Manager Data Warehouse

• Disk space: The data warehouse database must have at least 1024 MB free hard disk space. This is enforced at the time of database creation, and the required disk space will likely grow significantly. For information about requirements in SQL Server Planning, see Installing SQL Server 2008 or Installing SQL Server 2008 R2.
  
• File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
  
• Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server 2012 Core Installation.
  
• Processor Architecture: x64.
  
• Windows Installer version: at least Windows Installer 3.1.
  
• Microsoft SQL Server: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server 2012, SQL Server 2012 SP1.
  
• SQL Server Full Text Search is required.
  
• .NET Framework 4 is required for Setup to run. For more information, see the following document:
  
  
  • .NET Framework 4 redistributable package
    

Operations Manager Gateway Server

• Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
  
• Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server 2012 Core Installation.
  
• Processor Architecture: must be x64.
  
• Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell version 3.0.
  
• Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required for the management server.
  
• .NET Framework 4 is required if the Gateway server manages UNIX/Linux agents or network devices.
  

Supported Firewall Scenarios

The following table shows Operations Manager feature interaction across a firewall, including information about the ports that are used for communication between the features, which direction to open the inbound port, and whether the port number can be changed.
Firewall Scenarios for Operations Manager in System Center 2012 SP1

Operations Manager Feature A	Port number and direction	Feature B	Configurable	Note
Management server	1433 --->	Operational database	Yes (Setup)
Management server	1434 UDP < ---	Operational database	No	If the operational database is installed on a named instance of SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server 2012, or SQL Server 2012 SP1 such as in a cluster, and the Windows Firewall is enabled on the management server, you have to also open UDP 1434 inbound on the management server.
Management server	1433 --->	Operational database	Yes (Setup)
Management server	5723, 5724 --->	Management server	No	Port 5724 must be open to install this feature and can be closed after this feature has been installed.
Management server	1433 -->	Reporting data warehouse	No
Management server	1433 --->	Reporting data warehouse	No
Reporting server	5723, 5724 --->	Management server	No	Port 5724 must be open to install this feature and can be closed after this feature has been installed.
Operations console	5724 --->	Management server	No
Connector Framework source	51905 --->	Management server	No
Web console server	Selected web site port --->	Management server	No
Web console (for Application Diagnostics	1433, 1434 --->	Operational database	Yes (Setup)
Web console (for Application Advisor)	1433, 1434 --->	Data warehouse	Yes (Setup)
Web console (for Application Advisor)	80 --->	SQL Server Reporting Services	No
Web console browser	80, 443 --->	web console server	Yes (IIS Admin)	Default for HTTP or SSL. For either Network Authentication or Mixed Authentication, an account name and password can be sent as part of the request. We recommend you use SSL.
Agent installed by using MOMAgent.msi	5723 --->	Management server	Yes (Setup)
Agent installed by using MOMAgent.msi	5723 --->	Management server	Yes (Setup)
Agent installed by using MOMAgent.msi	5723 --->	Gateway server	Yes (Setup)
Gateway server	5723 --->	Management server	Yes (Setup)
Agent (Audit Collection Services (ACS) forwarder)	51909 --->	Management server Audit Collection Services (ACS) Collector	Yes (Registry)
Agentless Exception Monitoring data from client	51906 --->	Management server Agentless Exception Monitoring (AEM) file share	Yes (Client Monitoring Wizard)
Customer Experience Improvement Program data from client	51907 --->	Management server (Customer Experience Improvement Program) Endpoint	Yes (Client Monitoring Wizard)
Operations console (reports)	80 --->	SQL Server Reporting Services	No	The Operations console uses port 80 to connect to the SQL Server Reporting Services website.
Reporting server	1433 --->	Reporting data warehouse	Yes
Management server (Audit Collection Services Collector)	1433 --->	Audit Collection Services (ACS) database	Yes
Management Server	161, 162 <--->	Network device	Yes	All firewalls between the management servers in the resource pool and the network devices need to allow SNMP (UDP) and ICMP bi-directionally, and ports 161 and 162 need to be open bi-directionally. This includes Windows Firewall on the management server itself. If your network devices are using a port other than 161 and 162, you need to open bi-directional UDP traffic on these ports as well.
Management server or gateway server	1270 --- >	UNIX or Linux computer	No
Management server or gateway server	22 --- >	UNIX or Linux computer	Yes

In the preceding table, if SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server 2012, or SQL Server 2012 SP1 is installed by using a default instance, the port number is 1433. If SQL Server is installed with a named instance, it is probably using a dynamic port. To identify the port, do the following:

1. Run SQL Server Configuration Manager.
   
2. Open SQL Server Network Configuration.
   
3. Open Protocols for INSTANCE1 (or the instance that is running under it).
   
4. Open TCP/IP.
   
5. Click IP Addresses.
   
6. The port is under IPAll (usually the TCP Dynamic Ports).
   

Minimum Network Connectivity Speeds

Operations Manager requires the following minimum network connectivity speeds between the specified features.

Feature A	Feature B	Minimum requirement
Management server	Agent	64 Kbps
Management server	Agentless	1024 Kbps
Management server	Database	256 Kbps
Management server	Console	768 Kbps
Management server	Management server	64 Kbps
Management server	Data warehouse database	768 Kbps
Management server	Reporting server	256 Kbps
Management server	Gateway server	64 Kbps
Local management group	Connected management group (tiered)	1024 Kbps
Web console server	web console	128 Kbps
Reporting Data Warehouse	Reporting server	1024 Kbps
Console	Reporting server	768 Kbps
Audit collector	Audit database	768 Kbps

Supported Cluster Configurations

Operations Manager supports the clustering configurations for Operations Manager features as shown in the following table:

Important
Clustering of management servers is not supported in System Center 2012 Service Pack 1 (SP1), Operations Manager.

Only Cluster service quorum node clusters are supported. Multisite clusters (geographically dispersed clusters) are supported for all Operations Manager cluster roles. You can use replication technology to help provide high availability for data in Operations Manager, but the latency of communications between components introduce risks to data replication and might introduce failover issues. We recommend that you use synchronous mirroring of data disks between sites. Synchronous mirroring means that the data is fully synchronized across all sites and ensures the correct behavior of applications in the event of failover across sites.

Important
Microsoft is not obligated to release a hotfix on any Operations Manager issue that cannot be reproduced in a non-multisite cluster environment. If an analysis determines that non-Microsoft components in the configuration are causing the issue, the customer must work with the appropriate vendor for those components.

Server Feature	Cluster	Notes
Operations Manager Operational database	Single Active-Passive cluster	Other Operations Manager features must not be installed on the cluster or nodes of the cluster.
Operations Manager Reporting data warehouse	Single Active-Passive cluster	Other Operations Manager features must not be installed on the cluster or nodes of the cluster.
Audit Collection Services (ACS) database	Single Active-Passive cluster	Other Operations Manager features must not be installed on the cluster or nodes of the cluster.

Supported, But Not Recommended Cluster Configurations

Operations Manager supports the following clustering configurations for Operations Manager server roles, as shown in the following table; however, because of a potential performance effect on your computer running SQL Server, these configurations are not recommended:

Server Feature	Cluster	Notes
Operations Manager operational database and Operations Manager Reporting data warehouse.	Active-Active cluster where the operational database is installed on one node of the cluster and the Reporting data warehouse is installed on the other node of the cluster.	There might be some performance issues with SQL Server in this configuration.
Operations Manager operational database, Reporting data warehouse, and Audit Collection Services (ACS) database.	Single Active-Passive or Active-Active cluster where all three components are on a single cluster.	There might be some performance issues with SQL Server in this configuration.
Operations Manager operational database and Audit Collection Services database.	Single Active-Passive cluster where both components are on a single cluster.	There might be some performance issues with SQL Server in this configuration.
Operations Manager operational database and Reporting data warehouse.	Single Active-Passive cluster where both components are on a single cluster.	There might be some performance issues with SQL Server in this configuration.
Reporting data warehouse and Audit Collection Services database.	Single Active-Passive cluster where both components are on a single cluster.	There might be some performance issues with SQL Server in this configuration.

Monitored Item Capacity

Operations Manager supports the following number of monitored items.

Monitored item	Recommended limit
Simultaneous Operations consoles	50
Agent-monitored computers reporting to a management server	3,000
Agent-monitored computers reporting to a gateway server	2,000
Agentless Exception Monitored (AEM)-computers per dedicated management server	25,000
Agentless Exception Monitored (AEM)-computers per management group	100,000
Collective client monitored computers per management server	2,500
Management servers per agent for multihoming	4
Agentless-managed computers per management server	10
Agentless-managed computers per management group	60
Agent-managed and UNIX or Linux computers per management group	6,000 (with 50 open consoles); 15,000 (with 25 open consoles)
UNIX or Linux computers per dedicated management server	500
UNIX or Linux computers monitored per dedicated gateway server	100
Network devices managed by a resource pool with three or more management servers	1,000
Network devices managed by two resource pools	2,000
Agents for Application Performance Monitoring (APM)	700
Applications for Application Performance Monitoring (APM)	400
URLs monitored per dedicated management server	3000
URLs monitored per dedicated management group	12,000
URLs monitored per agent	50

Operations Manager Feature Firewall Exceptions

Feature	Exception	Port and protocol	Configured by
Management server	System Center Management service System Center Data Access service Operations Manager Connector Framework Operations Manager Customer Experience Improvement Operations Manager Application Error Monitoring	5723/TCP 5724/TCP 51905/TCP 51907/TCP 51906/TCP	Setup Setup Setup Setup Setup
Web console	Operations Manager web console	Selected web site port/TCP	Setup
Web console, http	World Wide Web Services, http	80/TCP	Windows Firewall
Web console, https	Secure World Wide Web Service, https	443/TCP	Windows Firewall
Operational database	SQL Server database server If using a named instance, add.	1433/TCP 1434/UDP	Windows Firewall Windows Firewall
Operations Manager data warehouse database	SQL Server database server If using a named instance, add.	1433/TCP 1434/UDP	Windows Firewall Windows Firewall
Operations Manager Reporting	SQL Server Reporting Services	80/TCP	Windows Firewall
Agent, manual installation of MOMAgent.msi	System Center Management service	5723/TCP	Windows Firewall
Agent, push installation	System Center Management service File and Print Sharing Remote Administration	5723/TCP 137/UDP, 138/UDP, 139/TCP, 445/TCP 135/TCP, 445/TCP	Windows Firewall Windows Firewall Windows Firewall
Agent, pending repair	System Center Management service File and Print Sharing Remote Administration	5723/TCP 137/UPD, 138/UPD, 139/TCP, 445/TCP 135/TCP, 445/TCP	Windows Firewall Windows Firewall Windows Firewall
Agent, pending upgrade	System Center Management service File and Print Sharing Remote Administration	5723/TCP 137/UDP, 138/UDP, 139/TCP, 445/TCP 135/TCP, 445/TCP	Windows Firewall Windows Firewall Windows Firewall
Gateway	System Center Management service	5723/TCP	Setup
Operations Manager Audit Collection Services database	SQL Server If using a named instance, add.	1433/TCP 1434/UDP	Windows Firewall Windows Firewall
Operations Manager Audit Collection Services Collector	ACS Collector Service	51909/TCP	Windows Firewall

Support for Languages in Addition to English

Operations Manager supports the following languages: English, German, French, Japanese, Spanish, Simplified Chinese, Russian, Italian, and Portuguese (Brazil).
Support for different languages
If your systems run a language other than English, you can install Operations Manager for that language. You also have the option of installing English Operations Manager for your management group.
For example, if you use a German version of a Windows operating system on all your servers, you can install German Operations Manager features for your entire management group. If you have a German version of a Windows operating system on all your servers, you can optionally install English Operations Manager features for your entire management group.
Agents for different languages
If you use an English management group, you can monitor any Windows Operating System Locale type.
If you use another language, you can monitor Windows operating systems for English and that language. For instance, if you use a German management group, you can monitor only English and German Windows operating systems.
Console for different languages
Operations Manager consoles are language independent. For example, you can use an Italian Operations Manager console to connect to a German management group.

Supported Network Monitoring Scenarios

Operations Manager supports monitoring of network devices that support Simple Network Management Protocol (SNMP). Port monitoring is available for devices that have implemented the interface MIB (RFC 2863) and MIB-II (RFC 1213) standards. In addition, peripheral monitoring, including processor and memory monitoring, is supported on a subset of devices. For more information, see System Center Operations Manager 2012: Network Devices with Extended Monitoring Capability.
Operations Manager can identify connected devices in a recursive discovery that use an IPv6 address; however, the initial device that is discovered must use an IPv4 address.
For more information about supported network devices, see Network Devices Supported for Discovery by Operations Manager 2012.

Application Performance Monitoring Requirements

To view Application Performance Monitoring event details, you must install the Operations Manager web console. For more information, see How to Install the Operations Manager Web Console.
Application Performance Monitoring requires the following software:

• .NET Framework 2.0, .NET Framework 3.5, .NET Framework 3.5 SP1, .NET Framework 4, or .NET Framework 4.5.
  
• Internet Information Services (IIS) 7.0. Application monitoring on a clustered IIS configuration is not supported.
  
• ISAPI and CGI Restrictions in IIS be enabled for ASP.NET 4.0. To enable this, select the web server in IIS Manager, and then double-click ISAPI and CGI Restrictions. Select ASP.NET v4.0.30319, and then click Allow.
  

Additionally, you must start the SQL Server Agent service and set the startup type to automatic.

What's New in System Center 2012 SP1 - Operations Manager

System Center 2012 Service Pack 1 (SP1), Operations Manager has a number of new capabilities and changes outlines in this document. We urge you to read the Release Notes for Operations Manager in System Center 2012 SP1 for details about known issues.
New capabilities include improvements to .NET Application Performance Monitoring (APM), Audit Collection Service (ACS), and UNIX and Linux monitoring.

New Monitoring Capabilities

Monitoring Windows Services Built on the .NET Framework

One of the most commonly requested features that was present in AVIcode, but not yet re-implemented in System Center 2012 – Operations Manager was the ability to monitor Windows Services, not just IIS-hosted applications. This is now possible again, and integrated into the APM template.

Automatic Discovery of ASP.NET MVC3 and MVC4 Applications

If the application contains “System.Web.Mvc.dll” in the /bin subfolder, it is now automatically discovered as an ASP.NET Web Application without the need to use the overrides that were documented in the APM.WEB.IIS7.mp Guide. For more information, see Configuring the Management Pack for Operations Manager APM Web IIS 7.

New Transaction Types: MVC Pages and WCF Methods

New transaction types have been introduced for MVC pages and for MVC methods. This augments the capability to specify more detailed settings for a given feature of your application. How to use this feature is documented in the APM template documentation.

Comparing Transaction Monitoring

Here is a comparison of the transactions you can monitor using System Center 2012 – Operations Manager and those you can monitor using the Operations Manager Beta version of System Center 2012 Service Pack 1 (SP1).

Component type	Transactions you can monitor using System Center 2012 – Operations Manager	Transactions you can monitor using The Operations Manager Beta version of System Center 2012 Service Pack 1 (SP1)
ASP.NET web application	ASP.NET webpage ASP.NET web service Function	ASP.NET webpage ASP.NET MVC page ASP.NET web service WCF method Function
ASP.NET web service	ASP.NET webpage ASP.NET web service Function	ASP.NET webpage ASP.NET MVC page ASP.NET web service WCF method Function
WCF service	No transactions allowed	ASP.NET webpage ASP.NET MVC page ASP.NET web service WCF method Function
Windows Service	Component type did not exist	WCF method Function

Enabled APM of SharePoint 2010

Operations Manager lets you monitor SharePoint web front-end components. You can monitor standard and custom SharePoint webpages for performance degradation and server-side exceptions. You can set up monitoring for SharePoint applications in much the same way you enable monitoring for other .NET web applications. Use the .NET Application Performance Monitoring template to configure SharePoint application monitoring. When monitoring SharePoint applications for exceptions, the exception call stack contains the relevant SharePoint specific parameters for troubleshooting.

Integration with Team Foundation Server 2010 and Team Foundation Server 2012

To speed interactions between operations and development, it is essential to quickly detect and fix problems that might need assistance from the engineering team. System Center 2012 Service Pack 1 (SP1), Operations Manager can integrate with development tools, such as Team Foundation Server (TFS) and Visual Studio, enabling deep troubleshooting and streamlining communications between developers and IT operations. You can synchronize Operations Manager alerts and Team Foundation Server (TFS) work items. Operations Manager integration with TFS introduces a new work item type definition, Operational Issue, which can be embedded into any of your organization’s engineering processes. After enabling synchronization, IT operations can manually assign alerts to the engineering team. Assigning an alert to engineering creates a new work item in Team Foundation Server. The workflow tracks and synchronizes changes made to TFS work items and changes made to associated alerts in Operations Manager.
Compared to the Microsoft Visual Studio Team Foundation Server 2010 Work Item Synchronization management pack, SP1 features include:

• Shipped as part of Operations Manager, included in the SP1 Media
  
• Improved security – synchronization account no longer requires TFS administrative rights
  
• Improved design of the Operational Issue WITD
  
• Improved design of the configuration Wizard
  
• Introduced support for TFS Area Path
  
• Support for default Team Projects
  
• Synchronization for new APM alert types from IIS8 web applications, WCF, Windows Services, and also for non-APM alerts
  
• Localization of Wizard UI and MP elements, and compatibility with localized versions of TFS
  
• Synchronize file attachments that can reside on a network file share or appended to TFS work items.
  
• Automatically route and close alerts to TFS
  
• IT operations can open TFS work items directly from the Operations Manager console using built-in integration with TFS web UI.
  

Conversion of Application Performance Monitoring events to IntelliTrace format

This new monitoring capability allows for opening of APM exception events from Visual Studio IDE as if the exception was captured during the IntelliTrace historical debugging session. Developers can stay within their familiar environment to examine complete exception call stack, for example: method parameters captured at the time of exception, and can navigate between the source code modules that participated in the exception call chain. Tightly integrated with TFS Work Item Synchronization Management Pack, this capability instantaneously brings generated IntelliTrace logs to TFS work items assigned to engineering. This can result in streamlining communications between IT Operations and Development and enriching the development experience with analysis of root causes of the application failure, reducing the mean time to recovery (MTTR) for the problems detected by APM.
Features include:

• APM exception events can be saved in IntelliTrace file format directly from Application Diagnostics
  
• Debug Symbols can be late-bound in Visual Studio 2012 allowing developers to navigate through source code, even when the production environment has no symbols loaded
  
• Developers can see one level of parameters that are converted and visible in the Visual Studio 2012 Ultimate Locals window, and displayed in the context of the selected call stack frame
  
• Developers can see additional method specific information (i.e. a connection string for ExecuteReader() method) in the Visual Studio 2012 Locals window in the context of the selected call stack frame
  
• Traces are automatically attached to APM exception events and can be automatically added to TFS work items or stored on a network file share. Developers can open traces using Visual Studio 2012 Ultimate and troubleshoot application problems while staying in their development environment.
  

Collecting Historical Traces Using IntelliTrace Profiling Management Pack

System Center 2012 SP1 – Operations Manager includes IntelliTrace Profiling Management Pack. This management pack lets you capturing historical traces directly from the Operations Manager console. These traces can help developers investigate problems by giving them visibility to application execution history without the developers needing access to the servers where the applications ran. Developers can use Visual Studio 2012 Ultimate to open collected traces.
IntelliTrace Profiling Management Pack automatically deploys the necessary infrastructure, IntelliTrace Collector, to the designated servers. When traces are collected, they are uploaded to a network file share and attached to Operations Manager alerts. Traces are uploaded to the management server using the same secure Operations Manager channel that agents use to communicate with the management servers. By configuring Team Foundation Server (TFS) synchronization, traces can be automatically added or linked to TFS work items.

New Management Packs and Support for Windows Server 2012 and IIS 8

To use APM with Windows Server 2012, you must import the following management packs:

• Microsoft.Windows.Server.Library version 6.0.6989.0 or newer
  
• Microsoft.Windows.Server.2012.Discovery version 6.0.6989.0 or newer
  
• Microsoft.Windows.InternetInformationServices.CommonLibrary version 7.0.8862.0 or newer
  
• Microsoft.Windows.InternetInformationServices.2012 version 7.0.8862.0 or newer
  
  

  Important
  If you had previously imported the Microsoft.Windows.InternetInformationServices.6.2 management pack, which was part of the Windows 8 Beta management pack release, it should be removed first.

  
  

Also, from the /ManagementPacks folder of the System Center 2012 – Operations Manager media, you should import Microsoft.SystemCenter.Apm.Web.IIS8. This is the equivalent of the Microsoft.SystemCenter.Apm.Web.IIS7 management pack, which was previously (and still is) used for IIS7.
These management pack versions to be used are specific to System Center 2012 Service Pack 1 (SP1), Operations Manager. Other than these specific prerequisites, how to use this feature is documented in the APM template documentation and the experience is identical to configuring APM for an IIS7-hosted application.

360 .NET Application Monitoring Dashboards

System Center 2012 Service Pack 1 (SP1), Operations Manager can show you different perspectives of application health in one place—360 .NET Application Monitoring Dashboards. The 360 .NET Application Monitoring Dashboards display information from Global Service Monitor, .NET Application Performance Monitoring, and Web Application Availability Monitoring to provide a summary of health and key metrics for 3-tier applications in a single view. The 360 .NET Application Monitoring Dashboards show where an application is unhealthy and provide a launch point for detail dashboards that highlight component-level issues.
The 360 .NET Application Monitoring Dashboards display data from powerful monitoring tools. .NET Application Performance Monitoring looks deep into the application to get details that can help you pinpoint solutions from server- and client-side perspectives. Web Application Availability monitoring in Operations Manager monitors internal synthetic transactions. Global Service Monitor monitors the availability of applications from an outside location, measuring availability from where the user is.
The 360 .NET Application Monitoring Dashboards show the following:

Key application metric or action	Type of monitoring used
Availability	Web Application Availability Monitoring and Global Service Monitor
Reliability	.NET Application Performance Monitoring
Performance	.NET Application Performance Monitoring and Global Service Monitor
Diagnostics	.NET Application Performance Monitoring
Resolution	The Team Foundation Server (TFS) Connector management pack takes an alert, assigns it to development in TFS with all appropriate detail.

ACS support for Dynamic Access Control

Windows Server 2012 enables business data owners to easily classify and label data allowing access policies to be defined for data classes that are critical to business. Compliance management in Windows Server 2012 becomes more efficient and flexible because access and audit policies can be based not only on user and group information but a richer set of user, resource and environmental claims, and properties from Active Directory and other sources. User claims such as roles, projects, organization, resource properties such as secrecy, and device claims such as health can be used in defining access and audit policies.
Windows Server 2012 enhances the existing Windows ACL model to support Dynamic Access Control where customers can define an expression based authorization access policy that includes conditions using user and machine claims, as well as resource (for example, file) properties. The following illustration is descriptive, and not an actual representation of an expression:

• Allow Read and Write access if User.Clearance >= Resource.Secrecy and Device. Healthy
  
• Allow Read and Write access if User.Project any_of Resource.Project
  

System Center 2012 Service Pack 1 (SP1) contributes to the fulfilling these scenarios by providing enterprise-wide visibility into the use of the Dynamic Access Control, leveraging Operations Manager’s Audit Collection Services to collect events from the relevant machines (file servers, domain controllers) and providing reporting to enable auditors and compliance officers to report on the use of Dynamic Access Control – for example, audit changes in policies, object access (success and failure), and “what-if” assessment of what would happen if a certain policy were applied.

Additional UNIX and Linux Monitoring Capabilities

Support for CentOS, Debian, Oracle, and Ubuntu Linux

System Center 2012 Service Pack 1 (SP1), Operations Manager has added support for monitoring of the following Linux operating systems:

• CentOS 5 (x86/x64)
  
• CentOS 6 (x86/x64)
  
• Debian 5 (x86/x64)
  
• Debian 6 (x86/x64)
  
• Oracle Linux 5 (x86/x64)
  
• Oracle Linux 6 (x86/x64)
  
• Ubuntu Server 10.04 (x86/x64)
  
• Ubuntu 12.04 (x86/x64)
  

Support for these operating systems is implemented with the “Universal Linux” monitoring packs. Import the following MP files to enable monitoring of the new Linux operating systems:

• Microsoft.Linux.Universal.Library.mp
  
• Microsoft.Linux.Universal.Monitoring.mp
  
• Microsoft.Linux.UniversalD.1.mpb (to support Debian and Ubuntu Linux agents)
  
• Microsoft.Linux.UniversalR.1.mpb (to support CentOS Linux agents)
  

Improved Heartbeat Monitoring

Heartbeat monitors for Operations Manager UNIX and Linux agents now support configurable “MissedHeartbeats” – allowing for a defined number of failed heartbeats to occur before generating an alert. Failed heartbeats will now cause Operations Manager to unload rules and monitors for UNIX and Linux agents until the heartbeat is restored. This makes it very easy to identify UNIX and Linux computers with failed heartbeats in the Operations Manager console.