Installing System Center 2016 Operations Manager Step by Step – Part 3

Part 3 – Install First Management Server

Installing First Management Server is always exciting and complex. You have to make sure that you do everything correct here and install using correct configurations.

Before you can start Installing your First Management Server, please make sure you have installed the pre-requisites.

  1. Installed Microsoft CLR Types for SQL Server 2014
  2. Installed Microsoft Report Viewer 2014 Runtime
  3. PowerShell V 2 or Later
  4. .NET Framework 4.5 or later

To install First Management server, following roles will be installed:

  1. Management Server
  2. Operating Console
  3. Web Console

Below is an example of single Management Server example

om2016-simple-mg-config

https://technet.microsoft.com/en-us/system-center-docs/om/plan/planning-a-management-group-design

Following is a complex Management group example

om2016-distributed-design

https://technet.microsoft.com/en-us/system-center-docs/om/plan/planning-a-management-group-design

Let’s just Install your First Management Server and verify everything works.

To Install via the Command line

  1. Install Web Server Roles
    1. Open Powershell and run the following command to Install required Web Server roles

      Add-WindowsFeature Web-Server, Web-WebServer, Web-Common-Http, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Static-Content, Web-Health, Web-Http-Logging, Web-Request-Monitor, Web-Performance, Web-Stat-Compression, Web-Security, Web-Filtering, Web-Windows-Auth, Web-App-Dev, Web-Net-Ext, Web-Net-Ext45, Web-Asp-Net, Web-Asp-Net45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Mgmt-Tools, Web-Mgmt-Console, Web-Mgmt-Compat, Web-Metabase, NET-Framework-45-ASPNET, NET-WCF-HTTP-Activation45, WAS, WAS-Process-Model, WAS-Config-APIs

  2. Install Microsoft System CLR Types for SQL Server 2016

    msiexec /package SQLSysClrTypes.msi /passive /norestart

  1. Install Microsoft Report Viewer 2016 Redistributable Package

    msiexec /package ReportViewer.msi /passive /norestart

Install SCOM 2016

You can setup a batch file as per below

setup.exe /silent /install /components:OMServer,OMConsole, OMWebConsole /ManagementGroupName:%ManagementGroupName% /SqlServerInstance:%SqlServerInstance% /DatabaseName:%DatabaseName% /DWSqlServerInstance:%DWSqlServerInstance% /DWDatabaseName:%DWDatabaseName% /UseLocalSystemActionAccount /DASAccountUser:%DASAccountUser% /DASAccountPassword:%DASAccountPassword% /DataReaderUser:%DataReaderUser% /DataReaderPassword:%DataReaderPassword% /DataWriterUser:%DataWriterUser% /DataWriterPassword:%DataWriterPassword% /WebSiteName:”Default Web Site” /WebConsoleAuthorizationMode:Mixed /EnableErrorReporting:Never /SendCEIPReports:0 /UseMicrosoftUpdate:0 /SendODRReports:0 /AcceptEndUserLicenseAgreement:1

Replace the variables with values for your setup and Run it using batch file or command line and it should install the required components for you.

Alternatively you can Install SCOM 2016 manually.

To Install SCOM 2016 via GUI

On the Operations Manager installation media, run Setup.exe, and then click Install

On the Getting StartedSelect 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.

For purpose of this post, I will be installing Management Server, Operations Console and Web Console.

Select required components and Click Next.

1

On the Getting StartedSelect installation location page, accept the default value of C:\Program Files\Microsoft System Center 2016\Operations Manager. Or, type a new location or browse to one, and then click Next.

2

On the Prerequisites page, review and resolve any warnings or errors, and then click Verify Prerequisites Again to recheck the system.

NOTE: 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

3

If the Prerequisites checker does not return any warnings or errors, the PrerequisitesProceed with Setup page appears. Click Next

On the ConfigurationSpecify 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.

4

On the ConfigurationPlease 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.

5

When the ConfigurationConfigure 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 nameDatabase size (MB)Data file folder, and Log file folder boxes, we recommend that you accept the default values. Click Next.

6

When the ConfigurationConfigure 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 nameDatabase size (MB)Data file folder, and Log file folder boxes, we recommend that you accept the default values. Click Next.

7

Click Next to Continue

Normally you need default website unless your company have other requirements

Enable SSL if required

8

Click Next to Continue

Leave Authentication mode to Mixed mode

9

On the ConfigurationConfigure Operations Manager accounts page, we recommend that you use the Domain Account option for theManagement 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.

Enter required credentials on Configuring Operations Managers screen.

SCOM will automatically verify the accounts and you should not see those red crosses over in screen.

10

Once accounts has been verified, click Next to Continue

Click Next on Diagnostic and Usage Data screen

Select on or Off depending on your requirement for Microsoft Updates. I normally prefer Off, so you have control which one to install and when.

Review the options on the ConfigurationInstallation Summary page, and then click Install. Setup continues

11

Click Install to begin Installation process

12

Once the Installation process has been completed successfully, click Close to Finish.

13

If Start the Operations Manager Console is checked, then it will the Operations Manager console directly.

When Operations Manager is opened, you can go to Administration and then Select Management Server to verify.

You will see your First Management Server Healthy, which is what we have done so far and it worked.

14

Now we can move to installing second Management Server

Reference: https://technet.microsoft.com/en-us/library/hh301922(v=sc.12).aspx

 

  1. Part 1
    1. Operations Manager Overview
    2. System Center Requirements
  2. Part 2
    1. SQL 2016 Installation
  3. Part 3
    1. First Management Server Installation
  4. Part 4
    1. Second M Management Server Installation
  5. Part 5
    1. Gateway Installation
  6. Part 6
    1. Reporting Services Installation
  7. Part 7
    1. Installing Agents
  8. Part 8
    1. Conclusion

3 thoughts on “Installing System Center 2016 Operations Manager Step by Step – Part 3

  1. Hi Harmik,

    I have to questions regarding your installation document
    1 Why didn’t you install the Reporting server?
    2 Regarding the action accounts. Why do you want the management server action account to be configured as local system?

    With kind regards,

    Martin

    Like

    1. Hi Martin

      Actually Reporting Server is installed separately in next blogs pages, as it is not required at this point of setup.

      Secondly Management Server action account has to be following attibutes:

      1. Member of the local Users group
      2. Member of the local Performance Monitor Users group
      3. “Allow log on locally” permission (SetInteractiveLogonRight)
      System_CAPS_importantImportant

      4. A low-privileged account can be used only on computers running Windows Server 2003 and Windows Vista. On computers running Windows 2000 and Windows XP, the action account must be a member of the local Administrators security group or Local System.

      5. Using a low-privileged domain account requires password updating consistent with your password expiration policies.
      You cannot enable Agentless Exception

      6. Monitoring (AEM) on a management server with a low-privileged action account.

      7. The Action account must be assigned the Manage Auditing and Security log privilege by using Local or Global policy, if a management pack is to read the event in the Security Event log.

      For more detailed information, please visit
      https://technet.microsoft.com/en-us/library/hh212808(v=sc.12).aspx
      or
      https://technet.microsoft.com/en-us/library/hh457003(v=sc.12).aspx

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s