OpsMgr 2012: a quickstart deployment guide

Courtesey-http://blogs.technet.com/b/kevinholman/archive/2012/04/26/deploying-opsmgr-2012-a-quick-start-guide.aspx

http://technet.microsoft.com/en-us/library/hh298609.aspx

http://technet.microsoft.com/en-us/library/jj656656.aspx

http://technet.microsoft.com/en-US/library/jj656654.aspx

 

Prerequisites:

 

1. Install Windows Server 2008R2 SP1 to all Servers

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

SQL Prerequisites

SQL Server 2008 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 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 System Center 2012 Service Pack 1 (SP1), Operations Manager 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.

 

SQL Installation methods

Install SQL 2008 R2 to the DB server role

• Setup is fairly straightforward. This document will not go into details and best practices for SQL configuration. Consult your DBA team to ensure your SQL deployment is configured for best practices according to your corporate standards.
• Run setup, choose Installation > New Installation…
• When prompted for feature selection, install ALL of the following:
  • Database Engine Services
  • Full-Text Search
  • Reporting Services
• Optionally – consider adding the following to ease administration:
  • Business Intelligence Development Studio (for custom report development)
  • Management Tools – Basic and Complete (for running queries and configuring SQL services)
• On the Instance configuration, choose a default instance, or a named instance. Default instances are fine for testing and labs. Production clustered instances of SQL will generally be a named instance. For the purposes of the POC, choose default instance to keep things simple.
• On the Server configuration screen, set SQL Server Agent to Automatic. Click “Use the same account for all SQL Server Services, and input the SQL service account and password we created earlier.
• On the Collation Tab – make sure SQL_Latin1_General_CP1_CI_AS is selected, as that is the ONLY collation supported.
• On the Account provisioning tab – add your personal domain user account or a group you already have set up for SQL admins. Alternatively, you can use the OMAdmins global group here. This will grant more rights than is required to all OMAdmin accounts, but is fine for testing purposes of the POC.
• On the Data Directories tab – set your drive letters correctly for your SQL databases, logs, TempDB, and backup.
• On the Reporting Services Configuration – choose to install the native mode default configuration. This will install and configure SRS to be active on this server, and use the default DBengine present to house the reporting server databases. This is the simplest configuration. If you install Reporting Services on a stand-alone (no DBEngine) server, you will need to configure this manually.
• Setup will complete.
• Apply SQL 2008 R2 SP1.
• The update is very straightforward. Accept the defaults and update all features. When complete, reboot the SQL server.

 

 

Operating System Pre requisties

Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server 2012 Core Installation.

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
• Windows Authentication
• Selected website for web console: requires a configured http or https binding.

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

 

• 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.
• Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required for the management server.
• Both .NET Framework 3.5 Service Pack 1 (SP1) and .NET Framework 4 are required. For more information, see the following documents:
  • .NET Framework 3.5 SP1 redistributable package
  • .NET Framework 4 redistributable package

Operations Console

• Microsoft Report Viewer 2010 Redistributable Package
• Microsoft .NET Framework 3.5 SP1 hotfix
• Disk space: %SYSTEMDRIVE% requires at least 512 MB free hard disk space.
• File system: %SYSTEMDRIVE% must be formatted with the NTFS file system

Create a dedidicate Domain account in AD which is for SCOM 2012 and add this account in the SCOM server local administrators group and set this account for the following account in installation time

1) Management server action account

2) System Center Configuration service and System Center Data Access service account

3) Data Warehouse Write account

4) Data Reader account

Deployment guide of SCOM 2012

 

• On the Proceed with Setup screen – click Next.
• On the specify an installation screen – choose to create the first management server in a new management group.  Give your management group a name. Don’t use any special or Unicode characters, just simple text. Click Next.
• On the Database Configuration screen, enter in the name of your SQL database server name and instance. In my case this is “OMDB”. Leave the port at default unless you are using a special custom fixed port.  If necessary, change the database locations for the DB and log files. Leave the default size of 1000 MB for now. Click Next.

On the data warehouse database screen, input the servername, instance, and if necessary change path locations as on the previous screen. Click Next.

• On the Web Console screen, choose the default web site, and leave SSL unchecked. If you have already set up SSL for your default website with a certificate, you can choose SSL.  Click Next.
• On the Web Console authentication screen, choose Mixed authentication and click Next.
• On the accounts screen, choose Domain Account for ALL services, and enter in the unique DOMAIN\OMAA, DOMAIN\OMDAS, DOMAIN\OMREAD, and DOMAIN\OMWRITE accounts we created previously. It is a best practice to use separate accounts for distinct roles in OpsMgr, although you can also just use the DOMAIN\OMDAS account for all SQL Database access roles to simplify your installation. Click Next.
• 
• Choose Yes or No to send Customer Experience and Error reports.
• Click Install.
• Close when complete.
• The Management Server will be very busy (CPU) for several minutes after the installation completes. Before continuing it is best to give the Management Server time to complete all post install processes, complete discoveries, configuration, etc. 10 minutes is typically sufficient.
•