SCOM2012系统建置手册

SCOM2012系统建置⼿册
Step by step installation of SCOM 2012
Pre-Install Preparation
1.Ensure that all minimum requirements are met for the role(s) you are
installing. The list of requirements for each role can be found here. 2.Ensure that the account being used to run your Management Server
services is a member of the Local Administrators group on each of
your Management Server.
3.Ensure that any machine that is going to run the Operations Console
has the MS Report Viewer installed, which can be found here.
4.Ensure that the DW Write account for the environment you are
installing is a local Administrator on the server hosting the SSRS
Reporting installation that will be used for SCOM.
Install the First Agent Management Server
Log on to the server by using an account that has local administrative credentials.
1.On the Operations Manager installation media, run Setup.exe, and
then on the splash screen click Install.
2.On the Getting Started, Select features to install page, select the
Management server feature, and then click Next.
3.On the Getting Started, Select installation location page, accept the
default value of C:\Program Files\System Center 2012\Operations Manager. Or, type a new location or browse to one, and then click
Next.
4.On the Prerequisites page, review and resolve any warnings or errors,
and then click Verify Prerequisites Again to recheck the system.
5.If the Prerequisites checker does not return any warnings or errors,
the Prerequisites, Proceed with Setup page appears. Click Next.
6.On the Configuration, Specify an installation option page, select
Create the first Management server in a new management group, type the name for the management group, and then click Next.
7.On the Configuration, Please read the license terms page, review
the Microsoft Software License Terms, select I have read,
understood and agree with the license terms, and then click Next.
8.When the Configuration, Configure the operational database page
opens, in the Server name and instance name box, type the name of the server and the name of the SQL Server instance for the database server that will host the operational database.
9.After you type the correct value for the SQL Server database server
name, click the SQL Server port box so that Setup will attempt to validate the values you typed for the SQL Server name and for the port number. If validation fails, ensure the SQL instance name you typed in is correct, and that you have permissions to read from the Master database and create new databases on the specified SQL instance, and try again.
10.In the Database name, Database size (MB), Data file folder, and
Log file folder boxes, accept the default values, and click Next. 11.When the Configuration, Configure the data warehouse database
page opens, in the Server name and instance name box, type the server name and the name of the instance of SQL Server for the
database server that will host the data warehouse database.
12.Because this is the first management server installation, accept the
default value of Create a new data warehouse database.
13.In the Database name, Database size (MB), Data file folder, and
Log file folder boxes, accept the default values, and click Next. 14.On the Configuration, Configure Operations Manager accounts
page, ensure that the Domain Account option is selected for each of the Management server action account, the System Center
Configuration service and System Center Data Access service
account, the Data Reader account, and the Data Writer account rows. Enter in the appropriate usernames for each row, with all
passwords. Click Next when finished.
15.On the Configuration, Help improve System Center 2012 –
Operations Manager page, select Yes for both options, and then click Next.
16.Review the options on the Configuration, Installation Summary
page, and then click Install. Setup continues.
17.When Setup is finished, the Setup is complete page appears. Click
Close.
Beginnings
The following step-by-step walkthrough, starts from a newly built Microsoft Windows 2008R2 with SP1 Enterprise member server. We already have a fully working SQL Server 2008 R2 instance on a different member server.
Database requirements:
· SQL Collation: IMPORTANT - install SCOM 2012 on SQL with
the SQL_Latin1_General_CP1_CI_AS collation!
·SQL Server 2008 with SP1/2/3, 2008R2, or 2008 R2 SP1 - Standard or Enterprise editions (no support for Express editions -it will not work, trust me, I’ve tried it!)
· 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
· SQL Server Full Text Search is required
· SQL Services Reporting Services (for Operations Manager Reporting)
Note: If you don’t yet have an SQL Server 2008 R2 instance, a standard Next Next Next type install with Full Text Search, will suffice for the following demo/pilot.
Walkthrough
Part 1 - Server Preparation
Logged in as a domain user with local administrator permissions (using domain administrator here which is not best practice) Add Features Wizard: Install the .NET Framework 3.5.1 feature from Server Manager > Features > Add Features:
Accept to add the additional Required Role Services and Next > Next >:
Select the role services to install for Web Server (IIS): Add the following IIS role services and Next >:
· IIS6 Metabase Compatability
· /doc/d64090e027284b73f3425002.html (and accept Add Required Role Services which includes the required - Default Document, ISAPI Filters, and ISAPI Extensions)
· Windows Authentication
· Static Content
· Directory Browsing
· HTTP Errors
· HTTP Logging
· Request Monitor
· Static Content Compression
· IIS Management Console
· CGI
Confirm Installation Selections: and Install:
Download and install Microsoft .NET Framework 4 (Web Installer): dotNetFx40_Full_setup.exe
Internet Information Services (IIS) Manager: From IIS Manager > Select the Web Server object > ISAPI and CGI Restrictions icon> and make sure that /doc/d64090e027284b73f3425002.html v4 is Allowed for 32 and 64 bit:
Download and install the Report Viewer controls which are part of the Microsoft Report Viewer 2010 Redistributable Package: ReportViewer.exe
(Optional) Turn off Windows Firewall:
Mount the SQL Server 2008 R2 DVD/ISO:
en_sql_server_2008_r2_enterprise_x86_x64_ia64_dvd_520517.iso
And run through the ‘New installation or add features to an existing installation’ wizard to install ‘Reporting Services’:
Note: We use a remote database for the operational database, and data warehouse database; installing Reporting Services here serves to populate the SQL Server instance field when on the ‘S QL Server instance for reporting services step’ of the SCOM2012 installation (see here for more info.) The SSRS instance needs to be a separate instance to SQL instance used by SCOM.
At this stage it would be worth updating the server with the latest Microsoft and Windows patches.
Part 2 - SCOM 2012 Install
Insert the System Center 2012 Operations Manager DVD/ISO and run SETUP.EXE (if autorun disabled):
en_system_center_2012_operations_manager_x86_x64_dvd_804695.iso
The Microsoft System Center 2012 - Operations Manager setup screen appears:
Links for reference:
Release Notes
Installation Guidance
Supported Configurations
Product Documentation
Operations Manager Community
Click the Install button:
Select features to install (here we’re going for a complete install) and Next >:
Select installation location and Next >:
Verify Prerequisites and if okay then Next >:
Specify whether this is going to be the first Management server or an additional one (here we are creating a first one, so we need to provide a Management group name) and Next >:
Accept the license terms and Next >:
Configure the operational database - provide name and instance name of the SQL server to be used, configure further as required, and Next >:
Configure the data warehouse database as required and Next >:
SQL Server instance for reporting services - since we installed SSRS locally, this will pick up the local instance, Next >:
Specify a web site for use with the Web console - use ‘Default Web Site’ or select as required, Next >:
Select an authentication mode for use with the Web console, Next >:
Configure Operations Manage accounts (for the demo using the domain administrator account which is not best practice - see Operations Manager Security Guide), Next >:
Customer Experience Improvement and other stuff, Next> :
Microsoft Update setting, Next >:
Installation Summary, Install:
The End!
Note: In hindsight; for a demo you could probably get away with a local installation SQL Standard or Enterprise on the SCOM Server, with an additional instance for Reporting Services. Apologies I have no time to verify this.。