Install Operations Manager 2012 Beta

Article
01/04/2013

Applies To: Operations Manager 2012

In System Center 2012 – Operations Manager, the first feature that is installed is the management server. The operational database is created during this setup. This is different than previous versions of Operations Manager that required the operational database be installed prior to the first management server. In this procedure, you will install the management server, management console, web console, and reporting server on the same server.

Before You Begin

Before you begin your installation, you should read the release notes, and ensure that your server meets the minimum system requirements for Operations Manager. For more information, see:

Operations Manager Administrators Role Assignment

Operations Manager handles assignment of the Operations Manager Administrators role differently than previous versions. In Operations Manager, Setup automatically assigns the Administrators group on the local computer to the Operations Manager Administrators role. You must be logged on with an account that has local Administrator rights to run Setup; this ensures that you can open the Operations console after Setup is completed.

Required Accounts

During Setup, you are prompted for two accounts, the management server action account and the System Center Configuration service and System Center Data Access service account. In Operations Manager, you can use the same account for both services.

Management server action account: This account is used to carry out actions on monitored computers across a network connection. To save time, specify a domain-based account. We recommend that you create an account for this purpose and do not use an account that has domain administrator credentials.
System Center Configuration service and System Center Data Access service account: This account is one set of credentials that is used to update and read information in the operational database. Operations Manager ensures that the credentials used for the System Center Data Access service and System Center Configuration service account are assigned to the sdk_user role in the operational database. The System Center Data Access service and System Center Configuration service account can be configured as either Local System or as a domain account. If the management server and the operational database are on different computers, the System Center Configuration service and System Center Data Access Service account must be a domain-based account. For better security, we recommend that you use an account different from the one used for the management server action account.

SQL Server Requirements

Operations Manager requires access to an instance of a server running Microsoft SQL Server 2008 SP1 or SQL Server 2008 R2. This instance can be located on a separate computer from the management servers in a distributed installation or on the first management server in the management group. In either case, the instance of Microsoft SQL Server 2008 SP1 or SQL Server 2008 R2 must already exist and be accessible before you start your first management server installation. The SQL Server Collation settings must be SQL_Latin1_General_CP1_CI_AS, and SQL Full Text Search must be enabled. This installation was tested on Microsoft SQL Server 2008 Enterprise with SP1 and Microsoft SQL Server 2008 R2 Enterprise. During Setup, you are prompted for the following:

The SQL Server database server name and instance name. If you have installed SQL Server by using the default instance, you only have to specify the SQL Server name.

You can accept the default values for or set:

SQL Server Port number. By default, 1433.
A new operational database (for first management server installation in the management group) or an existing operational database (for installing additional management servers in an existing management group).
The database name. By default, OperationsManager.
The starting database size. By default, 1000 MB.
The Data file and Log folder locations. By default, these are C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Data or C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log as appropriate to the SQL Server defaults.

Data Warehouse and Reporting Requirements

During this installation, you are prompted for two accounts: the Data Warehouse Write account and the Data Reader account. These accounts are created as domain user accounts and added to the local Administrators group on the target server.

Data Warehouse Write account: This account is assigned write permissions on the Data Warehouse database and read permissions on the operational database.

Note

Before you perform this procedure, ensure that the account you plan to use for the Data Warehouse Write account has SQL Server Logon rights and is an administrator on the computers hosting both the operational database and the reporting data warehouse. Otherwise, Setup fails, and all changes are rolled back. This might leave SQL Server Reporting Services in an inoperable state.
Data Reader account: This account is used to define which account credentials SQL Server Reporting Services uses to run queries against the Operations Manager reporting data warehouse. This account is also used for the SQL Server Reporting Services IIS Application Pool account to connect to the management servers.

The account that you use to run the Operations Manager Reporting server installation must be a member of the following groups and roles:

Local Administrator – Required by the Operations Manager Reporting server installation and for configuring SQL Server Reporting Services.
Operations Manager Administrators role – Required for configuring reporting roles.
SQL Server SysAdmin for the Operations Manager database – Required for configuring the dwsynch_users role.
SQL Server SysAdmin for the data warehouse database – Required for configuring the OpsMgrWriter and OpsMgrReader roles.

Ensure that SQL Server Reporting Services has been correctly installed and configured. For more information about how to install and configure SQL Server 2008 Reporting Services, see SQL Server Installation (SQL Server 2008 R2).

Installing Operations Manager

To install the Operations Manager single server management group configuration

Log on to the server by using an account that has local administrative credentials.
On the Operations Manager installation media, run Setup.exe, and then click Install.
On the Getting Started, Please read this license agreement page, review the Microsoft Software License Terms, select I have read, understood, and agree with the terms of the license agreement, and then click Next.
On the Getting Started, Select features to install page select the Management server, Management console, Web console, and Reporting server features. To read more about each feature its requirements, click Expand all, or expand the buttons next to each feature. Then click Next.
On the Getting Started, Select installation location page, accept the default value or type in a new location or browse to one. Then click Next.
On the Prerequisites page, review and resolve any warnings or errors, and then click Verify prerequisites again to recheck the system.

Note

Installation of the web console requires that ISAPI and CGI Restrictions in IIS be enabled for ASP.NET 4. To enable this, select the web server in IIS, 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
If the Prerequisite checker does not return any warnings or errors, the Prerequisites, Proceed with Setup page appears. Click Next.
On the Configuration, Specify an installation option page, select Create the first management server in a new management group, type in a name for your management group and then click Next.
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. If you installed SQL Server by using the default instance, you only have to enter the server name. If you changed the default SQL Server port, you must type in the new port number in the SQL Server port box.
As you type the values for SQL Server and instance name, you see a red circle with a white X in it appear to the left of the Server name and instance (server\instance name) and SQL Server port boxes. The white X indicates that the values have not yet been validated, and the black text indicates that you have not entered any illegal characters. If you enter illegal characters, the text itself turns red. This is shown below.

The white X appears under the following circumstances:
- You entered an instance of SQL Server or a SQL Server port value that is not valid or that does not exist.
- The instance of SQL Server that you specified does not have the required configuration or features.
- You entered a value that is out-of-range (for example, port 999999).
- You entered an illegal character for that box (for example, server\instance%)
You can hover the cursor over the Server name and instance text box to view additional information about the error.
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. When validation is successful the screen changes to look like this
In the Database name, Database size (MB)Data file folder, and Log file folder box, we recommend that you accept the default values. Click Next

Note

These paths do not change if you connect to a different instance of SQL Server.

Important

You might receive a message about having the wrong version of SQL Server, or you might encounter a problem with the SQL Server Windows Management Instrumentation (WMI) provider. To resolve this problem, open a Command Prompt window, select Run as administrator, and then run the following command. In the command, replace the <path> placeholder with the location of SQL Server:

mofcomp.exe “<path>\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof”.
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.
For the first management server installation, accept the default value of Create a new data warehouse database.
In the Database name, Database size (MB)Data file folder, and Log file folder boxes, we recommend that you accept the default values. Click Next.

Important

You might receive a message about having the wrong version of SQL Server, or you might encounter a problem with the SQL Server Windows Management Instrumentation (WMI) provider. To resolve this problem, open a Command Prompt window, select Run as administrator, and then run the following command. In the command, replace the <path> placeholder with the location of SQL Server:

mofcomp.exe “<path>\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof”.

Note

These paths do not change if you connect to a different instance of SQL Server.
On the Configuration, SQL Server instance for reporting services page, select the SQL Server database instance from the drop-down list. This drop-down list contains the SQL Server database instance name that was created when you installed SQL Server 2008 SP1 or SQL Server 2008 R2 and should be the name of the server on which you are installing Operations Manager. Click Next.
On the Configuration, Specify a web site for use with the Web console page, select Default Web Site or the name of an existing website. Select the option Enable SSL only if the website has been configured to use SSL, and then click Next.
On the Configuration, Select an authentication mode for use with the Web console page, select your option, and then click Next.
On the Configuration, Configure Operations Manager accounts page, we recommend that you use Domain Account option for the Management Server Action Account, System Center Configuration service and System Center Data Access service, the Data Reader account, and the Data Writer account. Neither of them should have domain administrator credentials. Prior to account validation, error icon will appear to the left of the Domain\Username box as show below.

Enter the credentials for a domain account in each field. The error icons will disappear after account validation. Click Next.
On the Configuration, **Help improve Operations Manager ** page, select your options and click Next.
If Windows Update is not activated on the computer, the Configuration, Microsoft Update page appears. Select your options, and then click Next.
Review the options on the Configuration, Installation Summary page, and click Install. Setup continues.
When Setup is finished, the Setup is complete page appears. Click Close and the Operations console will open.

To install the Operations Manager single server management group configuration by using the Command Prompt window

Log on to the server by using an account that has local administrative credentials.
Open the Command Prompt window by using the Run as Administrator option.
Change the path to where the Operations Manager setup.exe file is located, and run the following command.

Important

Use the /WebConsoleUseSSL parameter only if your website has Secure Sockets Layer (SSL) activated.

For a default web installation, specify Default Web Site for the /WebSiteName parameter.

Important

The following command assumes that you specified the Local System for the Management server action account (/UseLocalSystemActionAccount) and Data Access service (/UseLocalSystemDASAccount). To specify a domain\user name for these accounts, you must provide the following parameters instead.

/ActionAccountUser: <domain\username> /ActionAccountPassword: <password>
/DASAccountUser: <domain\username> /DASAccountPassword: <password>
```
setup.exe /silent /install
/components:OMServer,OMConsole,OMWebConsole,OMReporting
/ManagementGroupName: "<ManagementGroupName>"
/SqlServerInstance: <server\instance>
/DatabaseName: <OperationalDatabaseName>
/DWSqlServerInstance: <server\instance>
/DWDatabaseName: <DWDatabaseName>
/UseLocalSystemActionAccount /UseLocalSystemDASAccount
/DatareaderUser: <domain\username>
/DatareaderPassword: <password>
/DataWriterUser: <domain\username>
/DataWriterPassword: <password>
/WebSiteName: ”<WebSiteName>” [/WebConsoleUseSSL]
/WebConsoleAuthorizationMode: [Mixed|Network]
/SRSInstance: <server\instance>
/SendODRReports: [0|1]
/EnableErrorReporting: [Never|Queued|Always]
/SendCEIPReports: [0|1]
/UseMicrosoftUpdate: [0|1]
```

Verifying the Installation

To confirm the health of the management server

In the Operations console, select the Administration workspace.
In Device Management select Management Servers. In the results pane, you should see the management server that you just installed with a green check mark in the Health State column.

To confirm the health of operations manager reports

In the Operations console, in the navigation pane, click Reporting.

Note

After initial deployment, it can take up to 30 minutes for reports to appear.
Click Microsoft ODR Report Library, and then double-click any of the reports listed. The selected report is generated and displays in a new window.

By default, you should see the following reports:
- Alerts Per Day
- Instance Space
- Management Group
- Management Packs
- Most Common Alerts
Note

Selecting the management packs report is particularly useful at this point because it provides you with a full inventory of the management packs that have been installed on your server.
Close the report window.

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----