Install SCOM 2016 Update Rollup 1 – Step by Step

scom splash screen

In the previous article I have described the process to install SCOM 2016 , since that article was published Microsoft released update rollup 1 for SCOM 2016.

In this article I will ilustrate the process to follow to instsall SCOM 2016 Update Rollup 1 on single or multi system SCOM deployment.

[su_note note_color=”#ffff96″ text_color=”#000000″ radius=”5″]Note: An offline version of this article in PDF format is available in the e-book section of the site or over TechNet Gallery [/su_note]

Install SCOM 2016 Update Rollup 1 – Installation Order

Before describing the actual installation steps it is necessary to note the following requirements and best practices:

  • Update Rollup installation must be performed as an administrator
  • SCOM Console should be closed before applying the update (this is to avoid server’s reboot)
  • If User Account Control is enabled run the .msp file from an elevated command prompt
  • The account used to install the update must have the System Administrator rights both on the Operational and Data Warehouse Databases

Further to the above list Microsoft recommends installing the update as soon as possible after SCOM Deployment, while I have no hard proof of this I think it has to do with a compatibility issue between SCOM 2016 and October 2016 Cumulative Update for Windows Server 2016.

Install SCOM 2016 Update Rollup 1 Step by Step

The high level installation steps are as follows with point number 1 applying mainly to multi system deployments which should not the case in a lab environment

  1. Update Rollup package should be installed in the following order on infrastructure servers
  • Management Server(s)
  • Web Console Server role
  • Operations Console Role computer(s)
  1. Apply SQL Script (described below)
  2. Import Updated Management Packs
  3. Apply the nano agent update to manually installed agents or push the installation from the Pending view in the Operations Console (this of course only applies if you’re using Nano servers)

Once ready to perform installation download necessary files from Microsoft Update Catalog


Update is multi-language which means when downloaded and extracted you will have multiple files with the various supported language files but of course you only need to install language files supported/needed in your  deployment. I generally just delete unneeded files.

Open an elevated PowerShell or Command Prompt session, navigate to the folder where files have been downloaded and launch the .msp file (again order is management server, web console and operation console)


Installation will start but keep in mind there will be no success/failure message, I wonder if Microsoft will ever implement such feature for us mortals to know what’s going on, so just go through the installation of all update files.

Once all update files have been installed open SQL Management studio and run the script that can be found under %SystemDrive%Program FilesSystem Center 2016Operations ManagerServerSQL Script for Update Rollups


Script needs to be run against the OperationsManager database and NOT the OperationsManagerDW one


Once the SQL Script has been executed successfully updated management packs need to be imported. Updated MPs can be found under %SystemDrive%Program FilesMicrosoft System Center 2016Operations ManagerServerManagement Packs for Update Rollups


Open the Operations Console and navigate to [Administration] / [Management Packs] right-click on the node and finally select Import Management Packs






Now navigate to the Pending Management Node and update all server’s agents to the latest SCOM release.


Congratulations you’ve just updated your SCOM 2016 to Update Rollup1!


Leave a Reply

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

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

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s