Parts in this
series:
At this stage it would be worth updating the
server with the latest Microsoft and Windows patches.
In this lab demo, we’re going to install SCOM2012 on a member server.
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)
· 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
· ASP.NET (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
· IIS6 Metabase Compatability
· ASP.NET (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 ASP.NET 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 ‘SQL 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.
Comments
Post a Comment