System Center 2012 Operations Manager Sizing Helper Tool
SCOM virtualization:
• For performance reasons, Microsoft recommends storing both the operational and warehouse databases on a directly attached physical hard drive and not a virtual disk.
• Hypervisor snapshots and writing changes to a temporary virtual hard drive are not supported.
• System Center 2012 R2 Operations Manager runs on virtual machines in Microsoft Azure just as it does on physical computer systems.
SCOM OS:
• Server Operating System Requirements for System Center 2012 R2
• Installing System Center 2012 R2 Operations Manager on Windows Server 2012 Core requires:
• • Windows 32-bit on Windows 64-bit (WoW64) support, .NET 4.5, Windows PowerShell 3.0.
• • In addition, you need AuthManager. To install AuthManager for Windows 2012, add Server-Gui-Mgmt-Intra (the Minimal Server Interface.) To install for Windows 2012 R2, install AuthManager with this command: dism /online /enable-feature /featurename:AuthManager.
• Operations Manager does not support installing the 32-bit agent on a 64-bit operating system.
SCOM SQL DB:
• SQL Server Requirements for System Center 2012 R2
• 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.
• The SQL Server Agent service must be started, and the startup type must be set to automatic.
• 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.
• 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.
• If SQL is shared (e.g. with SCCM), SCOM will need its own SQL instance.
• If you are using a remote SQL server, do not install the SCOM 2012 Reporting Server component on the SCOM server, but run the SCOM setup on the SQL server and install it there.
• Although SQL Server Reporting Services is installed on the stand-alone server, Operations Manager reports are not accessed on this server; instead, they are accessed in the Reporting workspace in the Operations console. If you want to access published reports via the web console, you must install the Operations Manager web console on the same computer as Operations Manager Reporting server.
• No other applications that are using SQL Server Reporting Services can be installed on this instance of SQL Server.
And also:
• Clustering of management servers is not supported in System Center 2012 R2 Operations Manager.
• To view Application Performance Monitoring event details, you must install the Operations Manager web console.
Important recommended limits:
Agent-monitored computers reporting to a management server: 3000
Agentless-managed computers per management server: 10
URLs monitored per dedicated management server: 3000
UNIX or Linux computers per dedicated management server: 500
Network devices managed by a resource pool with three or more management servers: 1000
SCOM prerequisites:
Microsoft System CLR Types for SQL Server 2012
The Report Viewer controls (Operations console)
.NET Framework 4
.NET Framework 4 > HTTP Activation
Windows PowerShell v2 or v3
Windows Remote Management (Management Server)
Windows Installer 3.1
Remote Registry service (Operation Manager reporting)
IIS 7.5 or later, with the IIS Management Console (Web Console):
• Default Document
• Directory Browsing
• HTTP Errors
• Static Content
• HTTP Logging
• Request Monitor
• Static Content Compression
• Request Filtering
• Windows Authentication
• ASP.NET 3.5
• ASP.NET 4.5
• IIS 6 Metabase Compatibility
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.
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
SCOM SQL requirements:
Microsoft SQL Server Database Engine
Microsoft SQL Server Full Text Search
Microsoft SQL Server Reporting Services
Microsoft SQL Server Management Console
SCOM service accounts:
SCOM Action account
SCOM SDK account
SCOM Reporting account
SCOM SQL account
Problems:
An SQL instance for SSRS is missing: Ensure the SCOM Reporting Server component is being installed on the SQL server and not on SCOM itself (unless it runs SQL locally) and the SSRS is not used by any other application.
How to Install the Operations Manager Reporting Server
Preparing your environment for System Center 2012 R2 Operations Manager
No comments:
Post a Comment