• When you run the Agents module version 1.6.2-337, you may receive the following alert: Module was unable to convert parameter to a double value
• When you run System Center 2016 Operations Manager in an all-French locale (FRA) environment, the Date column in the Custom Event report appears blank
• The Enable deep monitoring using HTTP task in the System Center Operations Manager console doesn't enable WebSphere deep monitoring on Linux systems.
• When overriding multiple properties on rules that are created by the Azure Management Pack, duplicate override names are created. This causes overrides to be lost.
• When the heartbeat failure monitor is triggered, a "Computer Not Reachable" message is displayed even when the computer is not down
• The Get-SCOMOverrideResult PowerShell cmdlet doesn't return the correct list of effective overrides
• When creating a management pack (MP) on a client that contains a Service Level (SLA) dashboard and Service Level Objects (SLO), the localized names of objects aren't displayed properly if the client's CurrentCulture settings don't match the CurrentUICulture settings. In cases where the localized settings are English English, ENG, or Australian English, ENA, there's an issue when the objects are renamed.
• The Event ID: 26373 error, which may cause high memory consumption and affect server performance, has been changed from a “Critical” message to an “Informational” message.
• The Application Performance Monitoring (APM) feature in System Center 2016 Operations Manager Agent causes a crash for the IIS Application Pool that's running under the .NET Framework 2.0 runtime. Microsoft Monitoring Agent should be updated on all servers that use the .NET Framework 2.0 application pools for APM binaries update to take effect. Restart of the server might be required if APM libraries were being used at the time of the update.
• The UseMIAPI registry subkey prevents collection of processor performance data for RedHat Linux system. Also, custom performance collection rules are also impacted by the UseMIAPI setting
• Organizational Unit (OU) properties for Active Directory systems are not being discovered or populated
• The Microsoft.SystemCenter.Agent.RestartHealthService.HealthServicePerfCounterThreshold recovery task fails to restart the agent, and you receive the following error message: LaunchRestartHealthService.ps1 cannot be loaded because the execution of scripts is disabled on this system
• The DiscoverAgentPatches.ps1 script in Microsoft.SystemCenter.Internal.xml fails and you experience an exception
• An execution policy has been added as unrestricted to PowerShell scripts in Inbox management packs
• SQL Agent jobs for maintenance schedule use the default database. If the database name is not the default, the job fails
• This update adds support for OpenSSL1.0.x on AIX computers. With this change, System Center Operations Manager uses OpenSSL 1.0.x as the default minimum version supported on AIX, and OpenSSL 0.9.x is no longer supported

• Reporting
• Agent
• Server
• Web Console
• Console
• Gateway
• ACS

• When you try to upgrade System Center 2012 R2 Operations Manager Reporting Server to System Center 2016 Operations Manager reporting server
• Recovery tasks on "Computer Not Reachable" messages in the System Center Operations Manager Monitor generate failed logons for System Center Operations Manager Agents that are not part of the same domain as the Management Groups.
• When a Management Server is removed from the All Management Servers Resource Pool, the monitoring host process do not update the Type Space Cache.
• SHA1 is deprecated for the System Center 2012 R2 Operations Manager Agent and SHA2 is now supported.
• Because of incorrect computations of configuration and overrides, some managed entities go into an unmonitored state. This behavior is accompanied by event 1215 errors that are logged in the Operations Manager log.
• IntelliTrace Profiling workflows fail on certain Windows operating system versions. The workflow cannot resolve Shell32 interface issues correctly.
• There is a character limitation of 50 characters on the custom fields in the notification subscription criteria. This update increases the size of the limitation to 255 characters.
• You cannot add Windows Client computers for Operational Insights (OMS) monitoring. This update fixes the OMS Managed Computers wizard in the System Center Operations Manager Administration pane to let you search or add Windows Client computers.
• When you use the Unix Process Monitoring Template wizard to add a new template to the monitor processes on UNIX servers, the monitored data is not inserted into the database. This issue occurs until the Monitoring Host is restarted.

• RHEL 7 on Power8 is now supported in System Center2012 R2 Operations Manager

• SHA1 is deprecated and SHA2 is now supported on the management server that's used to sign the UNIX/Linux Operations Manager i (OMi) certificate.
• OMi start attempts fail on all FIPS-enabled UNIX/Linux systems. This fix updates the agents to support FIPS-enabled systems.
• The Average Physical disk sec/transfer performance counters are not displayed for Hewlett Packard systems.
• OMi displays incorrect memory information for Solaris 10 systems.
• The Network Adapter Performance counter is not displayed for SLES 12 x64 platforms in the console.
• You can't discover file systems on HPUX 11.31 IA-64 computers that have more than 128 disks. Previously, only 128 VGs were supported. This update extends support to 256 VGs.
• Deep monitoring can't be started successfully for some Jboss applications because the discovery of the Jboss application server sets the DiskPath for the Jboss server incorrect. Deep monitoring is not started in JBoss stand-alone mode when a nondefault configuration is used. This update provides additional support for JBoss stand-alone mode.

1. Create a Run As Account,
2. Create a Run As Profile,
3. Create a Channel,
4. Create a Subscriber,
5. Create a Subscription,

• Create a Run As Account
  • First we create a Run As Account. In Operations Manager console go to "Administration" pane and then open "Accounts" under "Run As Configuration". Click "Create Run As Account" under Tasks pane. Select "Simple Authentication" for account type and write a name for this account.
    
  • Type an email address in account name area. This email address should be external email address like hotmail, gmail etc. I will use a hotmail account for this area. For example externaladmin@hotmail.com. Type password twice and then continue.
    
  • Select More Secure and then click create.
    
  • After create user account open properties and configure distribution. This account should be distribute to "Notifications Resource Pool".
    
• Create a Run As Profile
  • Second step is to create a Run As profile. We use run as profiles for give special rights to perform specific action. In Operations Manager console go to "Administration" pane and then open "Profiles" under "Run As Configuration". Click "Run As profile" under tasks pane. It is important to add this account to "Notifications Internal Library" management pack. If you don't select this management pack you can't select account for sending notifications via external email server and account.
    
  • In this screen I added "Simple Email Account" account to this profile. So, this account will be used for sending notifications via external mail server.
    
• Create SMTP Channel,
  • To send email via external smtp server, we should create a channel. In this channel we will specify an email server, port number and account to authenticate. In Operations Manager console go to "Administration" pane and then open "Channels" under "Notifications". Click "New" and point "E-Mail (SMTP)" under "Tasks" pane. Type a name for this channel, then next,
    
  • Click add button to add external email server information. I used Hotmail servers to send email.
    Smtp server: smtp.live.com Port Number: 587 Authentication Method: External Email Authentication Run as profile of exnternal email account: External Email Account Profile
  • Click next and then finish wizard.
    
• Create Subscriber
  • Subscriber is a user or a group to recieve notifications from operations manager. In Operations Manager console go to "Administration" pane and then open "Subscriber" under "Notifications". Click "New" under "Tasks" pane. Type a name for subscriber name. Subscriber name is not email address. It is only for describing subscriber.
    
  • I selected send notifications always.
    
  • In this screen we create recipient addresses for each channel. Click "Add" to add recipients.
    
• Create a Subscription,
  • Last step is to create subscription. With this step we specify which type of alerts will send to recipients with which channel. In Operations Manager console go to "Administration" pane and then open "Subscriptions" under "Notifications". Click "New" under "Tasks" pane. Type a name for subscription. For example "All Alerts".
    
  • In this article I would like to send all alerts. But in real world you should filter the alerts what you would like to send.
    
  • Click add and select a subscriber,
    
  • Click Add to select a channel,
    
  • Click finish.
    

1. Prerequisites,

   In this script, we will test connectivity of an agent. If we couldn't connect to agent, then we will test DNS Name resolution of this agent. So, we need DNS aging and scavenging options have to be active. When this option active, DNS records (dynamically registered records) removed from DNS database automatically. By default, aging and scavenging of resource records is disabled. These options must be enabled, both at the DNS Server and on the zone. You can read details about aging and scavenging here. If you enable these options, removed servers resource records deleted automatically by DNS Server.

   If you have any agents that can't be resolve hostname – IP address information, you may add hostname – IP address information on hosts file located in management server. Because our script test DNS name resolution and connectivity with ping command. If you don't add address information to DNS Server or hosts file, you can delete active agents that running on workgroup or another domain.

2. Writing Custom PowerShell script,
   First we need to add some assemblies to our script to connect and manage operations manager.

Part 2 – Installing Operations Manager

1. Accounts
2. Setup
3. Initial settings - Licensing

Accounts

Setup

1. Logon to the server by using an account that has local administrative rights,
2. Run setup.exe as administrator,
   
3. In setup screen click "Install" to start wizard,
   
4. In "select features to Install" screen, Select the roles you want to install. In this scenario we select all features. Noticed that, you can select Reporting Server feature only if SQL Reporting service is installed. Click next,
   
5. In "select Installation location" screen you don't have to change location. Click next,
   
6. If complete installation of prerequisites in Part 1, In Prerequisites screen you see All prerequisites have passed. Click next,
   
7. In "Specify an installation option" screen choose to "Create the First Management Server in a new Management Group" and then give a special name for your Management Group. I chose SCOMMG for management group name. when you install agent software on a Windows Server, you have to specify this management group name. Click next,
   
8. Accept the EULA and then click Next,
   
9. On the Configure the operational database screen specify SQL Server Name and instance. Our SQL installation is located same server with the management server. So, type SCOM16 to Server Name area. Click Next,
   
10. On the Configure the data warehouse database screen specify SQL Server Name and instance. Our SQL installation is located same server with the management server. So, type SCOM16 to Server Name area. Click Next,
    
11. SQL Server instance for reporting services screen click next. If you don't select Reporting Services option on the feature selection screen, this screen will not be shown. Click Next,
    
12. Do not change any option in "Specify a web site for use with the Web console" screen and click Next,
    
13. Chose mixed authentication for Web console authentication mode then click Next,
    
14. On the "configure operations manager accounts fill appropriate user accounts. Create these accounts on the domain controller as domain account. You can use the following table;

1. On Diagnostic and usage data screen, click next,
   
2. On Microsoft update screen click next,
   
3. Installation summary screen click next,
   
4. When installation finished close the setup window.
   

Initial Settings - Licensing

1. Logon to operations manager server with local administrative rights and operations manager admin rights.
2. Click start menu and find "operations manager shell". Then click to open Shell screen.
   
3. Type following command to enter your product key. Change X's with your product key. You must use elevated permissions to use Set-SCOMLicense cmdlet.
   Set-SCOMLicense -ProductId XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
4. Type "Y" t confirm license then restart your server to make sure that these changes are applied correctly
5. You can check license with this command.
   Get-SCOMManagementGroup | ft SkuForLicense, Version, TimeOfExpiration

1. Part 1 - Preparing environment
2. Part 2 - Installing Operations Manager

Part 1 - Preparing Environment

1. Environment
2. Requirements and Prerequisites
3. Scenarios
4. Install prerequisites

Environment

Requirements and Prerequisites

Hardware

Server Operating System

Microsoft Monitoring Agent for Windows Platforms

Web Console requirements

Management Server

Console

Reporting Server

SQL Requirements

Accounts

In-Place Upgrade

Scenarios

Single-server deployment

Distributed Deployment

Installing

High Steps

1. Windows Server Feature and Role installation
2. SQL Server installation options
3. Change SQL Agent service startup state
4. Installing Report Viewer Controls
5. Installing Operations Manager 2016

Detailed Steps

Windows Server Feature and Role installation

1. Open a PowerShell screen with administrative privilege
   
2. Replace "sources\sxs" folder address for your computer and copy/paste to PowerShell screen.
   Import-Module ServerManager Install-WindowsFeature -Name NET-Framework-Core -Source C:\sources\sxs -Restart:$false Add-WindowsFeature Web-Server, NET-HTTP-Activation, NET-WCF-HTTP-Activation45, Web-Mgmt-Console, Web-Net-Ext, Web-Net-Ext45, Web-Static-Content, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Http-Logging, Web-Request-Monitor, Web-Filtering, Web-Stat-Compression, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Metabase, Web-Asp-Net, Web-Windows-Auth, Windows-Identity-Foundation

SQL Server installation options

1. Database Engine Services with Full-Text Search option and Reporting Service with Native Option.
   
2. SQL Collation must be SQL_Latin1_General_CP1_CI_AS.
   
3. Authentication mode is Windows. You have to add an account at least. I added my domain administrator account. You can create a special group, for example SCOMAdministrators named and add this group as a SQL Server Administrators.
   
4. You can install management tools from Microsoft Download Center. Setup file is about 900MB. (SSMS-Setup-Enu.exe)

Change SQL Agent service startup state

1. On the SQL Server open services.msc mmc console and find "SQL Server Agent (MSSQLSERVER)"
   
2. Open properties with Double click.
   
3. Change startup type from manual to automatic then click start to start service. Then click OK to close properties screen.
   
4. You can close services.msc screen.

Installing Report Viewer Controls

1. Double click to setup file,
2. Click next,
3. Accept eula and click next,
   
4. Click Install button to install,
   
5. Click finish button to close setup.
   

Operations Manager (KB3190029)

Virtual Machine Manager (KB3190598), (KB3190597)

Data Protection Manager (KB3190600)

Orchestrator (KB3190602), (KB3190603), (KB3190604)