We have a lot of questions about the latest release of SCOM which is now at 1807.
Previously Savision has offered webinars with the Microsoft team. See the last one around SCOM1801 and migrations here.
Today we share an excerpt of a great blog written by our very good friend Bob Cornelissen MVP with BICTT. It has all you need to know about SCOM1807 features and potential migration path. The full article can also be read with the link at the bottom.
A few months ago SCOM 1807 was released at the end of July 2018. It was a release we had been waiting for due to some fixes and due to some features.
Let’s discuss a few things about this release according to this agenda:
• New Features in SCOM 1807
• Issues Fixed in SCOM 1807
• Where to get SCOM 1807
• The migration from earlier versions of SCOM to 1807
I fear it is going to be a bit of text to bring all of this together, but I have been asked questions about these subjects several times and by now I have done a few upgrades and I can say I am happy with the progress.
Here we go…
New Features in SCOM 1807
SCOM Agent and APM
Support for SQL 2017
SCOM Web Console
Where to get SCOM 1807
The SCOM 1807 version is not a clean install CD (ISO). This means that SCOM 1807 is basically a set of update files to install on top of SCOM 1807. You could say a rollup on top of SCOM 1807. We will talk about that below as well. The downloads for the several roles can be found here:
And for the Unix/Linux packs (and agents): https://www.microsoft.com/en-us/download/details.aspx?id=29696 and select the correct version you need!
Also you will see the updates in WSUS, meaning you can use WSUS and ConfigMgr (SCCM) as well to get things updated. Keep in mind the SQL Scripts and management pack updates and Unix/Linux and Nano items still need to be applied manually through the manual process! If you use WSUS and such to move from 1801 to 1807, please do not forget to do the SQL script and pack update manually as soon as possible after doing the management server updates on those servers.
The migration from earlier versions of SCOM to 1807
I regularly get asked about what is possible in migrating from one version of SCOM to another. Talking about how to get from 2012 or 2012 R2 or 2016 or 1801 as source to the destination 2016 or 1801 or 1807 is usually asked. Since we are talking about 1807 as the destination in this blog post the migration scenario is ALWAYS 1801 to 1807. So if you are not running 1801 right now and want to go to 1807 you first need to get to SCOM 1801. From 2012 to 2012 R2 to either 2016 or 1801 or from 2016 to 1801 is possible given the correct rollups are installed for the 2012/2012R2 type of configurations. Anyway, if you want to make use of what SCOM 1807 has to offer in the Semi Annual Channel, you first need to get to SCOM 1801.
Once you are at SCOM 1801 and you download the files mentioned above to upgrade to SCOM 1807, the supported installation order is:
1) Upgrade the SCOM infrastructure components
a. Management Servers
c. Web Console
e. SCOM Consoles
f. SCOM Reporting
2) Apply the SQL Script ( %SystemDrive%\Program Files\Microsoft System Center\Operations Manager\Server\SQL Script for Update Rollups\ Update_rollup_mom_db.sql )
3) Manually import the management packs you need ( %SystemDrive%\Program Files\Microsoft System Center\Operations Manager\Server\Management Packs for Update Rollups )
4) Apply the SCOM agent updates
5) Apply Nano agent updates
6) Update Unix/Linux MP’s and agents (https://www.microsoft.com/en-us/download/details.aspx?id=29696 )
Check out https://www.microsoft.com/en-us/download/details.aspx?id=29696 for the download links and install order as well.
I must make this additional remark, because I get this question a lot for both these and Update Rollups on SCOM 2012/2016 and so on. Do we need to finish the upgrades of all gateways and SCOM consoles before we can continue to steps 2/3 and further mentioned above? No this is not a problem. Usually after upgrading the SCOM management servers I apply the SQL scripts and management packs. Do not let one SCOM console sitting on some terminal server stop your deploy of the other components for instance. Also a few down-level SCOM agents should not stop you either.
The good news is that I have not seen any errors yet in the upgrade from 1801 to 1807. Thank you to the MSFT product team!
What could happen are errors when you do not have enough rights on the SQL server and SCOM server to run the updates. Also see the following tip which is connected to rights as well.
What also helps is if you start up an administrative cmd prompt of PowerShell (Run as admin) and from there go to the folder where you downloaded and extracted the msp update files and run them from that prompt.
Same goes for the msp files belonging to update rollups in 2016 for instance.
SCOM continues to innovate and add features. The semi annual channel versions bring us new features every 6 months together with the fixes we get in the update rollups to the LTSB versions as well. We are only a few months away from looking at what SCOM 1901 and SCOM 2019 are bringing to the table. I know hard work is being done for those versions coming up.
Also the upgrade from older versions of SCOM to 1801 and 1807 have been going rather smooth so far, so I am happy with that process.
The upgrade from 1801 to 1807 is very easy, so go for it!
Keep on monitoring everything!
Read the rest of the blog here