We were delighted to welcome Aditya Goda (Microsoft Program Manager) onto our Coffee Break webinar series, to discuss what’s new in SCOM 2019.
We cover the highlights below – you’ll see new features, demo videos, and a live Q & A with Microsoft. We'll also tell you the release date!
Before we start though, let’s consider that SCOM 2019 is a Long-Term Servicing Channel (LTSC) release. This commits Microsoft to provide five years of mainstream support, plus five years of extended support. Awesome!
Microsoft also announced they will no longer develop Semi-Annual Channel releases (i.e. they will not release 19XX). They will focus on LTSC releases, with Update Rollouts available every six months over the five year mainstream support window.
Now let's dive into those features.
There’s good news for admins here. Microsoft will now let you use complex operators in the notifications area. In addition to the previous ‘AND’ operator, you’ll also discover OR, and Exclude operators (handy if you want to exclude test servers from your alerts). Regular expressions make an appearance too.
And even better news, SCOM 2019 includes HTML styling for alert emails. Going forward, you’ll build emails with colour coding, and embed links to the alert, alert source, and monitor – directly within the email. Check out the demo below.
SCOM 2019 introduces a new concept – if a monitor remains unhealthy, alerts can’t be closed. But if you need to manually close alerts, Microsoft baked in an alert closure failure dashboard. It allows you to reset the health of any monitor. View the demo below for more detail.
Those of you who monitor Linux and UNIX workloads likely fear failovers. You know that it will duplicate all active alerts. Luckily, Microsoft recognised this issue and resolved it for both Linux and Network devices.
The latest version of SCOM also introduces recommendations for third-party Management Packs (MP) for Linux/UNIX. You'll start to receive reminders to update MPs and much more.
And SCOM 2019 extends Linux log file monitoring to include any data source, from Docker and Azure, through to Java applications logs.
The Azure Management Pack for SCOM receives an upgrade, with Microsoft keen for you to monitor more Azure solutions from within SCOM. The MP will discover instances across many different Azure services (such as App Insights) and allow you to define performance metrics for each service.
Crucially, admins will enjoy access to dashboards which show what you monitor in Azure. And rest assured, the MP will work with earlier versions of SCOM.
See a demo of the MP below.
SCOM 2019 defaults to logging on Run As account users as a service. It replaces local log on, which cached passwords and created security issues in some environments. SCOM will send you an alert if any configured Run as Account does not have the right to log on as a service.
SCOM 2019 brings a bunch more features and fixes we haven’t covered yet:
Microsoft will release the new version in March 2019, with in-place upgrades possible from the 2016, 1801, or 1807 versions. If you deploy 2012 R2, you’ll need to upgrade to 2016 first.
What about getting SCCM and SCOM to tie together for maintenance mode when patching servers?
That’s interesting feedback, thanks. We will look into it in the future.
Do other System Centre products need to be upgraded at the same time?
Is there a VMM2019 and SCOrch 2019?
Yes - all products in the suite [are covered].
Will features included in the SAC release be included in SCOM 2019 UR releases?
Featues in SAC releases 1801 and 1807 have been included in SCOM 2019.
Will there be an SCCM 2019?
No. SCCM does CB releases every 4 months.
What is difference with SCOM 2019 and the current branch 1801/1807?
SCOM 2019 is an LTSC release i.e. it is supported for 5 years (mainstream support) + 5 years (extended support). SAC releases are supported for 18 months.
Is the duplicate alert improvement generic for resource pools? [I’m] Think[ing] about a resource pool used for network monitoring.
Yes, this improvement applies to network monitoring as well.
How about support for visual studio 2019?
Visual Studio 2019 is still in preview. We plan [to add] support by the time of GA of VS 2019.
Which regex does SCOM use for notification?
Full .Net -same as PowerSHell -Match operator.
It appears with the new web console that MS wants to get rid of the fat client? Or simply sue the fat client for basic overrides creation?
Yes, it would seem the fat console is for Administrators/authors. That said alert closure blocking is in the fat client as well.
Do you have plans on having a single pane of glass with SCOM 2019 and Azure Monitor?
Azure MP provides integration between monitoring Azure resources back into SCOM.
Any support on monitoring mobile devices?
[There is] no such support in SCOM 2019.
I would like to have all alerts from Azure Monitor inside SCOM.
You can do that today with Azure MP.
Will all future Microsoft developed MPs be non-version specific. e.g. the new SQL MP supports all version of SQL from version 2012 to the latest and greatest version.
Thats our strategy. It will take a while to get all MPs on to that strategy.
[Are there] any big improvements in event correlations? If a network ID [goes] down we get only 1 alert.
This is a problem we are looking to solve. [It won’t be] in SCOM 2019 though.
© Squared Up Ltd. 2019