My personal notes for installing SCOM 2016 Update Rollup 2, Step-by-Step. UR2 (Update Rollup) has a lot improvements, please see below the many updates being provided in this UR. Two fixes I am seeing that makes me happy, is having the alerts view fixed… Previously alerts within the Alerts view would still appear even after the alert was closed. Also, the Get-SCOMGroup cmdlet consistently failed when there was a great number of groups within an environment.
It is highly recommended to upgrade your lab/Dev environments first before upgrading your Production environment(s). The step by step procedures below are the steps I took and in no way shape or form do I accept responsibility for any data loss, and/or issues within your environment. It is advised to always take a backup of your SQL databases and/or snapshots of your SCOM environment(s). Please take these notes as suggestions. Always refer to Microsoft’s KB (posted below) for full documentation steps.
Here are the key updates for UR2 (source Microsoft):
Issues that are fixed in Operations Manager Update Rollup 2
- When you use the Unix Process Monitoring Template wizard (adding a new template) to monitor processes on UNIX servers, the monitored data is not inserted into the database because of the following failure (Event ID 10801)
- When a management server is removed from the All Management Servers Resource Pool, the monitoring host process does not update the TypeSpaceCache.
- When alerts are closed from the Alerts view after you run a Search, the closed Alerts still appear in the View when the Search is cleared.
- When you press Ctrl+C to copy an alert in Operations Manager Alert view and then press Ctrl+V to paste it to Notepad, the Created time is in UTC time, not local time.
- Groups disappear from Group view after they are added to a Distributed Application.
- IM notifications from Operating Manager to Skype fail when an incorrect exception causes NullReferenceException in the SipNotificationTransport.Send method.
- When the maintenance mode option for the dependency monitor is set to “Ignore,” and the group (consisting of the server to which this dependency monitor is targeted) is put in Maintenance mode, the state of the monitor changes to critical and does not ignore maintenance mode.
- Because of a rare scenario of incorrect computation of configuration and overrides, some managed entities may go into an unmonitored state. This behavior is accompanied by 1215 events that are written to the Operations Manager log.
- Recovery tasks on “Computer Not Reachable” Operations Manager Monitor generate failed logons on SCOM Agents that are not part of the same domain as the management groups.
- The ManagementGroupCollectionAlertsCountRule workflow fails and generates a “Power Shell Script failed to run” alert.
- Get-SCOMGroup cmdlet fails when thousands of groups are created in Operations Manager.
- Organizational unit properties for computers that are running Windows are not discovered or populated. This discovery is part of the System Center Internal Library MP. After this update, organizational unit properties will be discovered for all computers that are running Windows.
- When the Operations Manager Health Service agent starts, and the agent is configured for AD integration, if the agent cannot contact Active Directory at all, it immediately goes dormant and stops trying to connect and obtain the policy from Active Directory.
Issues that are fixed in the UNIX and Linux management packs
- SHA1 is deprecated, and SHA256 certificates are now supported on the management server that’s used to sign the Unix/Linux OMI certificate.
- OMI does not work on Linux servers configured for FIPS compliance.
- Avg. Physical disk sec/transfer performance counters are not displayed for Hewlett Packard computers.
- OMI displays incorrect Memory information on Solaris 10 computers.
- Network adapter performance is not displayed for SLES 12 x64 platform in the Operations Manager Console.
- Cannot discover file systems on HPUX 11.31 IA-64 computers with more than 128 disks. Previously it supported only 128 VGs. Now support is extended to 256 VGs.
- Deep monitoring cannot be started successfully on some JBoss applications because the discovery of the JBoss application server sets the Disk Path for the JBoss server incorrectly. Deep monitoring was not being started in JBoss stand-alone mode when a nondefault configuration was used.
Install Procedure
Once you are ready to begin your upgrade, it is recommended you do the following server/roles in the order specified below:
- Install the update rollup package on the following server infrastructure in the order below:
- Management server(s)
- Agents; Nano Agents
- Web console server role computers
- Gateway(s)
- Operations console role computers
- Apply SQL script(s).
- Manually import the management packs.
- Apply the nano agent update to manually installed agents, or push the installation from the Pending view in the Operations console.
Once you have downloaded the rollup files, I like to extract and only keep the language I need, in this case, ENU (English). You will need to install these with Administrative rights, I like to use PowerShell as Local Administrator. It really does frustrate me, as there is no indication that the rollup installed correctly, (other than looking at the file version number change via File Explorer; Build Number 7.2.11719.0 (RTM) –> 7.2.11822.0 (UR2)).
Personally, I prefer to execute the MSP files via PowerShell (RunAs Administrator) console.
Again, the order needs to be:
- Management server(s)
- Agents; Nano Agents
- Web console server role computers
- Gateway(s)
- Operations console role computers
Once the Update Rollups are installed, you will now need to apply the SQL script(s). In this UR, only the Operations Manager (OpsMgr) Database is affected.
The script(s) can be found here, “%SystemDrive%\Program Files\Microsoft System Center 2016\Operations Manager\Server\SQL Script for Update Rollups\“
Please note, the user executing these scripts needs to have read and write permissions to the database(s).
Once you have successfully executed the SQL script, you will now need to import the updated Management Packs (MP). These MPs can be found here, “%SystemDrive%\Program Files\Microsoft System Center 2016\Operations Manager\Server\Management Packs for Update Rollups\“.
You will need to import the following MPs, please see below:
- Microsoft.SystemCenter.Internal.mp
- Microsoft.SystemCenter.2007.mp
- Microsoft.SystemCenter.Advisor.Internal.mpb
- Microsoft.SystemCenter.OperationsManager.Library.mp
- Microsoft.SystemCenter.Image.Library.mp
- Microsoft.SystemCenter.Visualization.Library.mpb
- Microsoft.SystemCenter.Advisor.mpb
- Microsoft.Windows.InternetInformationServices.CommonLibrary.mp
- Microsoft.SystemCenter.AlertAttachment.mpb
- Microsoft.SystemCenter.IntelliTraceProfiling.mpb
- Microsoft.SystemCenter.SyntheticTransactions.Library.mp
- Microsoft.SystemCenter.OperationsManager.AM.DR.2007.mp
- Microsoft.SystemCenter.OperationsManager.SummaryDashboard.mp
- Microsoft.SystemCenter.Advisor.Resources.(LANGUAGECODE_3LTR).mpb
Don’t forget, once the MPs have been imported, you should now go back to your Pending Management view, under the Administrations pane, and update all servers.
And that is that! You are now on the latest and greatest System Center Operations Manager release for SCOM 2016.
SCOM & Other Geeky Stuff 
Reblogged this on Cloud & Virtualization Complete Guide.
LikeLike