Step-by-Step – SCOM 2016 Update Rollup 1 (UR1) Install Procedure

Well, that was fast… System Center/Microsoft Operations Manager (MOM) team just released Update Rollup 1 for SCOM 2016, only weeks after the System Center 2016 suite and Windows Server 2016 were released.

The MOM team did not indicate what exactly the fixes were in this Update Rollup, so your guess is good as mine. However, I believe one of the issues that may have been resolved was the SCOM 2012R2/SCOM 2016 Console crash due to the October Cumulative Update, October 2016 Windows Server Cumulative Update(s).

Below 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 UR1 (source Microsoft):

Issues that are fixed in this update rollup can be found here, https://support.microsoft.com/en-us/kb/3190029

Once you are ready to begin your upgrade, it is recommended you do the following server/roles in the order specified below:

  1. Install the update rollup package on the following server infrastructure in the order below:
  • Management server(s)
  • Web console server role computers
  • Operations console role computers
  1. Apply SQL scripts.
  2. Manually import the management packs.
  3. 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.11759.0 (UR1)).

1

2

3

Personally, I prefer to execute the MSP files via PowerShell (RunAs Administrator) console.

Again, the order needs to be:

  1. Management Servers
  2. Web Console Role Servers
  3. Operations Console Role Servers

Once the Update Rollups are installed, you will now need to apply the SQL scripts. In this UR, only the Data Warehouse is affected.. However, before doing the SQL part, I highly recommend rebooting all of the SCOM Management Server(s), as none of the installers requested a reboot. I ran into some errors with the SQL script update. After a reboot, the script executed just fine.

The scripts 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).

Execute the flowing SQL script on Data Warehouse DB SQL Server against OperationsManagerDW database, UR_Datawarehouse.sql.

*** !WARNING! AT THE TIME OF THIS POST, MICROSOFT’S KB IS WRONG! I have reported the incorrect files/documentation notes to their MOM team. Please note, after the MSP files have extracted, only the “update_rollup_mom_db” is to be found, this script needs to be run against the OperationsManager Database NOT the Data Warehouse.***

4

5

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.Advisor.Internal.mpb
  • Microsoft.SystemCenter.OperationsManager.Library.mp
  • Microsoft.SystemCenter.Image.Library.mp
  • Microsoft.SystemCenter.Visualization.Library.mpb
  • Microsoft.SystemCenter.Advisor.mpb
  • Microsoft.SystemCenter.AlertAttachment.mpb
  • Microsoft.SystemCenter.IntelliTraceProfiling.mpb
  • Microsoft.SystemCenter.2007.mp

6

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.

7

And that is that! You are now on the latest and greatest System Center Operations Manager release for SCOM 2016.

Advertisements

21 thoughts on “Step-by-Step – SCOM 2016 Update Rollup 1 (UR1) Install Procedure

  1. When I run the MSP files for the update, nothing appears to happen after it closes out. And the file versions still say 7.2.11719.0. No errors in event log.

    Like

      1. I get a SQL script error, this is a fresh SCOM 2016 install:
        Msg 207, Level 16, State 1, Procedure fn_KnowledgeArticleId, Line 133
        Invalid column name ‘ManagementPackId’.
        Msg 207, Level 16, State 1, Procedure fn_KnowledgeArticleId, Line 133
        Invalid column name ‘MPName’.
        Msg 207, Level 16, State 1, Procedure fn_KnowledgeArticleId, Line 133
        Invalid column name ‘MPKeyToken’.
        Msg 207, Level 16, State 1, Procedure fn_DisplayStringId, Line 161
        Invalid column name ‘ManagementPackId’.
        Msg 207, Level 16, State 1, Procedure fn_DisplayStringId, Line 161
        Invalid column name ‘MPName’.
        Msg 207, Level 16, State 1, Procedure fn_DisplayStringId, Line 161
        Invalid column name ‘MPKeyToken’.
        Msg 207, Level 16, State 1, Procedure fn_FolderItemId, Line 184
        Invalid column name ‘ManagementPackId’.
        Msg 207, Level 16, State 1, Procedure fn_FolderItemId, Line 184
        Invalid column name ‘MPName’.
        Msg 207, Level 16, State 1, Procedure fn_FolderItemId, Line 184
        Invalid column name ‘MPKeyToken’.

        Like

  2. I had a similar error. After rebooting all affected Management Servers, and re-executing the script, it was successful.

    Should note, I have reached out to the MOM (Microsoft Operations Manager) team to indicate an issue with the MSP files and documentation on TechNet — The documentation indicates to run the UR_Datawarehouse.sql file against the Data Warehouse DB, however after running the MSP files, this script is not to be found, only the Update_Rollup_Mom_DB.sql. The Update_Rollup_Mom_DB.sql name would indicate it needs to be run against the OpsMgr DB (as previous UR’s).

    Either the script name is wrong, or the DW script is missing. However, when running the Update_Rollup_Mom_DB against the DW, it does execute successfully.

    Like

      1. Try to disconnect your SQL session, and re-connect. Then, re-run the script. Is the script being ran locally, or from a Management Server?

        If all fails, I would say, wait for Microsoft/MOM team to get back on the documentation errors.

        Like

      2. I’m local on the SQL server. The error revolves around MPs. Maybe something I haven’t done yet since it’s a new install?

        ________________________________

        Like

      3. I meant, are you copying and saving the script locally on your SQL server, or running it directly from the SCOM server?

        Also, the errors you have mentioned pertain to SQL, not the MPs. Once you have applied the DW SQL script, then you can proceed with the MPs.

        Like

      4. The errors from SQL are for MP’s columns in the database is what I mean. I am running the script within management studio, on the SQL server. Kind of frustrating a fresh install has this issue. One difference I have is two management servers. But I ran the update on both, and rebooted both before trying to run the script.

        Any other suggestions? Or should I call Microsoft?

        Like

      5. If you can wait it out for Microsoft to get back to the issues indicated in their KB, then wait. If not, I would call Microsoft. I would be surprised if they have a fix, as the UR was released days ago. Is your environment at least functional for now?

        Like

      6. What version is your console file?
        C:\Program Files\Microsoft System Center 2016\Operations Manager\Console
        Microsoft.EnterpriseManagement.Monitoring.Console

        Mine still says 7.2.11719.0, but other files like Microsoft.EnterpriseManagement.Monitoring.Components.dll show the new version.

        Like

      7. It was a bug with some of the management packs I had added, MS gave me the work around by removing them pre-update through PowerShell, then re-adding them afterwards.. I would not recommend this update and wait for the next one when perhaps they can get their ducks in a row after it’s been out for a while.

        From: Carter, Jason
        Sent: Wednesday, October 19, 2016 2:50 PM
        To: ‘SCOM & Other Geeky Stuff’
        Subject: RE: [New comment] Step-by-Step – SCOM 2016 Update Rollup 1 (UR1) Install Procedure

        What version is your console file?
        C:\Program Files\Microsoft System Center 2016\Operations Manager\Console
        Microsoft.EnterpriseManagement.Monitoring.Console

        Mine still says 7.2.11719.0, but other files like Microsoft.EnterpriseManagement.Monitoring.Components.dll show the new version.

        Like

    1. HI Mark, thanks for that. This blog post was done right around the time of the release of UR1. There were several issues with the documentation from MSFT. I am positive the documentation was updated after the initial release of UR1 as I personally submitted documentation error issues to the System Center team(s).

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s