How to Install the First Management Server in a Management Group
Updated: May 13, 2016
Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations Manager
In System Center 2012 – Operations Manager, and System Center 2012 Service Pack 1 (SP1), Operations Manager the first feature that is installed is the management server. The operational database and data warehouse database are created during this setup. This procedure assumes that you have already installed a supported version of Microsoft SQL Server locally on the same server that you are going to install the first management server. However, you can specify an instance of SQL Server that is installed on a separate server.
You must ensure that your server meets the minimum system requirements for System Center 2012 – Operations Manager. For more information, see System Requirements for System Center 2012 – Operations Manager.
Important
Before you follow these procedures, read the Before You Begin section of Deploying System Center 2012 - Operations Manager.
To install the first management server in the management group
-
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, Select features to install page, select the Management server feature. You can also select any of the additional features listed. For example, to also install the Operations console, select Operations console. To read more about each feature and its requirements, click Expand all, or expand the buttons next to each feature, and then click Next.
-
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.
-
On the Prerequisites page, review and resolve any warnings or errors, and then click Verify Prerequisites Again to recheck the system.
Important
You might receive a message that indicates that ASP.NET 4 is not registered with Internet Information Services (IIS). To resolve this problem, open a Command Prompt window, select Run as administrator, and then run the following command:
%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -r
-
If the Prerequisites 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 a name for your management group, and then click Next.
Note
After the management group name is set, it cannot be changed. The Management Group name cannot contain the following characters:, ( ) ^ ~ : ; . ! ? " , ' ` @ # % \ / * + = $ | & [ ] <>{}, and it cannot have a leading or trailing space. It is recommended that the Management Group name be unique within your organization if you plan to connect several management groups together.
-
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.
-
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 type the server name. If you changed the default SQL Server port, you must type the new port number in the SQL Server port box.
As you type the values for the SQL Server and instance names, you see a red circle with a white X in it appear to the left of the Server name and 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.
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 name 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.
-
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.
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”.
Note
The SQL Server model database size must not be greater than 100 MB. If it is, you might encounter an error in Setup regarding the inability to create a database on SQL due to user permissions. To resolve the issue, you must reduce the size of the model database.
-
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.
-
Because this is 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, Configure Operations Manager accounts page, we recommend that you use the Domain Account option for 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. None of them should have domain administrator credentials. Click Next.
-
On the Configuration, Help improve System Center 2012 - Operations Manager page, select your options, and then click Next.
-
If Windows Update is not enabled 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 then click Install. Setup continues.
-
When Setup is finished, the Setup is complete page appears. Click Close.
-
Open the Operations console.
-
In the Operations console, in the navigation pane, click the Administration button, and then expand Device Management.
-
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 install the first management server in the management group 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.
Note
Setup.exe requires administrator privileges because the Setup process requires access to system processes that can only be used by a local administrator.
-
Change the path to where the Operations Manager setup.exe file is located, and run the following command.
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 /ManagementGroupName: "<ManagementGroupName>" /SqlServerInstance: <server\instance> /DatabaseName: <OperationalDatabaseName> /DWSqlServerInstance: <server\instance> /DWDatabaseName: <DWDatabaseName> /UseLocalSystemActionAccount /UseLocalSystemDASAccount /DatareaderUser: <domain\username> /DatareaderPassword: <password> /DataWriterUser: <domain\username> /DataWriterPassword: <password> /EnableErrorReporting: [Never|Queued|Always] /SendCEIPReports: [0|1] /UseMicrosoftUpdate: [0|1] /AcceptEndUserLicenseAgreement: [0|1]