Skip to content
adatum
  •  SCOM Web API
  • About adatum
Azure

OMS and SCOM announcements from Ignite 2017

  • 26/09/201729/09/2017
  • by Martin Ehrnst

Microsoft Ignite in Orlando has started, already on day one we got a lot of announcements and new features. In this post I will try to keep track of the updates on regarding monitoring and management. SCOM, OMS, Azure monitor etc.

Microsoft Operations Management Suite, Log Analytics, Azure Monitor

  • Azure Security Center for hybrid cloud.
  • Azure Monitor, near real-time alerts
  • New container monitoring solution
  • Using Log Analytics query across multiple workspaces
  • The OMS portal as we know it will be deprecated and everything integrated in to the Azure portal.

System Center Operations Manager

From the session “System Center : First look at advancements coming this year” held 26.09 we got the following annoucements regarding SCOM.

  • New release cadence.
    • System Center 1801 prieview early November. Release Q1 2018
  • Service Map integration
  • Windows Server 2016 SDDC monitoring
  • Improved Unix/Linux support
    • “setup improvements” hopefully a better way to deploy “manually”
    • Kerberos support
    • Log file monitoring with FluentD. Essentially this enables us to create monitors etc. based on logfiles as we can with Windows
  • SCOM 2016 HTML5 console
    • Improved diagnostics and drill down – this is huge for those who haven’t invested in third-party software
    • Custom widget support. Display other charts on your dashboard.
  • MP updates and recommendations (introduced in 2016) now supports 3rd party MPs. 56 partners with certified MPs are available.
  • Visual Studio Authoring Extension for VS 2017

Other interesting stuff

  • Planned Maintenance for Azure VM
  • Teams primary communication client for Office 365 (Not Skype)
  • Updates to cognitive services api
  • Azure Cost Management from Clouddyn
  • Azure Stack is shipping

Share this:

  • LinkedIn
  • Twitter
Operations Manager

SCOM 2016 WMI Health Monitor FIX

  • 05/09/201719/12/2019
  • by Martin Ehrnst

As discussed on technet and within the SCOM community there was a bug introduced in SCOM 2016 which triggered the WMI health monitor. A couple of community fixes were introduced, and Morten Lerudjordet also created an addendum management pack with rewritten scripts that solved the issue.

Now Microsoft have released hotfix to their MP that fix this problem. So if you are upgrading or migrating to SCOM 2016 you should add this management pack before going in to production.

Share this:

  • LinkedIn
  • Twitter
Lecture speaking Community

Speaking at Experts Live Berlin

  • 16/08/201703/12/2018
  • by Martin Ehrnst

For the first time i will speak publicy outside Norway. I am travelling to Experts Live in Berlin.

I was lucky to be invited by SquaredUp to their SCOM community (and famous whisky Tasting) session. I’ll have a small contribution on how you can automate and integrate your operations manager environment with your modern application stack.
If you find SCOM interesting, come by and see a live demo on the SCOM Web API, Powershell management pack and other great community contributions.

More about Experts Live and a session list

Share this:

  • LinkedIn
  • Twitter
Operations Manager

SCOM 2016 migration – Transfer alert Ticket ID

  • 12/06/201712/06/2017
  • by Martin Ehrnst

Quick publish:

We are migrating a large SCOM environment to 2016 and the current 2012 environment have an integration with our ticketing system. As we want the migration as smooth as possible, updating the co-existing alerts with the already connected ticket ID seemed like a good idea.

All alerts with an assigned ticket that aren’t closed have a custom resolution state. Using Powershell I grabbed all alerts from SCOM 2012 and updated the same alerts in our 2016 environment.

Import-Module OperationsManager

#Connect to old SCOM environment
$OldEnv = New-SCOMManagementGroupConnection OldScomServer

#Get all alerts with custom resolution state, indicating a ticket is created
$Alerts = get-scomalert | where {$_.ResolutionState -eq 3}
#Connect to the new SCOM Environment.
$NewEnv = New-SCOMManagementGroupConnection NewSCOMServer

#Loop through the alert and set resolution state, ticket and custom field in the new environment
foreach ($Alert in $Alerts)
    {
    Get-ScomAlert | where {$_.Name -eq $Alert.Name -and $_.MonitoringObjectPath -eq $Alert.MonitoringObjectPath -and $_.ResolutionState -eq 0} | Set-SCOMAlert -ResolutionState 3 -CustomField4 "TEXT" -TicketID $Alert.TicketId
    }
#list updated alerts
Get-SCOMAlert -ResolutionState 3 | select Name, TicketID

As you see, we have a string in custom field 4, you can just remove this and change your resolution state to fit your environment.

Share this:

  • LinkedIn
  • Twitter
Automation

Update: SCOM web API

  • 02/06/201715/11/2017
  • by Martin Ehrnst

Big updates:

I have made a lot of changes to the SCOM web API. As you can see from the picture above. Maintenance scheduling is added, which means you can create a new maintenance schedule in SCOM 2016. To the computer endpoints I have added the a possibility to get detailed information. This will list all related object to the server. Logical disks, network cards etc.

These are the API endpoints available at the moment:

Agents

RouteDescription
[GET] API/AgentsGets all agents
[GET] API/Agents/{id}Get a single agent

Alerts

RouteDescription
[GET] API/AlertsGets all open alerts
[GET] API/Alert/{id}Get a single alert
[PUT] API/AlertUpdate the specified alert with resolution state, TicketId
[GET] API/Alert/{ComputerName}Get all alert from specific computer, use IncClosed=true to include open and closed alerts

Computer

RouteDescription
[GET] API/Computer/WindowsGet all windows computers wit basic properties
[GET] API/Computer/Windows/{ComputerName}Get A single windows computers with basic properties
[GET] API/Computer/Windows/{ComputerName}/DetailedGet A single windows computers with hosted child objects
————
[GET] API/Computer/LinuxGet all Linux computers wit basic properties
[GET] API/Computer/Linux/{ComputerName}Get A single Linux computer with basic properties
[GET] API/Computer/Linux/{ComputerName}/DetailedGet A single Linux computers with hosted child objects

Maintenance

RouteDescription
[POST] API/ComputerMaintenancePut the specific computer object and all child in maintenance mode
[POST] API/ObjectMaintenancePut the specific monitoring object and all child in maintenance mode
[POST] API/MaintenanceScheduleCreate a new maintenance schedule. SCOM 2016 ONLY

Object

RouteDescription
[GET] API/MonitoringObject/{id}Get a monitoring object and all child object

 

Examples

Create a new maintenance schedule by sending a post to /API/MaintenanceSchedule with a body including object id, start date and end date in UTC, optionally a comment.

#CREATE A MAINTENANCE SCHEDULE WITH TWO OBJECTS. Time in UTC

$body = @"
{
  "scheduleName": "new maintenance schedule",
  "id": "a43a5b09-5c32-8624-1427-73b8e1f05248",
  "StartTime": "2017-05-30T13:53:33.550Z",
  "EndTime": "2017-05-30T14:53:33.550Z",
  "comment": "TicketID"
}
"@


Invoke-RestMethod -Uri 'http://localhost:64049/API/MaintenanceSchedule' -Method Post -Body $body -UseDefaultCredentials -ContentType 'Application/json'

Get details/related object from a computer:

Invoke-RestMethod -Uri 'https://host/API/Computer/windows/computer.fqdn/Detailed' -UseDefaultCredentials

Which will return something like this. Notice the relatedObjectsCount and relatedObjects

Share this:

  • LinkedIn
  • Twitter

Posts navigation

1 2 3 4 5 … 8

Top Posts & Pages

  • Using Azure pipelines to deploy ARM templates
  • Azure AD authentication in Azure Functions
  • Multi subscription deployment with DevOps and Azure Lighthouse
  • Working with Azure Monitor Rest API
  • Creating Azure AD Application using Powershell
  • Remediate Azure Policy with PowerShell
  • Serverless application with PowerShell: Azure Functions
  • Maintenance Mode based on Event
  • Metric alerts for Azure monitor logs
  • Access to Blob storage using Managed Identity in Logic Apps - by Nadeem Ahamed

Tags

agent announcements api ARM authoring Automation Azure AzureAD AzureFunctions AzureLighthouse AzureMonitor AzureSpringClean Bicep Community CSP database EventGrid ExpertsLive ExpertsLiveEU IaC Infrastructure as code Integrations LogAnalytics management pack monitoring MSIgnite MSIgnite2017 MSOMS MSP nicconf Nordic Virtual Summit OperationsManager OpsMgr Powershell QUickPublish rest SCDPM SCOM SCOM2016 SCVMM Serverless SquaredUP SysCtr system center Webasto

Follow Martin Ehrnst

  • Twitter
  • LinkedIn

RSS Feed RSS - Posts

RSS Feed RSS - Comments

Microsoft Azure MVP

Martin Ehrnst Microsoft Azure MVP

NiCE Active 365 Monitor for Azure

NiCE active 365 monitor for Azure
Adatum.no use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it. Cookie Policy
Theme by Colorlib Powered by WordPress
adatum
Proudly powered by WordPress Theme: Shapely.