SCOM 2016 – Install System Center Operations Manager 2016 – Part 3

Standard

In this series off blog post I am going to take you true the steps I took to install System Center Operations Manager 2016. The Environment will be installed using the following software:

  • Microsoft Windows Server 2016 – Download from here
  • Microsoft SQL Server 2016 – Download from here
  • System Center Operations Manager 2016 – Download from here

My Test environment consist of the following servers,

  • DC01 – Domain Controller
  • SQL01 – Microsoft SQL 2016 server
  • DATA01 – Data Server
  • MS01 – Scom Management Server 01
  • MS02 – Scom Management Server 02
  • WEB01 – Scom Web Console Server,

Here you can find the previous blogposts

In this part we are going to install the second Management Server and the System Center operations Manager Console.

First we are going to install the System Center Operations Manager Console. The System Center Operations Manager Console will be installed on Windows 10 domain joined machine. Before we can install the System Center Operations Manger console we need to install Report Viewer Controls. These can be download from here. I am using a Group Policy to deploy the Report Viewer Controls.

  1. Start the "Group Policy Management" console
  2. Right click on the Group Policy Object that is applied to all the workstation that you want to deploy the Report Viewer and click “Edit
    CreateGPO01
  3. In the “Group Policy Management Editor” navigate to “Computer Configuration – Policies – Software Settings – Software installation” then right click on “Software installation” then click on “New” then “Packages
    CreateGPO02
  4. Navigate to the path that you placed the installation files and select “Reportviewer.msi” then click “Open
  5. On the “Deployment Screen” select “Advanced” and click “OK
    CreateGPO03
  6. On the “Microsoft Report Viewer 2015 Runtime Properties” page, click “OK
    CreateGPO04
  7. Restart the client computer that is available in the Organizational Unit that you want to use. The result should look something like this:
    CreateGPO05
  8. On the “Windows Client” where you want to install the “System Center Operations Manager Console” click “Setup.exe
  9. On the “Operations Manager” screen click “Install
  10. On the “Operations Manager Setup” page, in the section“Select feature to Install” select “Operations Manager Console” and click “Next
    ConsoleInstall01
  11. On the “Operations Manager Setup” page, in the section “Select installation location” click “Next
    ConsoleInstall02
  12. On the “Operations Manager Setup” page, in the section “Proceed with Setup” screen click “Next
    ConsoleInstall03
  13. On the “Operations Manager Setup” page, in the section “Proceed read the license terms” Screen check “I have read, understood and agree with the license term” and click “Next
    ConsoleInstall04
  14. On the “Operations Manager Setup” page, in the section “Diagnostic and usage Data” screen click “Next
    ConsoleInstall05
  15. On the “Operations Manager Setup” page, in the section “Microsoft Update” screen select “Off” and click “Next
    ConsoleInstall06
  16. On the “Operations Manager Setup” page, in the section “Installation Summary” screen click “Install
    ConsoleInstall07
  17. On the “Operations Manager Setup” page, in the section “Setup is Complete” click “Close
    ConsoleInstall08
  18. The end result should look something like this
    ConsoleInstall09

Now we are going to install the second management server. On the server is Windows Server 2016 Core edition installed.  I used the following script to install the management server:

First we need to install the AuthManager for Windows Server 2016 using PowerShell:

InstallMS01

Next we can run the following command:

When you start the “System Center Operations Manager” Console and you to “Administration” and expand “Device Management”, “Management Servers” you should see two Management servers.

InstallMS02

This completes the third part of these series. In the fourth part we are going to install the web-console.

Big thanks’ to Tao Yang and Florent Appointaire for there information on there blogs on how to install System Center Operations Manager 2016 on Windows Server Core 2016

SCOM 2016 – Install System Center Operations Manager 2016 – Part 1

Standard

In this series off blog post I am going to take you true the steps I took to install System Center Operations Manager 2016. The Environment will be installed using the following software:

  • Microsoft Windows Server 2016 – Download from here
  • Microsoft SQL Server 2016 – Download from here
  • System Center Operations Manager 2016 – Download from here

My Test environment consist of the following servers,

  • DC01 – Domain Controller
  • SQL01 – Microsoft SQL 2016 server
  • DATA01 – Data Server
  • MS01 – Scom Management Server 01
  • MS02 – Scom Management Server 02
  • WEB01 – Scom Web Console Server,

Here you can find the rest of the blogposts.

Before we can deploy System Center Operations Manager 2016 we need to deploy a instance of Microsoft SQL Server 2016. This instance will be located on a separated computer.

Before we can install Microsoft SQL Server 2016 we need to create group managed service accounts. I used the following steps to create the managed service accounts:

  1. Start “Active Directory Users and Computers” and create a “Group” whit a Group Scope “Global” and the  Group type “Security”. Give the group a logical name In my case “SG- Sql2016Agents", and click “OK
    Install and Configure SQL for System Center Operations Manager 2016
  2. Open the properties off the above created group and add the domain member servers that will be hosting the SQL Server instances that will be using the group managed service accounts.
    Install and Configure SQL for System Center Operations Manager 2016
  3. On your “Domain Controller” run a “PowerShell” command prompt as administrator and run the following command:

    Install and Configure SQL for System Center Operations Manager 2016

     

  4. On your “Domain Controller” run a “PowerShell” command prompt as administrator and enter the following command: 

    Install and Configure SQL for System Center Operations Manager 2016

  5. Next we need to grand the created group managed service account the right to “Validated write to service principal name” permission:
    • In “Active Directory Users and Computers”, click “View” and check “Advanced Features”.Install and Configure SQL for System Center Operations Manager 2016
    • In “Active Directory Users and Computers”, right click on the domain and go to “Properties” and click on the “Security” tab.
    • On the “Security” tab click “Advanced
    • On the “Advanced Security settings for <Domain>”  page, on the “Permissions” tab click “Add
    • On the “Permission Entry for <Domain>” page, at the top, click the “Select a principal” link
    • On the “Select User, Computer, Service Account, or Group” page, click “Object Types
    • On the “Object Types” page, select “Service Accounts” and click “OK
    • On the “Select User, Computer, Service Account or Group” page, enter the name of de service you created above and press “Enter
    • On the “Permission Entry for <Domain>” in the “Applies to” section select “Descendant Computer Objects
    • On the “Permission Entry for <Domain>” page in the “Permissions” section select “Validated write to service principal name” and click “OKInstall and Configure SQL for System Center Operations Manager 2016
    • Click “OK” three times to close all dialogs

    After completing the the above steps the result should look something like this:

    Install and Configure SQL for System Center Operations Manager 2016

     

  6. On your “Domain Controller” run a “PowerShell” command prompt as administrator and enter the following command:

  7. Next we need to grand the created group managed service account the right to “Validated write to service principal name” permission. See "Step 5"
  8. On your “Domain Controller” run a “PowerShell” command prompt as administrator and enter the following command:

  9. Next we need to grand the created group managed service account the right to “Validated write to service principal name” permission. See "Step 5"
  10. On your “SQL Server” install the AD module for PowerShell.

    Install and Configure SQL for System Center Operations Manager 2016

  11. When rebooting the “SQL Server” the Group Managed Service accounts are configured on the Server. You can check if the Group managed Service accounts are installed using the following command:

    The result should look something like this:

    Install and Configure SQL for System Center Operations Manager 2016

     

Know that the Service accounts for SQL are created lets start by installing SQL Server 2016

  1. On the “SQL Server Installation Center” page click “Installation” and click “New SQL Server Stand-Alone installation or add features to an existing Installation

    Install and Configure SQL for System Center Operations Manager 2016

  2. On the “SQL Server 2016 Setup” page, in the “Product Key” section enter a Product key click “Next

    Install and Configure SQL for System Center Operations Manager 2016

  3. On the “SQL Server 2016 Setup” page,, in the “License Terms” section click “I Accept the license terms” and click “Next

    Install and Configure SQL for System Center Operations Manager 2016

  4. On the “SQL Server 2016 Setup” page, on the “Microsoft update” section click “Use Microsoft Update to check for Updates (Recommended)” and click “Next

    Install and Configure SQL for System Center Operations Manager 2016

  5. On the “SQL Server 2016 Setup” page, in the “Product Updates” section click “Next

    Install and Configure SQL for System Center Operations Manager 2016

  6. On the “SQL Server 2016 Setup” page, on the “Install Rules” section click “`Next

    Install and Configure SQL for System Center Operations Manager 2016

  7. On the “SQL Server 2016 Setup” page, in the “Feature Selection” select the following and click “Next”:
    • Database Engine Service
    • Full-Text Extraction for fast text search
    • Reporting Services – Native

    In my environment I changed the paths to where I wanted to install SQl. Install and Configure SQL for System Center Operations Manager 2016

  8. On the “SQL Server 2016 Setup” page, in the “Feature Rules” section click “NextInstall and Configure SQL for System Center Operations Manager 2016
  9. On the “Sql Server 2016 Setup” page, in the “Server Configuration” section on the “Service Accounts Tab” add the above created service accounts to wright service. The result should look something like this:Install and Configure SQL for System Center Operations Manager 2016
  10. On the “Sql Server 2016 Setup” page, in the “Server Configuration” section on the  “Collation” tab make sure that “SQL_Latin1_General_CP1_CI_AS” is selected and click “NextInstall and Configure SQL for System Center Operations Manager 2016
  11. On the “SQL Sever 2016 Setup” page, in the “Database Engine Configuration” section click “Next” In my environment I added a group off SQL Administrators which are allowed off managing the SQL Server.Install and Configure SQL for System Center Operations Manager 2016
  12. On the “SQL Server 2016 Setup” page, on the “Reporting Services Configuration” section make sure “Install and Configure” is selected and click “NextInstall and Configure SQL for System Center Operations Manager 2016
  13. On the “SQL Server 2016 Setup” page, on the “Ready to Install” section click “InstallInstall and Configure SQL for System Center Operations Manager 2016
  14. On the “SQL Server 2016 Setup” page, on the “Complete” section click “CloseInstall and Configure SQL for System Center Operations Manager 2016

This completes the first post in a series of post where we install System Center Operations Manager 2016. In the next post we are going the install all the prerequisites and create all the service accounts.

Disable Discovery of a SQL Server.

Standard

In my environment I have a couple of SQL severs that are being discovered by the System Center Management Pack for SQL Server where I don’t want to monitor the SQL Server application.

I took the following steps to complete this option:

  1. Create a Group with the client computers you don’t want to monitor
  2. Apply Overrides to Object Discoveries
  3. Run "Remove-SCOMDisabledClassInstance"

1. Create a Group with client Computers  you don’t want to monitor

  1. Start the "System Center Operations Manager Console"
  2. In the System Center Operations Manager console, click "Authoring"
  3. Right-click "Groups", and then click "Create a new Group" to start the Create Group Wizard.
  4. On the "General Properties" page, Enter a "Name", "Description" and select the management pack you want to use. Click "Next" General Properties Group
  5. On the "Explicit Members" page, click "Add/ Remove Objects" Add/ Remove Objects
  6. On the "Create Group Wizard – Object Selection" page, enter the computer name you don’t want to monitor in the "Filter by part or name(Optional)" box. In the "Available Items" box select the computer object and click "Add" and click "Ok"Create Group Wizard - Object Selection
  7. On the "Explicit Members" page, click "Next"
  8. On the "Dynamic Members" page, click "Next"
  9. On the "Sub Groups" page, click "Next"
  10. On the "Excluded Members" page, click "Create"

2. Apply Overrides to Object Discoveries

  1. Start the "System Center Operations Manager Console"
  2. In the System Center Operations Manager console, click "Authoring"
  3. On the "Authoring" page, expand "Management Packs" and select "Object Discovery"
  4. Click the "Scope" button on the Operations Manager toolbar
  5. On the "Scope Management Pack Objects" page, in the look for bar type "SQL " and select the target "SQL Server 2005 DB Engine", “SQL Server 2008 DB Engine”, “SQL Server 2012 DB Engine” and click "OKScope Management Pack Objects
  6. Click “Find Now
  7. Right click on "Discover SQL Server 2005 Database Engines (Windows Server)" and click "Overrides", "Override the Object Discovery", "For a group" Override the Object Discovery
  8. On the "Select Object" page, select the group that you created above
  9. On the "Override Properties" page, check "Enabled" and change the "Override Value" from “True", to "False" and select the "Management Pack" where you want to store the overrides. Click "Apply" and "OK" Override Properties
  10. Repeat the above steps for "Discover SQL Server 2008 Database Engines (Windows Server)" and the "Discover SQL Server 2012 Database Engines (Windows Server)"

3. Run "Remove-SCOMDisabledClassInstance"

  1. Start the "Operations Manager Shell"
  2. At the command prompt Type "Remove-SCOMDisabledClassInstance" and press "Enter"
  3. Answer the Question by pressing "Y" and press "Enter"

    Operations Manager Shell

Now the SQL Servers that were discovered will not be discovered and be removed from the computers state view in the SQL Management Pack

Installing Update Rollup 9 SCOM 2012 Sp1

Standard

In this blog post I will take you true the steps of installing System Center Operations Manager 2012 Sp1 update Rollup 8 to Update Rollup 9

The following issues are fixed in this Update

  • Operational Insight through Operations Manager
  • Support for “SUSE Linux Enterprise Server systems

You can download the Update Rollup 9 form here
The downloaded files consist of an update for the “System Center Operations Manager Console” and the “System Center Operations Manager Server. 

Microsoft Update Catalog

The following steps outline the process of installing the Update

  1. Backup the operations Manager Databases and unsealed Management Pack’s
  2. Install Update to the Management server
  3. Install update to the secondary Management Servers
  4. Install Update to the Operations Manager Console
  5. Run the SQL scripts
  6. Import Management Pack’s
  7. Deploy the update to the agents

1. Backup the operations Manager Databases and unsealed Management Pack’s

I did a manual backup from my databases using the SQL Console

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server
  3. Right click on the database that you want to backup, select "Tasks" and click "Backup

    Backup Database

  4. On the "Backup Database Select the setting that you want to use and click "Ok

    BackupRunning

  5. When the Backup is completed click "Ok
  6. Repeat the steps Above for all the databases

You can backup your management pack’s using the powershell Operations Manager shell and type the following command:

Get-SCManagementPack | Export-SCManagementPack -path D:\Backup\MP

backupMP

2. Install Update to the Management server

  1. Extract the cabinet file
  2. Start a "elevated powershell command prompt"
  3. Run the "KB3023167-AMD64-Server.msp"

    ManagementServerUpdate

  4. Installation is running. This can take some time.

    ManagementServerUpdate1

  5. On the Dialog Screen "System Center Operations Manager 2012" klik "Yes" to restart the server

    ManagementServerUpdate2

3. Install update to the secondary Management Servers

I installed the update the same way is installed it on the Management Server. So follow Step 2

4. Install Update to the Operations Manager Console

  1. If you don’t want to reopen the System Center Operations Manager Console close the
  2. Extract the cabinet file
  3. Start a "elevated Powershell command prompt"
  4. Run the "KB3023167-AMD64-ENU-Console.msp"

    UpdateConsole1

  5. Installation is running. This can take some time.

    UpdateConsole2

 

5. Run the SQL scripts

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server and select the “OperationsManagerDW" Database

    SelectOperationManagerDW

  3. On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "UR_Datawarehouse.SQL" file and then click Open.
  4. When the file is loaded, click "Execute" in the SQL Editor tool bar
  5. Your Result should look something like:

    RowsAffected

Next we need to run the following script against the OperationsManager database

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server and select the “OperationsManager" Database

    SelectOperationManager

  3. On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "update_rollup_mom_db" file and then click Open.
  4. When the file is loaded, click "Execute" in the SQL Editor tool bar
  5. Your Result should look something like:

    RowsAffected3

6. Import the management Pack

  1. Start the System Center Operations Manager Console and select the "Administration pane"
  2. Right click "Management Pack" and click "Import Management Packs…"
  3. In the "Import Management Packs" and click "Add" and click "Add from Disk…"
  4. Browse to "D:\Program Files\System Center 2012\Operations Manager\Server\Management Packs for Update Rollups" and select the management Pack’s in that folder
    • Microsoft.SystemCenter.AlertAttachment.mpb
    • Microsoft.SystemCenter.IntelliTraceProfiling.mpb
      • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb which should be installed from SCOM 2012 SP1
      • MediaMicrosoft.Windows.InternetInformationServices.Common.mpb which should be installed from the online catalog
    • Microsoft.SystemCenter.Visualization.Library.mpb
    • Microsoft.SystemCenter.Image.Library.mp
    • Microsoft.SystemCenter.Advisor.Internal.mpb
    • Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp
    • Microsoft.SystemCenter.Apm.Infrastructure.mpb
    • Microsoft.SystemCenter.Apm.Library.mpb
    • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp p
    • Microsoft.SystemCenter.DataWarehouse.Reports.mp
    • Microsoft.SystemCenter.DataWarehouse.ServiceLevel.Report.Library.mp
    • Microsoft.SystemCenter.TFSWISynchronization.mpb
  5. Click "Install"

    ImportManagmentPacks

  6. Click "Close"

7. Deploy the update to the agents

  1. Start the System Center Operations Manager Console and select the "Administration pane"
  2. Select " Device Management" and then "Pending Management"
  3. Select the a "Agent" and click "Approve"

    Aprove

  4. On the "Agent Update" page click "Update"

    Update

  5. when you open de the "Agent by Version" view you should see something like this:

    Ready

More information on installing Update Rollup 9 for System Center Operations Manager 2012 sp1 can be found here. To install this Update Rollup 8 I used the deployment plan from Kevin Holman

Operations Manager Failed to start a process

Standard

In my System Center Operations Manager 2012 sp1 Update Rollup 8 environment I was getting the following error in System Center Operations Manager Console from my “Windows Server 2008” and my “Windows Server 2008 r2” servers:

Operations Manager failed to start a proccess

After doing some research I found the following article on Kevin Holman blog. Noticing that the solution was written for Windows Server 2003. I did do the registry modification for the WMI buffer thresholds. The following Registry values needed to be modified:

  • "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM\Low Threshold On Events (B)", change from "10000000" to "35000000"
  • "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM\High Threshold On Events (B)" change from "20000000" to "70000000"

I used a PowerShell script to change the above setting. You can download the script from here

After the restart of the server you have to close the warning in the System Center Operations Manager Console manually.

Installing Update Rollup 8 SCOM 2012 Sp1

Standard

In this blog post I will take you true the steps of installing System Center Operations Manager 2012 Sp1 update Rollup 7 to Update Rollup 8

The following issues are fixed in this Update

  • The Health Service bouncing that is caused by high memory usage in the MonitoringHost process.
  • This update includes a fix to prevent resynchronization of all managed entities from the Operations Manager to the Operations Manager Data Warehouse (OMDW) database and to prevent the failure to sync that this causes because of duplicate entries.
  • The import of Visualization.component.library and Visualization.library binary files (.mpb) fails. The import succeeds on a successive try.
  • System Center Operations Manager agents randomly time out when authenticating to the Gateway or Management Server because of domain controller or network performance issues. The time-out value was set to 1 second earlier. A fix was made to increase server time out to-20 seconds and client time out to 5 minutes.

You can download the Update Rollup 8 form here

The following steps outline the process of installing the Update

  1. Backup the operations Manager Databases and unsealed Management Pack’s
  2. Install Update to the Management server
  3. Install update to the secondary Management Servers
  4. Install update to the gateway servers
  5. Install update to the ACS servers
  6. Install Update to the Web Console
  7. Install Update to the Operations Manager Console
  8. Run the SQL scripts
  9. Import Management Pack’s
  10. Deploy the update to the agents

1. Backup the operations Manager Databases and unsealed Management Pack’s

I did a manual backup from my databases using the SQL Console

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server
  3. Right click on the database that you want to backup, select "Tasks" and click "Backup

    BackupDatabase

  4. On the "Backup Database Select the setting that you want to use and click "Ok

    BackupRunning

  5. When the Backup is completed click "Ok
  6. Repeat the steps Above for all the databases

You can backup your management pack’s using the powershell Operations Manager shell and type the following command:

Get-SCManagementPack | Export-SCManagementPack -path D:\Backup\MP

backupMP

2. Install Update to the Management server

  1. Extract the cabinet file
  2. Start a "elevated powershell command prompt"
  3. Run the "KB2991997-AMD64-Server.msp"

    UpdateManagementServer

  4. Installation is running. This can take some time.

    UpdateManagementServerRunning

  5. On the Dialog Screen "System Center Operations Manager 2012" klik "Yes" to restart the server

    UpdateManagementServerRestart

3. Install update to the secondary Management Servers

I installed the update the same way is installed it on the Management Server. So follow Step 2

4. Install update to the gateway servers

  1. Extract the cabinet file
  2. Start a "elevated powershell command prompt"
  3. Run the "KB2991997-AMD64-Gateway.msp"

    UpdateGatewayServer

  4. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.

5. Install update to the ACS servers

  1. Extract the cabinet file
  2. Start a "elevated powershell command prompt"
  3. Run the "KB2991997-AMD64-ENU-ACS.msp"

    UpdateACS

  4. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.

6. Install Update to the Web Console

  1. Extract the cabinet file
  2. Start a "elevated powershell command prompt"
  3. Run the "KB2991997-AMD64-ENU-WebConsole.msp"

    UpdateConsole

  4. Installation is running. This can take some time.

    UpdateWebConsoleRunning

  5. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.

7. Install Update to the Operations Manager Console

  1. If you don’t want to reopen the System Center Operations Manager Console close the
  2. Extract the cabinet file
  3. Start a "elevated Powershell command prompt"
  4. Run the "KB2991997-AMD64-ENU-Console.msp"

    UpdateConsole

  5. Installation is running. This can take some time.

    UpdateConsoleRunning

 

8. Run the SQL scripts

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server and select the “OperationsManagerDW" Database

    SelectOperationManagerDW

  3. On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "UR_Datawarehouse.SQL" file and then click Open.
  4. When the file is loaded, click "Execute" in the SQL Editor tool bar
  5. Your Result should look something like:

    RowsAffected

Next we need to run the following script against the OperationsManager database

  1. Start the "SQL Server Management Studio"
  2. Connect to the Database server and select the “OperationsManager" Database

    SelectOperationManager

  3. On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "update_rollup_mom_db" file and then click Open.
  4. When the file is loaded, click "Execute" in the SQL Editor tool bar
  5. Your Result should look something like:

    RowsAffected3

9. Import the management Pack

  1. Start the System Center Operations Manager Console and select the "Administration pane"
  2. Right click "Management Pack" and click "Import Management Packs…"
  3. In the "Import Management Packs" and click "Add" and click "Add from Disk…"
  4. Browse to "D:\Program Files\System Center 2012\Operations Manager\Server\Management Packs for Update Rollups" and select the management Pack’s in that folder
    • Microsoft.SystemCenter.AlertAttachment.mpb
    • Microsoft.SystemCenter.IntelliTraceProfiling.mpb
      • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb which should be installed from SCOM 2012 SP1
      • MediaMicrosoft.Windows.InternetInformationServices.Common.mpb which should be installed from the online catalog
    • Microsoft.SystemCenter.Visualization.Library.mpb
    • Microsoft.SystemCenter.Image.Library.mp
    • Microsoft.SystemCenter.Advisor.Internal.mpb
    • Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp
    • Microsoft.SystemCenter.Apm.Infrastructure.mpb
    • Microsoft.SystemCenter.Apm.Library.mpb
    • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp p
    • Microsoft.SystemCenter.DataWarehouse.Reports.mp
    • Microsoft.SystemCenter.DataWarehouse.ServiceLevel.Report.Library.mp
    • Microsoft.SystemCenter.TFSWISynchronization.mpb
    • Microsoft.SystemCenter.Visualization.Component.Library.mpb
  5. Click "Install"

    UpdateManagementPacks

  6. Click "Close"

10. Deploy the update to the agents

  1. Start the System Center Operations Manager Console and select the "Administration pane"
  2. Select " Device Management" and then "Pending Management"
  3. Select the a "Agent" and click "Approve"

    Aprove

  4. On the "Agent Update" page click "Update"

    Update

  5. when you open de the "Agent by Version" you should see something like this:

    Ready

More information on installing Update Rollup 8 for System Center Operations Manager 2012 sp1 can be found here. To install this Update Rollup 8 I used the deployment plan from Kevin Holman

Installing the SQL Management Pack

Standard

In this blog post I going thru the steps I took to install and configure the SQL Management Pack. You can download the management pack from here

1. Create a Active Directory Domain User Account

  1. Start "Active Directory Users and Computers"
  2. Expand your domain and browse to the Organization Unit where you create your Service Accounts
  3. Click on the “Create a new user in the current container

    CreateUserAccount

  4. On the “New Object – User” page file in the “First name:”,”Full Name:”,”User logon name:” and the “User logon name (pre-Windows 2000):” and click “Next

    NewObjectUser

  5. On the "New Object – User" enter a "Password",">Confirm password", uncheck "User Must change Password at next logon" and check "User cannot change password","Password never expires" and click "Next"
  6. On the "New Object – User" click "finish"

You can also do this steps using Windows Powershell. The following windows Powershell commands needs to be run at an "administrator-level Windows Powershell" command prompt:

2. Making the Active Directory Account Member of the Local Administrators Group

  1. On the Database Server that you want to monitor start the "Server Manager"
  2. In the "Server Manager" expand "Configuration","Local Users and Computers","Groups"

    ServerManagerGroups

  3. In the "Groups" section double click the group "administrators"
  4. On the "Administrators Properties" page click "Add..

    AdministratorProperties

  5. On the "Select Users, Computers, Service Accounts, or groups" Type the above created account name and click "Check Names" then click "OK"
  6. On the "Administrators Properties" page, click "Apply" and the "Ok"

3. Grant the Active Directory Account Sys Admin Right on the SQL

  1. On the Database Server that you want to monitor start the "SQL Server Management Studio"
  2. In the "Connect to server" page, enter the login credentials and click "Connect"
  3. In the "Object Explorer" screen, expand "Security","Logins

    MicrsoftSQLServerManagementStudio

  4. Right click on "Logins" and click "New Login"

    SQLNewLogin

  5. In the "Login – New" screen click "Search"

    SQLSearch

  6. In the "Select User or Group" screen, change the location to "Entire Domain" and search for the above created account and click "OK"
  7. In the "Login – New" screen, in the "Select a Page pane, select "Server Role" and check "sysadmin" and click "OK"

    SQLsysadmin

  8. Close the "Microsoft SQL Server Management Studio"

4. Create a Run As account in System Center Operations Manager Console

  1. Start "System Center Operations Manager Console"
  2. Browse to the "Administration" pane
  3. In the "Administration" pane, expand "Run As Configuration" and click "Accounts"

    RunsAsAccounts

  4. Right Click "Accounts" and click "Create Run As Account

    CreateRunAsAccount

  5. On the "Introduction" page, Click "Next

    CreateRunAsAccountIntroduction

  6. On the "General Properties" page, select the "Run As account type", "Windows" and enter a "Display Name" and click "Next

    CreateRunAsAccountGeneralProperties

  7. On the "Credentials" page, enter the above created "User Name", "Password", "Confirm password", "Domain" and click "Next"

    CreateRunAsAccountCredentials

  8. On the "Distribution Security" page, select "More secure – I want to manually select the computers which the credentials will be distributed" and click "Create"

    CreateRunAsAccountDistributionSecurity

  9. On the "Completion" Page, click "Close"

    CreateRunAsAccountCompletion

  10. Right click the above created Run As Account and click "properties"
  11. On the "Run As Account properties – SQL Monitoring Run As Account" page, select the tab "Distribution"

    RunsAsAccountsDistribution

  12. On the "Distribution" page, click "Add"
  13. On the "Computer Search" page, enter the sql server that you want to monitor and click "Add" and the "Ok"

    ComputerSearch

  14. On the "Distribution" page, click "Apply" and the "OK"

4. Import the SQL Management Pack

  1. Copy the "SQLServerMP.msi" to a management server
  2. Double click "SQLServerMP.msi", check "I accept the terms in the license Agreement", and click "Install"

    SQLManagementPackInstall

  3. If a "User account Control" window pops up click "Yes"
  4. In the "System Center Monitoring Pack for SQL Server Setup" window, uncheck "Open Management Pack folder" and click "Finish"
  5. The default location for the Management Pack is "C:\Program Files (x86)\System Center Management Packs\System Center Monitoring Pack for SQL Server\6.5.1.0"
  6. Start the "System Center Operations Manager Console", go the "Administration" workspace and right click "Management Pack’s"

    ImportManagementPacks

  7. In the "Import Management Packs" screen, click "Add" and click "Add from Disk"

    AddfromDisk

  8. In the "Online Catalogue Connection" screen click "No"
  9. Browse to the location where you installed the "System Center Monitoring Pack for SQL Server" and select the management pack that you want to import. I selected:
    • Microsoft SQL Server Generic Dashboards
    • Microsoft SQL Server Generic Presentation
    • Microsoft SQL Server Core Library
    • Microsoft SQL Server Visualisation Library
    • Microsoft SQL Server 2008 (Discovery)
    • Microsoft SQL Server 2008 Mirroring (Discovery)
    • Microsoft SQL Server 2008 Mirroring (Monitoring)
    • Microsoft SQL Server 2008 (Monitoring)
    • Microsoft SQL Server 2008 (Presentation)
    • Microsoft SQL Server 2012 AlwaysOn (Discovery)
    • Microsoft SQL Server 2012 Alwayson (MOnitoring)
    • Microsoft SQL Server 2012 (Discovery)
    • Microsoft SQL Server 2012 (Monitoring)
    • Microsoft SQL Server 2012 (Presentation)
  10. On the "Select Management Packs" page, click "Install"

    SelectManagementPackInstall

  11. When the import is finished click "Close"

5. Associate Runs As Account with the Run As Profile

  1. Start the "System Center Operations Manager Console", go the "Administration" workspace, expand "Run As Configuration" and select "Profiles"

    RunsAsConfigurationProfiles

  2. Right click "SQL Server Discovery Account" and select the properties

    SQLServerDiscoveryAccountProperties

  3. On the "Introduction" page, click "Next"
  4. On the "General Properties" page, click "Next"
  5. On the "Run As Accounts page, click "Add"

    RunsAsAccountsAdd

  6. On the "Add a Run As Account screen, Select the "SQL Monitoring Run As Account" check "All Targeted Objects" and click "OK"
  7. On the "Run As Accounts page, click "Add"
  8. On the "Run As Accounts page, click "Save"
  9. On the "Completion" page, click "SQL Monitoring Run As Account"
  10. The "Run As account Properties – SQL Monitoring Run As Account will be opened. Click "Ok"
  11. On the "Completion" page, click "Close

    RunsAsAccountsCompleted

  12. Repeat the above steps for "SQL Server Default Action Account" and "SQL Server Monitoring Account"

When finished the sql management pack should look something like this.

SQLManagementPackReady

If you want more information on the SQL management pack. Take a look at Kevin Holeman blog. This blog post

Backup Management Pack’s

Standard

Backup all System Center Operations Manager 2012 Management Pack’s. I took the following steps to complete this task.

Launch the System Center Operations Manager shell

OperationsManagerShell

Get-SCManagementPack | Export-SCManagementPack -Path D:\Backup\ManagementPack

OperationsManagerShellBackup

If you are using System Center Operations Manager 2007 r2 Use the following command line:

Get-ManagementPack | Export-ManagementPack -Path D:\Backup\ManagementPack

Installing Update Rollup 6 SCOM 2012 Sp1

Standard

In this blog post I will take you true the steps of installing System Center Operations Manager 2012 Sp1 update Rollup 5 to Update Rollup 6

The following issues are fixed in this Update

  • Service Level Objectives (SLO) dashboards sometimes load in several seconds and sometimes take minutes to load. Additionally, in some cases, the dashboard is empty after it loads.
  • SQL Time Out Exceptions for State data (31552 events) occur when you create Data Warehouse work flows.
  • This update rollup includes a fix for the dashboard issue that was introduced in Update Rollup 5.
  • Adding multiple regular expressions (RegEx’s) to a group definition causes a SQL exception when adding or running the group.
  • The System Center Operations Manager console is slow to load views if you are a member of a custom Operator role.
  • All IBM WebSphere application servers that run on Linux or AIX computers will not be automatically discovered by the Management Pack for Java Enterprise Edition (JEE) if multiple application servers are defined in a single WebSphere profile.

    You can download the Update Rollup 6 form here

    The following steps outline the process of installing the Update

    1. Backup the operations Manager Databases and unsealed Management Pack’s
    2. Install Update to the Management server
    3. Install update to the secondary Management Servers
    4. Install update to the gateway servers
    5. Install update to the ACS servers
    6. Install Update to the Web Console
    7. Install Update to the Operations Manager Console
    8. Run the SQL scripts
    9. Import Management Pack’s
    10. Deploy the update to the agents

    1. Backup the operations Manager Databases and unsealed Management Pack’s

    I did a manual backup from my databases using the SQL Console

    1. Start the "SQL Server Management Studio"
    2. Connect to the Database server
    3. Right click on the database that you want to backup, select "Tasks" and click "Backup

      BackupDatabase

    4. On the "Backup Database Select the setting that you want to use and click "Ok

      BackupRunning

    5. When the Backup is completed click "Ok"
    6. Repeat the steps Above for all the databases

    U can backup your management pack’s using the following command:

    Get-SCManagementPack | Export-SCManagementPack -path D:\Backup\MP

    backupMP

    2. Install Update to the Management server

    1. Extract the cabinet file
    2. Start a "elevated command prompt"
    3. Run the "KB2929885-AMD64-Server.msp"

      kb2929885ManagementServer

    4. Installation is running. This can take some time.

      kb2929885ManagementServerRunning

    3. Install update to the secondary Management Servers

    I installed the update the same way is installed it on the Management Server. So follow Step 2

    4. Install update to the gateway servers

    1. Extract the cabinet file
    2. Start a "elevated command prompt"
    3. Run the "KB2929885-AMD64-Gateway.msp"

      kb2929885Gateway

    4. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.

    5. Install update to the ACS servers

    1. Extract the cabinet file
    2. Start a "elevated command prompt"
    3. Run the "KB2929885-AMD64-ENU-ACS.msp"

      kb2929885Acs

    4. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.

    6. Install Update to the Web Console

    1. Extract the cabinet file
    2. Start a "elevated command prompt"
    3. Run the "KB2929885-AMD64-ENU-WebConsole.msp"

      kb2929885Webconsole

    4. Installation is running. This can take some time.

      kb2929885WebConsoleRunning

    5. The update doesn’t give any feedback. Check the application event-viewer if the setup is finished.
    6. After installing the update, you need to add the following line to the %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file:

      < machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

      I did that using the following steps:

      • Start "Powershell" as administrator and stop the IIS Service "iisreset /Stop"
      • In a text editor such as Notepad, open the application-level Web.config.default file.
      • In the Web.config.default file, locate the "<system.web>" section.
      • Under the "<system.web>" add the following line:

        < machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

      • Start "Powershell" as administrator and stop the IIS Service "iisreset /Start"

    7. Install Update to the Operations Manager Console

    1. If you do not want to restart the computer after you apply the console update, close the console before you apply the update for the console role.
    2. Extract the cabinet file
    3. Start a "elevated command prompt"
    4. Run the "KB2929885-AMD64-ENU-Console.msp"

      kb2929885Console

    5. Installation is running. This can take some time.

      kb2929885WebConsoleRunning

    6. I did a restart of the computer.

    8. Run the SQL scripts

    1. Start the "SQL Server Management Studio"
    2. Connect to the Database server and select the OperationManagerDW" Database

      SelectOperationManagerDW

    3. On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "UR_Datawarehouse" file and then click Open.
    4. When the file is loaded, click "Execute" in the SQL Editor tool bar
    5. Your Result should look something like:

      RowsAffected

    Next we need to run the following script against the OperationsManager database

    1. Start the "SQL Server Management Studio"
    2. Connect to the Database server and select the OperationManager" Database

      SelectOperationManager

    3. On the File menu, click Open, browse to D:\Program Files\System Center 2012\Operations Manager\Server\SQL Script for Update Roll ups , select the "update_rollup_mom_db" file and then click Open.
    4. When the file is loaded, click "Execute" in the SQL Editor tool bar
    5. Your Result should look something like:

      RowsAffected3

    8. Import the management Pack

    1. Start the System Center Operations Manager Console and select the "Administration pane"
    2. Right click "Management Pack" and click "Import Management Packs…"
    3. In the "Import Management Packs" and click "Add" and click "Add from Disk…"
    4. Browse to "D:\Program Files\System Center 2012\Operations Manager\Server\Management Packs for Update Rollups" and select the management Pack’s in that folder
      • Microsoft.SystemCenter.AlertAttachment.mpb
      • Microsoft.SystemCenter.IntelliTraceProfiling.mpb
        • Microsoft.SystemCenter.IntelliTraceCollectorInstallation.mpb which should be installed from SCOM 2012 SP1
        • MediaMicrosoft.Windows.InternetInformationServices.Common.mpb which should be installed from the online catalog
      • Microsoft.SystemCenter.Visualization.Library.mpb
      • Microsoft.SystemCenter.Image.Library.mp
      • Microsoft.SystemCenter.Advisor.Internal.mpb
      • Microsoft.SystemCenter.Apm.Infrastructure.Monitoring.mp
      • Microsoft.SystemCenter.Apm.Infrastructure.mpb
      • Microsoft.SystemCenter.Apm.Library.mpb
      • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp p
      • Microsoft.SystemCenter.DataWarehouse.Reports.mp
      • Microsoft.SystemCenter.DataWarehouse.ServiceLevel.Report.Library.mp
      • Microsoft.SystemCenter.TFSWISynchronization.mpb
      • Microsoft.SystemCenter.Visualization.Component.Library.mp
      • Microsoft.SystemCenter.Visualization.Component.Library.mpb
    5. Click "Install"
    6. Click "Close"

    10. Deploy the update to the agents

    1. Start the System Center Operations Manager Console and select the "Administration pane"
    2. Select " Device Management" and then "Pending Management"
    3. Select the a "Agent" and click "Approve"

      Aprove

    4. On the "Agent Update" page click "Update"

      Update

    5. when you open de the "Agent by Version" you should see something like this:

      Ready

    More information on installing Update Rollup 6 for System Center Operations Manager 2012 sp1 can be found here. To install this Update Rollup 6 I used the deployment plan from Kevin Holman

    Diagnostic and Recovery Time-Out

    Standard

    When I run a Diagnostic and Recovery task and the Diagnostic or Recovery task runs longer then 5 minutes the Diagnostic or Recovery task will fail.

    The Issue

    I have created a unit monitor based on a SNMP Probe Monitor using the following OID: .1.3.6.1.4.1.318.1.1.10.2.2.2.1.4.1. After that I created the following script based recovery task:

    • A Visual Basic script which calls a powershell script. You can download the Visual Basic script from here

    • A Powershell script which runs the time-out script. You can download the Visual Basic script from here

      <?xml version="1.0"?>

    • A Powershell function which is used to calculate the Current Time. You can download the Visual Basic script from here

      <?xml version="1.0"?>

    When you generate an alert. The Recovery task is started but after 5 minutes the Recovery Tasks stops running.

    The Fix

    • Start the "System Center Operations Manager Console" select "Administration" and click "Management Packs"
    • Select the management pack that you saved the recovery task to and in the tasks pane click "Export Management Pack"

      ExportManagementPack

    • Select a path or location where you want to export the management pack to and click "Ok"
    • Open the exported xml and search for the "Recovery ID" element. My part of the code looks like this:

      <?xml version="1.0"?>

    • The Time-out value equals 300 which is equal to 5 minutes. I replaced this Value to 3600 which equals 1 hour. The Code should look something like this:

      <?xml version="1.0"?>

    • Save the XML
    • Start the "System Center Operations Manager Console" select "Administration" and click "Management Packs"
    • CLick "Import Management Pack" and browse tot XML and import the Management Pack
    • Run the test again and the output should look something like this.

      result