Upgrading #OpsMgr 1801 to 1807 - Fieldnotes

Upgrading #OpsMgr 1801 to 1807 - Fieldnotes

My Fieldnotes are quick, unrefined notations and reflections from the field.
Content may be obvious and unnecessary to some, useful to others. The main purpose is for them to be used as a searchable notebook.
These Notes are not to be seen as a manual, a how-to or a set of instructions, but rather a collection of thoughts, reflections and experiences from my field-work.


Upgrades from OpsMgr (SCOM) 1801 to 1807 is generally a safe operation. Can be done using Windows Update if you want to, but I would suggest only letting Management Servers, Reporting Servers and Web Console servers pre-load the update for a controlled update at a suitable time.

I general, the updates goes smooth, but you still have to run the SQL-script(s) and import the updated Management Packs provided with the update. This should be done directly after updating the last Management Server.


Updating the Management Servers

Fairly quick update, may need a restart afterwards.

On occasion, especially if the patch has to wait on shutting down the management server services (healthservice, omsdk, cshost) due to backlogs or high load, it might fail at replacing the binaries. You will notice this as the management server will go grey in the SCOM Console and you might find connectivity errors in the OperationsManager eventlog.
If this happens, can be fixed by simply applying the patch again after a reboot.

Updating the database(s)

The official documentation say that you should “Apply SQL scripts” (plural) then only mentions the Update_rollup_mom_db.sql script. Not entirely sure what gives? I’ve only applied the mentioned script file, and that’s been working so far. The DW-script don’t seem to be doing very much anyway.


Apart from the vague instructions regarding the SQL-scripts, the 1807 upgrade is pretty straight-forward. Alhough, given the recent experiences with 1801, I am far more cautious going into these semi-annual updates going forth.

I am a bit dissapointed with the actual update, though. There’s very little going on between these, supposedly larger, updates compared to what we got with the old Update Rollups.

Not much more to say on that front, perhaps there will be something interesting in SCOM 2019…