System Center 2012 SP1 Operations Manager Upgrading System Center 2012 SP1 Operations Manager System Center 2012 R2 Operations Manager Predrag Oparnica Senior PFE – SCOM Microsoft

Topics What's New in System Center 2012 R2 Operations Manager Things To Do Before Upgrading Upgrade Scenarios Step-by-Step Available Update Rollups Known Issues

What's New in System Center 2012 R2 Operations Manager

What's New in System Center 2012 R2 Operations Manager Fabric Monitoring Microsoft Monitoring Agent Integrating Operations Manager with Development Processes (DevOps) Support for IPv6 Java Application Performance Monitoring System Center Advisor UNIX and Linux Monitoring Fabric Monitoring A close integration between System Center 2012 R2 Virtual Machine Manager and System Center 2012 R2 Operations Manager introduces System Center cloud monitoring of virtual layers for private cloud environments. To get this new functionality, use the System Center 2012 Management Pack for System Center 2012 R2 Virtual Machine Manager Dashboard, which is imported automatically when you integrate Operations Manager and Virtual Machine Manager. For information about how to integrate Operations Manager and Virtual Machine Manager, see Configuring Operations Manager Integration with VMM. The Fabric Health Dashboard shows a detailed overview of the health of your private clouds and the fabric that services those clouds. The dashboard helps you answer questions like “What is the health of my clouds and the fabric serving those clouds?” Fabric Health Dashboard – Monitoring the Health of Private Clouds The Diagram view gives you a diagram of the entire infrastructure and shows the health state of each part of the fabric. The Diagram view helps you answer questions, such as “What is the health of my entire fabric?” Improvements to the diagram ensure that health rolls up and that the relevant fabric components are part of the Diagram View. Fabric Monitoring Diagram View – Displays Health States of Cloud and On-Premise Environments Microsoft Monitoring Agent Microsoft Monitoring Agent is a new agent that replaces the Operations Manager Agent and combines .NET Application Performance Monitoring (APM) in System Center with the full functionality of Visual Studio IntelliTrace Collector for gathering full application profiling traces. Microsoft Monitoring Agent can collect traces on demand or can be left running, which monitors applications and collects traces continuously. Integrating Operations Manager with Development Processes (DevOps) Here are two important changes to the DevOps functionality in System Center 2012 R2 Operations Manager: New Alert Fields of TFS Work Item ID and TFS Work Item Owner In System Center 2012 R2 Operations Manager, you can synchronize Operations Manager alerts and Team Foundation Server (TFS) work items. When synchronization is enabled, IT operations can then assign alerts to the engineering team. Assigning an alert to engineering creates a new work item in TFS. The workflow will track and synchronize any changes that are made to TFS work items and any associated Operations Manager alerts. Integration between System Center 2012 Service Pack 1 (SP1) and TFS used the Ticket ID and Owner fields of the Operations Manager alert to store and display which work item is associated with an alert and who it is assigned to. Beginning in System Center 2012 R2 Operations Manager, two new alert fields, TFS Work Item ID and TFS Work Item Owner, hold these values. These fields are read-only in the Operations Manager console to prevent accidental changes of the values that are controlled in TFS. If you previously personalized any standard alert views or created your own alert views in System Center 2012 SP1 using Ticket ID and Owner fields to display TFS information, you must replace those fields with the TFS Work Item ID and TFS Work Item Owner fields to continue displaying the same information. The previous Ticket ID and Owner fields are still used for synchronization of alerts with incidents in Service Manager Alert Connector. This monitoring capability now allows the opening of APM performance events from Visual Studio IDE as if the performance event was captured during the IntelliTrace historical debugging session. Tightly integrated with TFS Work Item Synchronization Management Pack, this capability instantaneously brings generated IntelliTrace logs to TFS work items assigned to engineering. This can result in streamlining communications between IT Operations and Development and enriching the development experience with analysis of root causes of the application failure, reducing the mean time to recovery (MTTR) for the problems detected by APM. Conversion of Application Performance Monitoring (APM) Performance Events to IntelliTrace format Support for IPv6 In System Center 2012 R2 Operations Manager the Operations console can take IPv6 addresses as input for Network Discovery and display IPv6 addresses in the network-related views. Java Application Performance Monitoring The System Center 2012 Management Pack for Java Application Performance Monitoring lets you monitor Java application performance and exception events by using Operations Manager Application Advisor. You can set method and resource timing for performance events, stack traces for exception events, and set Java specific counters (such as Average Request Time and Requests Per Second) for events. Additionally, you get Operations Manager level alerting on Java application server counters. You can download the management pack from the Microsoft Download Center. System Center Advisor System Center Advisor is an online service that analyzes installations of Microsoft server software. With the latest preview version of Advisor, you can now view Advisor alerts in the Operations Manager Operations console. Advisor collects data from your installations, analyzes it, and generates alerts that identify potential issues (such as missing security patches) or deviations from identified best practices with regard to configuration and usage. Advisor also provides both current and historical views of the configuration of servers in your environment. Ultimately, Advisor recommendations help you proactively avoid configuration problems, reduce downtime, improve performance, and resolve issues faster. For more information about Advisor, see Viewing System Center Advisor Alerts and Advisor online help UNIX and Linux Monitoring Debian GNU/Linux 7 is now supported by the Universal Linux agents and Management Packs UNIX and Linux agents for Operations Manager are now based on the Open Management Infrastructure (OMI) open-source CIM Object Manager.

Things To Do Before Upgrading

Things To Do Before Upgrading Back Up System Center 2012 - Operations Manager Operational database Data Warehouse database Audit Collection Service (ACS) database Custom Management Packs Custom report definition files Computer Certificates System Requirements: SCOM 2012 R2 Minimum Hardware Requirements Minimum Software Requirements Use Operations Manager Sizing Helper tool Upgrade path: SCOM 2012 RTM > SCOM 2012 SP1> SCOM 2012 R2

Upgrade Scenarios

Upgrade Scenarios Single-Server Management Group Distributed Management Group

Step-by-Step

Step-by-Step Pre-Upgrade Tasks ----------------------------- Upgrade a Management Server Upgrade an ACS Collector Upgrade a Gateway Server Upgrade an Operations Console Upgrade an Agent Upgrade a Web Console Upgrade Reporting Upgrade OM2012 SP1 Agents to OM2012 R2 Parallel Environments ------------------------ Post-Upgrade Tasks

Pre-Upgrade Tasks Review the Operations Manager Event Logs Cleanup the Database (ETL Table) Remove Agents from Pending Management Disable the Notification Subscriptions Stop the Services or Disable any Connectors Verify that the Operational Database Has More Than 50 Percent Free Space http://technet.microsoft.com/en-us/library/dn249704.aspx Get-SCOMNotificationSubscription | where-object{$_.Enabled} | Disable-SCOMNotificationSubscription

Upgrade an Management Server Use account with necessary permissions Upgrade from Wizard or Command prompt Start with one MS Don’t upgrade multiple MSs from once Expect event logs on agents during upgrade process Complete upgrade on all MSs Verify MSs version and health after upgrade http://technet.microsoft.com/en-us/library/dn249711.aspx

Upgrade an ACS Collector Use account with necessary permissions Upgrade from Wizard or Command prompt ACS collector must be MS or Gateway http://technet.microsoft.com/en-us/library/dn249711.aspx

Upgrade a Gateway Server Use account with necessary permissions Upgrade from Wizard or Command prompt Gateways need to be upgraded manually Verify Gateway version and health after upgrade http://technet.microsoft.com/en-us/library/dn249698.aspx

Upgrade an Operations Console Use account with necessary permissions Upgrade from Wizard or Command prompt Verify Console version after upgrade http://technet.microsoft.com/en-us/library/dn249713.aspx

Upgrade an Agent Pushed Agents / deployed with SCOM console Will remain in pending state after MSs upgrade Not approve more than 200 agents at once time Verify Agents version and health after upgrade Manually installed Agents / deployed with SCCM Need to be manually upgraded /depl. with SCCM Use account with necessary permissions Upgrade from Wizard or Command prompt http://technet.microsoft.com/en-us/library/dn249715.aspx

Upgrade a Web Console Use account with necessary permissions Upgrade from Wizard or Command prompt Any customizations made to the web.config will be lost (backup web.config) http://technet.microsoft.com/en-us/library/dn249691.aspx

Upgrade Reporting Use account with necessary permissions Upgrade from Wizard or Command prompt http://technet.microsoft.com/en-us/library/dn249722.aspx

Upgrade OM2012 SP1 Agents to OM2012 R2 Parallel Environments Multi-home agents to report on both side SCOM 2012 R2 Agent is capable to report SCOM 2012 SP1 Management Server http://technet.microsoft.com/en-us/library/dn249702.aspx

Post-Upgrade Tasks Re-enable the Notification Subscriptions. Restart or Re-enable the Connector Services (if needed) Re-enable Audit Collection Services (ACS) on agents that were upgraded Verify That the Upgrade Was Successful http://technet.microsoft.com/en-us/library/dn249708.aspx Get-SCOMNotificationSubscription | where {$_.Enabled –like “False”} | Enable-SCOMNotificationSubscription

Demo Upgrading to SCOM 2012 R2

Available Update Rollups

Available Update Rollups SCOM 2012 R2 Update Rollup 1 is available Installation order Management Server(s) Gateway Server(s) Web console server Operations console Apply SQL scripts Manually import the management packs http://support.microsoft.com/kb/2904678/en-us

Known Issues

Known Issues Issues with APM monitoring (resolved in UR1) Upgrade failed (no direct upgrade from RTM to R2) SCOM 2012 RTM > SCOM 2012 SP1 > SCOM 2012 R2

Questions ? 9/22/2018

Senior Premier Field Engineer proparni@microsoft.com Contact Predrag Oparnica Senior Premier Field Engineer proparni@microsoft.com © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION