Menu Close

UR8 for SCOM 2016 – Step by Step

image

KB Article for OpsMgr: https://support.microsoft.com/en-us/help/4514877/update-rollup-8-for-system-center-2016-operations-manager

Download catalog site: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=4514877

Updated UNIX/Linux Management Packs: https://www.microsoft.com/en-us/download/details.aspx?id=29696

Recommended hotfix page: https://kevinholman.com/2009/01/27/which-scom-hotfixes-should-i-apply/

 

Key fixes:

  • Fixed: CPU Spike issues because of workflows running on all agents at the same time is addressed through script optimization and removing the sync time.
  • Fixed: Maintenance mode state changes which are recorded in MaintenanceModeStage table requires grooming when table grows. If the table is large, grooming takes longer and the operation times out with SQLTimeOut exception.
  • Fixed: If a group is renamed in a Management pack, then console shows the new value but Powershell command Get-SCOMGroup returns the old name of group. Database Updates functionality was inconsistent for SCOM group renaming through MP and SCOM Console.
  • Fixed: Reporting – Historical data does not appear, if input reporting end time is before group creation time. With this fix, historic data for a group (if data is available for objects in the group) would be displayed irrespective of group creation time.
  • Fixed: If the registry key under “Computer\HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup\UseMIApi” is set and a Unix/Linux Script task without a parameter is executed then this task fails.
  • Improvement: Sometimes SQL stored procedure “p_SelectForNewTypeCache” takes long time to complete, and SDK service fails to start. This is fixed and above SQL stored procedure will complete faster now.
  • Fixed: In some customer scenarios where SCOM monitors a large number of virtual machines hosted on a single Host, the disk I/O could possibly spike once per hour.  Every hour the HealthService.exe of each Virtual machine writes to the page file.  If a large number of VM’s all boot/initialize at the same time, this could cause the paging to occur simultaneously.  A registry key and a set of values are now provided to disable the memory trimming and control the frequency if impacted.  The general recommendation is to disable Memory trimming in the SCOM agent, by creating these registry keys on all agents – if you are impacted by this.  This will defer to the OS for memory trimming on demand.

             Key:  HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\MemoryTrimming
            
             REG_DWORD Decimal Value:  Enable
             SCOM default existing registry value:   (not present)
             SCOM default value in code = 1
             Enable = 0 (trimming is disabled)  Enable = 1 (trimming is enabled)

             REG_DWORD Decimal Value:  DelayInSeconds
             Time period in seconds the agent waits after initializtion to start trimming
             SCOM default existing registry value:   (not present)
             SCOM default value in code = 120

             REG_DWORD Decimal Value:  PeriodInSeconds
             Recurring period in seconds at which the working set should be trimmed
             SCOM default existing registry value:   (not present)
             SCOM default value in code = 3600
             Minimum value = 3600  Maximum value = 4294967295

 

NOTE:  I get this question every time we release an update rollup:  ALL SCOM Update Rollups are CUMULATIVE.  This means you do not need to apply them in order, you can always just apply the latest update.  If you have deployed SCOM 2016 and never applied an update rollup – you can go straight to the latest one available.

 
Let’s get started

From reading the KB article – the order of operations is:

  1. Install the update rollup package on the following server infrastructure:
    • Management Servers
    • Audit Collection Server (ACS)
    • Web Console Servers
    • Gateway Servers
    • Operations Console Servers
    • Reporting Server
  2. Apply SQL scripts
  3. Manually import the management packs
  4. Apply Agent Updates
  5. Update Nano Agents
  6. Update Unix/Linux MP’s and Agents

 

WHOA Nelly

Before we get started – there are some configuration changes necessary in SQL to support UR6 and later.  UR6 (and later) has some fixes for Scheduled Maintenance, and these require some rights configuration FIRST – BEFORE applying UR6 or later.  Otherwise you might run into some trouble.  If you applied UR6/UR7 and already made these changes, then this step should just be verifying they are correct.

Essentially, you need to:

  1. Open SQL Management studio
  2. Connect to the SQL instance that hosts your OperationsManager database
  3. Select your SQL login for the Management Server Action account, choose properties.
  4. Select “User Mappings”, and Add/verify a user mapping to the MSDB database.
  5. In this user mapping – select db_owner, public, SQLAgentOperatorRole, SQLAgentReaderRole, SQLAgentUserRole

 

image

  1. Now, open the properties for the SQL login for the SDK/DAS account.
  2. Select “User Mappings”, and Add/verify a user mapping to the MSDB database (you may already have one).
  3. In this user mapping – select db_owner, public, SQLAgentOperatorRole, SQLAgentReaderRole, SQLAgentUserRole

image

Note:   If you do not configure these rights, you might see failures in the SCOM logs after applying UR6 (or later) about not being able to synchronize scheduled maintenance jobs, or you might see issues with creating new Schedule Maintenance failing, locking up the console, or even creating large numbers of duplicate jobs.

Repeat this on any SQL instances that are part of a SQL AlwaysOn Availability Group for your OperationsManager database, if applicable.

 

 

Management Servers

image

It doesn’t matter which management server I start with.  I simply make sure I only patch one management server at a time to allow for agent failover without overloading any single management server.

I can apply this update manually via the MSP files, or I can use Windows Update.  I have 2 management servers, and I always recommend a manual installation on management servers, I DO NOT recommend ever using Windows Update.  My first management server holds 3 roles, and each must be patched:  Management Server, Web Console, and Console.

The first thing I do when I download the updates from the catalog, is copy the cab files for my language to a single location, and then extract the contents.

image

 

Once I have the MSP files, I am ready to start applying the update to each server by role.

***Note:  You MUST log on to each server role as a Local Administrator, SCOM Admin, AND your account must also have System Administrator role to the SQL database instances that host your OpsMgr databases.

My first server is a Management Server, Web Console server, and has the OpsMgr console installed, so I copy those update files locally, and execute them per the KB, from an elevated command prompt:

image

This launches a quick UI which applies the update.  It will bounce the SCOM services as well.  The update usually does not provide any feedback that it had success or failure….  but you MIGHT see a reboot prompt.  You can choose “No” and then reboot after applying all the SCOM role updates.

You can check the application log for the MsiInstaller events to show completion:

Log Name:      Application
Source:        MsiInstaller
Event ID:      1036
Description:  Windows Installer installed an update. Product Name: System Center Operations Manager 2016 Server. Product Version: 7.2.11719.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: System Center 2016 Operations Manager Update Rollup 8 Patch. Installation success or error status: 0.

You can also spot check a couple DLL files for the file version attribute:

image

 

Next up – run the Web Console update:

image

 

Lastly – install the Console Update (make sure your console is closed):

image

 

You can check help/about in the console:

image

 

 

Additional Management Servers:

image

Apply the UR updates for Server, Web Console, and Console roles as needed for all additional management servers.  You should only patch one management server at a time to allow for graceful failover of agents and to keep resource pools stable.

 

Updating ACS (Audit Collection Services)

image

One of my management servers is also my ACS Audit Collection Server role.  I will apply the update for that:

image

 

image

 

Note the above image states “Operations Manager 2012”.  This is a known issue. Ignore it.

Updated files:

image

 

 

Updating Gateways:

image

Generally I can use Windows Update or manual installation.  I will proceed with manual:

image

 

The update launches a UI and quickly finishes.

Then I will spot check the DLL’s:

image

 

I can also spot-check the \AgentManagement folder, and make sure my agent update files are dropped here correctly:

image

***NOTE:  You can delete any older UR update files from the \AgentManagement directories.  The UR’s do not clean these up and they provide no purpose for being present any longer.

 

 

Updating Reporting:

image

On your server that hosts the SCOM Reporting role, run the update:

image

 

 

Apply the SQL Scripts

image

In the path on your management servers, where you installed/extracted the update, there are TWO SQL script files.  One for the Operations Database, and one for the Warehouse Database.

image

 

%SystemDrive%\Program Files\Microsoft System Center 2016\Operations Manager\Server\SQL Script for Update Rollups

(note – your path may vary slightly depending on if you have an upgraded environment or clean install)

 

Operations Database update:

First – let’s run the script to update the OperationsManager (Operations) database.  Open a SQL management studio query window, connect it to your Operations Manager database, and then open the script file (update_rollup_mom_db.sql).  Make sure it is pointing to your OperationsManager database, then execute the script.

You should run this script with each UR, even if you ran this on a previous UR.  The script body can change so as a best practice always re-run this.

image

image

Click the “Execute” button in SQL mgmt. studio.  The execution could take a considerable amount of time and you might see a spike in processor utilization on your SQL database server during this operation. 

I have had customers state this takes from a few minutes to as long as an hour. In MOST cases – you will need to shut down the SDK, Config, and Monitoring Agent (healthservice) on ALL your management servers in order for this to be able to run with success.

IF YOU GET AN ERROR – STOP!  Do not continue.  Try re-running the script several times until it completes without errors.  In a production environment with lots of activity, you will almost certainly have to shut down the services (sdk, config, and healthservice) on your management servers, to break their connection to the databases, to get a successful run.

 

Data Warehouse database update:

Next – let’s run the script to update the OperationsManagerDW (Warehouse) database.  Open a SQL management studio query window, connect it to your OperationsManagerDW database, and then open the script file (UR_Datawarehouse.sql).  Make sure it is pointing to your OperationsManagerDW database, then execute the script.

You should run this script with each UR, even if you ran this on a previous UR.  The script body can change so as a best practice always re-run this.

image

image

 

 

Manually import the management packs

image

There are 36 management packs in this update!  Most of these we don’t need – so read carefully.

The path for these is on your management server, after you have installed the “Server” update:

\Program Files\Microsoft System Center 2016\Operations Manager\Server\Management Packs for Update Rollups

However, the majority of them are Advisor/OMS, and language specific.  Only import the ones you need, and that are correct for your language. 

This is the initial import list:

image

image

 

 

What NOT to import:

The Advisor MP’s are only needed if you are connecting your SCOM environment to Microsoft Operations Management Suite / Log Analytics cloud service, which is very rare (Previously known as Advisor, and Operations Insights)

DON’T import ALL the languages – ONLY ENU, or any other languages you might require.

The Alert Attachment MP update is only needed if you are already using that MP for very specific other MP’s that depend on it (very rare)

The IntelliTrace Profiling MP requires IIS MP’s and is only used if you want this feature in conjunction with APM.

So I remove what I don’t want or need – and I have this:

image

 

#Note: If the “Install” button is greyed out – this means you might already have one or more of these MP’s with the same version installed.  Find it by scrolling through each one, the console will tell you if you already have the same version.

 

Update Agents

image

Agents should be placed into pending actions by this update for any agent that was not manually installed (remotely manageable = yes):

image

 

If your agents are not placed into pending management – this is generally caused by not running the update from an elevated command prompt, or having manually installed agents which will not be placed into pending by design, OR if you use Windows Update to apply the update rollup for the Server role patch.

You can approve these – which will result in a success or failure message once complete:

image

You normally can verify the PatchLevel by going into the console and opening the view at: Monitoring > Operations Manager > Agent Details > Agents by Version

image

 

I *strongly* recommend you take a look at this community MP, which helps see the “REAL” agent number in the Administration –> Agent Managed view console:

https://kevinholman.com/2017/02/26/scom-agent-version-addendum-management-pack/

image

 

And my SCOM Management Group Management MP, which will help show you REAL UR levels based on a better discovery.  This has long been a pain point in SCOM:

https://kevinholman.com/2017/05/09/scom-management-mp-making-a-scom-admins-life-a-little-easier/

image

image

 

 

Update UNIX/Linux MPs and Agents

image

You can get the current Unix/Linux MP updates here: https://www.microsoft.com/en-us/download/details.aspx?id=29696

The current version of these MP’s for SCOM 2016 UR8 is 7.6.1092.0  – and includes agents with version 1.6.2-343

Make sure you download the correct version for your SCOM deployment version:

image

Download, extract, and import ONLY the updated Linux/UNIX MP’s that are relevant to the OS versions that you want to monitor.  Here is the FULL list:

image

In my environment – I only monitor RedHat and Universal Linux distributions, so this is my pared down list of MP’s to update:

image

 

This will take a considerable amount of time to import, and consume a lot of CPU on the management servers and SQL server until complete.

Once it has completed, you will need to restart the Healthservice (Microsoft Monitoring Agent) on each management server, in order to get them to update their agent files at \Program Files\Microsoft System Center 2016\Operations Manager\Server\AgentManagement\UnixAgents

 

You should see the new files dropped with new timestamps:

image

Now you can deploy the Linux agent updates:

image

image

Next – you decide if you want to input credentials for the SSH connection and upgrade, or if you have existing RunAs accounts that are set up to do the job (Agent Maintenance/SSH Account)

image

If you have any issues, make sure your SUDOERS file has the correct information pertaining to agent upgrade:

https://kevinholman.com/2016/11/11/monitoring-unix-linux-with-opsmgr-2016/

 

 

Update the remaining deployed consoles

image

This is an important step.  I have consoles deployed around my infrastructure – on my Orchestrator server, SCVMM server, on my personal workstation, on all the other SCOM admins on my team, on a Terminal Server we use as a tools machine, etc.  These should all get the matching update version.

 

Review:

Now at this point, we would check the OpsMgr event logs on our management servers, review the Management Group Health dashboard, check for any new or strange alerts coming in, and ensure that there are no issues after the update.

 

Known Issues:

1. The “Operations Manager” Event log on SCOM servers is forced back to the default value of 16MB after you apply UR8.  If you customized this value on Management Servers (and I recommend doing this) to a larger value such as 60-100MB, this value will be set back to 16MB.  This will result in a Management Server event log that is too small for best practices, and you should set this back to your previously modified value.

2.  Customized registry values might be wiped out by UR8 and reset to default values.  For instance, one of the things I change on SCOM *Management servers*, is the registry value at “HKLM\SYSTEM\CurrentControlSet\services\HealthService\Parameters\Persistence Checkpoint Depth Maximum”.  This is forced back to a default value of 20971520 after you apply the Update Rollup.  I recommend this value be set to 104857600 on SCOM management servers.  There could be others.  If you customize Registry settings on SCOM Agents or Management Servers, you should verify them after applying any Update Rollup as part of your testing, and make a plan to automate fixing them if necessary.

3.  UR8 will overwrite the registry path at “HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\InstallDirectory” and modify this path to the C: drive, even when the SCOM Agent is installed to some other drive letter, such as the E: drive.  This can break some automations.  You should correct this registry entry via MP automation if this affects you.

4.  The ACS update shows “Operations Manager 2012” in the UI but is actually for SCOM 2016.

9 Comments

  1. Gino

    MemoryTrimming Issue – Wow! I had logged a ticket about this exact behaviour over a year and a half ago. Nice to see it was finally acknowledged.

  2. Gerald Versluis

    Hi Kevin,

    Great article, as always. I do have one question however: I know that the URs should be cumulative, but the release notes state very clearly – as they did with UR7 – that you must have the Server part of UR2 installed. The UR6 notes state that this is only necessary if you want to be able to roll back UR6 at a later time. The notes for UR7 and UR8 no longer mention the “only if you want to roll back” bit, they just state the Server UR2 must be installed.
    I’m 99% sure this is a documentation thing, but can you ask the team to look into this?

    • Kevin Holman

      I have tried to make this clear as I can. I have also given this feedback to the product group many times. UR2 is NOT a prerequisite. UR2 simply fixed a bug in rolling back/uninstalling a UR. ANY UR after UR2 also contains this fix. It is such a miniscule scenario, I don’t even give it credence to document. In 13 years of supporting SCOM, I have never seen a need to “uninstall” a rollup, and this is technically impossible anyway, once you import the MP’s or run the SQL scripts, it would be unsupported to roll back a management server or GW UR.

    • Gary

      I can confirm what Kevin says. I have just upgraded from 2016 RTM straight to UR8 by following the instructions on this page without issue.

  3. Alexander

    Hey Kevin,

    Thank you for the great Guide!

    We have one small problem when we rollout scom agents on our Linux Clients. The update overwrites all our security settings in the omiserver.conf file. For example it enables SSLv3 again by default. We therefore would have to manually change all config files on all Servers again (we have a few different conf files so we cant just rollout one for all).
    Is there any way to keep old omiserver.conf settings when upgrading scom agents on Linux?

  4. Rishab

    Hi Kevin,

    We are having high Memory usage (process name MonitoringHost.exe) in 2016 UR8, any troubleshooting steps you can recommend.

Leave a Reply

Your email address will not be published. Required fields are marked *