Last time (Fixing OMS Workspaces) we looked a way to repair or distribute OMS Workspace settings using Powershell. Wouldn't it be nice if we could leverage SCOM's access to individual machines to be able to keep them attached to the workspaces? If we could pull this off, we could minimize the amount of time we're blind to each server in our environment. Why use SCOM to push OMS settings?
We've seen some interesting behaviors in Azure with the Healthservice Agent which provides the connection to SCOM in our hosted environment and OMS in Azure. The management groups registered with the service (Healthservice - Microsoft Management Agent - MMA for short) seem to disappear every once in a while. We suspect it happens during updates to the agent (extension if you're deploying from the Azure portal).
Sounds Fancy! The problem I was having was that SCOM doesn't have a default way to look at all of the members of a group/subgroup tree in a convenient way. The Get-SCOMGroup cmdlet doesn't have an option to recursively search any subgroups it finds. It requires all kids of clunky Powershell to enumerate all of that if you need it. I needed it.
Straight to the code: https://github.com/cole-mcdonald/SCOM-GhostedObjects
Microsoft's System Center Operations Manager has much more power than the interface allows access to. Of exceeding importance in an enterprise setting is building high availability into our systems. SCOM includes much of this by default in the management structures. The interface no longer reflects these settings, but they're still available to us through Powershell. Here's a little script I use in our environment for bringing new gateways online.
Our Operations Manager installation has been through a few sets of hands since the contracted installer put it in place 4 or so years ago. I inherited it as a fully operational black box a year ago. I was handed the keys and tasked with figuring out how it all went together. I'd come from the Linux world (technically FreeBSD), I'd never even heard of System Center, much less Operations Manager. I knew nothing of the history of the program itself or the suite of apps which had been acquired by Microsoft and bundled together into an enterprise DevOps platform.
Connecting System Center to Microsoft Teams (straight to the code: https://github.com/cole-mcdonald/Blog_Code/blob/master/Send-SCOM2Teams.ps1)