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:
- 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
- Apply SQL scripts.
- 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.11759.0 (UR1)).
Personally, I prefer to execute the MSP files via PowerShell (RunAs Administrator) console.
Again, the order needs to be:
- Management Servers
- Web Console Role Servers
- 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.***
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:
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.