In our last online session, we hosted Aditya Goda, Program Manager at Microsoft, and MVP Bob “SCOM-Bob” Cornelissen, Managing Consultant at BICTT to present “Migrating to SCOM 1801“. They covered a lot of ground in terms of what’s new in SCOM 1801 and the different migration options currently available. Their presentation was followed by an extensive Q&A session with our attendees.
Below you will find the top questions that were asked to our experts and their replies. In addition to this, you will also find some interesting results we obtained from polling our attendees to get a grasp of the current status of the SCOM space.
From which version is it possible to upgrade to SCOM 1801 and what are the requirements (e.g. SQL)?
The upgrade is possible from SCOM 2012 R2 and SCOM 2016. In case you need to update your database as well, it is necessary to upgrade from SQL 2012 R2 to SQL 2016 with your SCOM 2012 R2 deployment and then upgrade to SCOM 1801.
Can I move to from SAC to LTSC? What are the plus and cons of SAC vs LTSC?
No, it’s not possible to move from LTSC to SAC.
With the SAC, you will have access to new features and enhancements at a faster cadence, with releases approximately twice per year. The support for SAC releases lasts for 18 months after the release.
With the LTSC, you will have delayed access to new features but more stable support: 5 years of mainstream support followed by 5 more years of extended support.
What are the consequences of migration on groups, DAs and (custom) MPs?
Moving groups, DAs and MPs is normally possible provided they are clean and healthy enough.
How does the licensing work? Is it different for SAC and LTSC?
No, it’s not different. In both cases, you need to be on System Center Software Assurance.
Can I upgrade in place or should I opt for the side by side route?
It all depends on how clean the environment is. If it is healthy and clean enough, an in place upgrade should work out fine. As always, keep backups of everything in case something goes wrong.
How can I upgrade all SCOM clients at once during a side by side migration?
Push the agents from the new SCOM server. This will upgrade the agent itself and connect it to both environments.
Can 1801 monitor Containers and Dockers?
No, container monitoring is not supported.
Is there a SCOM WEB API?
Yes, SCOM REST API can be used to visualize SCOM data using the Custom widget in HTML5 dashboards.
Documentation for SCOM REST API’s: https://docs.microsoft.com/en-us/rest/operationsmanager/
How do SCOM 1801 and OMS overlap/complement each other? When should I use one or the other?
SCOM 1801 and OMS have a good integration story. SCOM data (like alerts) can be pushed to OMS and analyzed through Log Analytics and other solutions (alert Management) in OMS.