Last night System Center 2019 Update Rollup 2 was released. I blogged about the list of 5 products updated and their respective KB article pages here.
This blog post will be specifically about SCOM though.
What we always do first is go to the KB article and read what is new, what is fixed and where the downloads are located.
- KB Article with all the info
The next thing is checking out what is new in features. Microsoft wrote an article about that as well. We also have a post up since a while detailing some of those new features. We will publish an updated version of a blog for the new auditing feature later (need to take new screenshots).
The main new features are:
- Change tracking for Management Packs
- Scheduled Maintenance Mode Improvements
- Support for Favorite Reports in Web console
- Support for Folders in monitoring view of Web console
- CentOS 8 support
They are all discussed in the article we wrote last month. The first one about Change tracking we were asked to wait a bit with the extended version. So we will be writing about that now the UR2 is released. Watch this blog for that one.
Next I always check out Kevin Holman’s page if he wrote about the UR, and he did write about it last night as well with screenshots and versions and steps. Also he updated his SCOM Management MP. So here are two links:
So we went ahead and update our SCOM demo server from a beta UR2 version to the latest release.
- Because it is available, I first install Kevin’s pack and next close the SCOM Console.
- Next up is the Microsoft updates stuff. We start with the Management Server and run the new style installer for the management server, which includes the SQL scripts and pack updates (not the linux ones). Check if all steps are green in that wizard. If not you can resolve issues and use the .msp file for server, but in that case do not forget to run the SQL scripts and MP import manual steps. The wizard just takes care of all 3 steps if successful.
- Next do not forget to update other roles sitting on the same server (sometimes). For example the SCOM Console. I am running these from al elevated command prompt (or PowerShell prompt in this case) and just run the msp files.
- Go through updating remaining management servers using the server.msp file (not the full simplified wizard), Consoles, Web Console, Reporting, Gateways
- Unpack the UNIX/Linux msi and install the packs you need for the distributions you are supporting monitoring for.
- Now it is time to upgrade the SCOM agents. I usually start with the Windows agents and next do the Linux/Unix agents where applicable.
And there is a lot of checking if everything is still working. Use the views in the SCOM Administration pane and also the SCOM Management mp views to determine versions of what you just updated and if any are still missing. Keep in mind to give the whole process a bit of time.
Good luck and have fun with this latest release!