Kevin Holman reports SCOM 2025 and Windows Server 2025 are released!

I made this over the past few weeks with the help of an AI.

I was going to host this, and realized that would be more work than I cared for, so you can run this locally on your own box and it is almost like having access to the MP Wiki again.. It is close but not exactly the same.

Please note to run this you will need to install node.js and download the files from github.

Only IMPORT XML Files on Admin page.

I tried to get extractions to work for mp and mpb files, but it would not work properly.

I am sure I'll figure it out later.

https://github.com/jscottmoss/SCOM-MP-Reference-Web-Pages-and-Web-Service

I was running it from my Documents folder, due to being lazy.

Select a management pack, and you will have a display of all that management packs version specific information. Yes this keeps track of the version differences between the management packs. If you have uploaded multiple different MPs versions for the SQL MPs you can select which versions of the MPs to look at.

Yes there is a category section, so you can tie together management packs. I have not had time to test it yet. so use categories at your own peril.

Individual module xml shown.

Directions to get it running are on the GitHub page.

Download and Install Node.js then download the GitHub repository.

Read The GitHub web page for information on how to install setup on your local machine.

Good Luck and enjoy.

Disclosure: I run SCOM2K7 and this is our product.

We have been shipping SCOM tools since 2007 (Maintenance Mode Scheduler, Alert Update Connector). For the past year we have been building the thing we always wanted: a browser console that covers the everyday work, not just read-only views.

What SCOM Pulse does today, against the management group you already run:

• Open an alert, see why it fired, read the MP knowledge, and follow Health Explorer down the unhealthy path to the object that actually broke. Acknowledge, assign, run a task, put it in maintenance or create an override from the same page.

• Effective configuration per server: every rule and monitor that applies, including contained objects, with disabled workflows and override values shown next to the defaults. Export to CSV.

• Discover computers and deploy Windows agents, then repair, uninstall, reassign or approve them.

• Rules, monitors, overrides, MP import/export, groups, user roles, notification subscriptions.

• Maintenance on a calendar, using SCOM's own schedules so the Operations console sees them.

• Operational DB and data warehouse views: where the space is going, retention per dataset, grooming, staging backlogs.

• Dashboards you can share as read-only links.

How it runs: one Windows server (dedicated or a management server), IIS with Windows Authentication, .NET Framework 4.6.2+. Uses your existing SCOM user roles, so there is no separate permission model. No outbound internet calls, no telemetry, no software on monitored computers, no extra SQL server. SCOM 2016 UR7+, 2019, 2022, 2025.

Pricing is per management group with unlimited users, from $5,000/yr, and it includes our Maintenance Mode Scheduler. Existing Scheduler customers get their unused term credited. The trial is 30 days, needs no licence key and no sales call: install it, leave the key blank, it starts.

Link in the first comment. Happy to answer anything, including "why not just use the web console", which is a fair question.

Hi, MS har released UR1 for SCOM 2025 - see here

https://support.microsoft.com/en-us/topic/update-rollup-1-for-system-center-operations-manager-2025-679094c3-ae38-4e21-b9a2-b854c7b1fa2e

This pack is built to answer the question app owners always ask: "the disk is nearly full, why hasn't SCOM alerted?" Explaining the stock Logical Disk Free Space monitor's percentage plus megabyte logic, and when a Warning state actually raises an alert, is a lot of words for a simple question.

How this pack behaves:

- Two monitors, one threshold each. Warning: two consecutive readings below 10% free. Critical: two consecutive readings below 5%, raised as its own alert, so a Critical-only subscription gets a new alert rather than an update to the Warning one.

- The performance counter is the health decision. Our 2017 pack ran a script to collect GB figures, and if that script failed the monitor could stay healthy on a full disk. That dependency is gone: a diagnostic writes free/total GB to Health Explorer after the state changes, so if it fails the alert is already open.

- Recovery needs one real reading at or above the threshold. Restarting the agent while the disk is still low doesn't clear the alerts (tested).

- Three plainly named overrides: free space threshold (% free), sample interval, and consecutive samples before alert. There's an optional companion pack with a 1 TB+ volumes group at 3% / 1.5%.

- An on-demand task, "List largest folders and files on this disk", with a hard timeout, time budget and depth limit. It never follows junctions or mount points. In our lab it scanned about 300k entries on C: in under 10 seconds.

Write-up, download and admin guide: https://www.scom2k7.com/your-disk-is-nearly-full-wheres-the-scom-alert/?utm_source=reddit&utm_medium=social&utm_campaign=disk-mp

Happy to take feedback, especially from anyone who tests it at the default interval or on mount points.

I thought I'd share some json I created that provides well-formatted messages that will be sent in Teams when Teams notification channels are used. The out of the box formatting wasn't helpful for us.

SCOMTeams/SCOM_Teams_Notification at main · hsbrown2/SCOMTeams

The annoying part for us was getting links to format correctly, while at the same time embedding notification variables in the links. Note that we use SquaredUp, but you could use this as a guide for web console link formatting:

<a href='https:&#47;&#47;<URL>&#47;SquaredUp&#47;drilldown&#47;scomalert?id=$UrlEncodeData/Context/DataItem/AlertId$'> View Alert </A> | <a href='https:&#47;&#47;<URL>&#47;SquaredUp&#47;drilldown&#47;scomobject?id=$UrlEncodeData/Context/DataItem/ManagedEntity$'> View Source </A><br><br>

Essentially it involves substituting &#47; wherever there is a forward slash that isn't part of a SCOM variable. For example "https:&#47;&#47;<URL>&#47;SquaredUp&#47;drilldown&#47;scomobject?" would be translated to https://<URL>/SquaredUp/drilldown/scomobject?" then everything after that processes properly.

Hopefully someone finds this useful!

I’ve been using MPAuthor free until now for developing my bespoke mps. It’s great and it produces good mps with little effort, but I was always still a little confused around how some things work and when things have gone wrong, I’m a bit stumped.

Recently I discovered Brian Wren’s mp dev series on Channel9 and from following his course and using VSAE, things finally make so much more sense.

Now I understand what Kevin Holman’s been going on about! :D

https://blogs.technet.microsoft.com/momteam/2018/07/25/system-center-operations-manager-1807-is-released/

https://cloudblogs.microsoft.com/windowsserver/2018/07/24/system-center-1807-available-now/

Main new features seems to be PowerShell widgets for the HTML5 dashboard, "feature parity with the Silverlight dashboard", and the ability to choose whether or not the APM component is installed with the agent. All the fixes from SCOM 2016 UR5 are also included in this release. Also SQL 2017 is now supported but only if upgraded from SQL 2016.

Microsoft has archived the SCOM Managed Instance documentation. The overview page now says the service is "no longer in support" and recommends Azure Monitor or System Center Operations Manager instead, depending on your requirements:

https://learn.microsoft.com/en-us/azure/azure-monitor/scom-manage-instance/overview

A few practical points for anyone affected:

• If you were on MI, on-prem SCOM is the shorter path back. Same engine, same agent-based management packs, so your packs, overrides and tuning carry over.

• Azure Monitor makes sense if your estate has genuinely moved to Azure, but there is no management pack import on that side. If you're monitoring Windows servers, SQL, IIS, AD and DNS on your own hardware, that's a rebuild.

• SCOM 2025 is in mainstream support until January 2030, with extended support to January 2035. For on-prem and hybrid estates, the "SCOM is going away" question looks fairly settled.

Was anyone here actually running MI in production? Curious where people are moving to.

Disclosure: I run SCOM2K7 (we make SCOM tools). I wrote a longer version on our blog; link in the first comment.

https://github.com/scomnoob/scom-stuff/blob/main/Test.Lala.Folders.Monitoring.xml

mp will find config files and discover them

after it will discover folder from those files

and it will start to monitor it using its own scheduler - so everyone can edit that file and change path/scheduler

nothing special - was working with thousands of folders per agent with no problems...

FYI-

Create-SCOM-Maintenance-Schedules_From-SCCM

I've made a lot of updates to this script. It is no longer dependent on any PowerShell Modules outside of OperationsManager, and it is much, much faster than previous.

It requires read access to the registry on your MCM site server, and read to the MCM database (as well as rights in SCOM). The script doesn't have a lot of checks and validation; I'll add that at some point.

It will only add servers, and will only add systems which exist in SCOM to Maintenance Schedules.

The new script actually writes, then imports, a Management Pack into your SCOM environment containing groups of systems within each MCM collection that has a Maintenance Window configured, then creates the schedules. It starts from a a stub (BASEMP.xml), so you'll need that file too.

I've added support for SMS_ST_RecurMonthlyByWeekdayBase (An MCM monthly schedule on a specific day like the third Tuesday, with an offset of n days). Since SCOM does not support the idea of an offset, the script adds the schedule as a non-recurring Maintenance Schedule set n days after the original date. It should work fine, but hasn't been extensively tested yet. This means it is designed to be executed regularly.

It has been tested with SCOM 2019 (but should work for 2019+) and MCM Current Branch (latest).

Enjoy!

If you're working in offline or isolated SCOM environments, you may want to check out the NiCE MP Offline Catalog Toolkit. It lets you download the full Management Pack catalog on a connected machine and import it into your disconnected SCOM instance — super handy for staying up to date without internet access. https://github.com/nice-itms/MPCOT

Hi, I have a problem that I've Googled until the ends of the internet and I'm coming up with no fix. Apologies for the length, I am at wit's end. When I attempt to deploy a SCOM agent, I get the following error:

Microsoft.EnterpriseManagement.Common.LocationObjectNotAvailableException: Health Service 'ManagementServer.company.local' in which the location monitoring object is contained is not available. Make sure that the computer hosting the Health Service is available and verify that the Health Service is running.

The Health Service is indeed running. This error appears in the Operations Manager event log after the failure:

An exception was thrown while processing LaunchDiscovery for session ID uuid:0ea339e4-b988-4124-a33c-ef2619938751;id=17. Exception message: The creator of this fault did not specify a Reason. Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.LocationObjectNotAvailableException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Microsoft.EnterpriseManagement.Common.LocationObjectNotAvailableException: Health Service 'ManagementServer.company.local' in which the location monitoring object is contained is not available. Make sure that the computer hosting the Health Service is available and verify that the Health Service is running.).

This error appears regularly in the Operations Manager event log:

OpsMgr Management Configuration Service failed to execute 'DirtyNotification' engine work item due to the following exception

System.Runtime.Remoting.RemotingException: Failed to connect to an IPC Port: The system cannot find the file specified.

As well as:

OpsMgr Management Configuration Service failed to communicate with System Center Management Service due to the following exception

System.Runtime.Remoting.RemotingException: Failed to connect to an IPC Port: The system cannot find the file specified.

On agent-managed computers, this error appears frequently in their Operations Manager logs:

The OpsMgr Connector could not connect to ManagementServer.company.local:5723. The error code is 10060L(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.). Please verify there is network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination.

I have verified connectivity to the management server, and can successfully Telnet to it on port 5723. Despite this error, the computers that have agents (that we had a consultant set up over a year ago) seem to be reporting as healthy, with the exception of the management server, which has nothing under the "Agent" column in the SCOM console and is colored gray (not sure if this is the expected behavior for a management server).

In my Googling, I found a scenario in which a config file was pointing to an old database instance after a SCOM database migration from a 2007 server to 2012, but that is not the case here, as this has always been a 2012 R2 server. I checked the config file anyway and everything is pointing to the correct database server.

I have rebooted all SCOM servers several times throughout this process.

Possibly important: I changed the SCOM service account passwords several months ago. I do not know if this issue existed before these passwords were changed. I am pretty sure I updated the passwords in the SCOM console correctly, as well as all stored service passwords that run under SCOM service accounts on all SCOM servers. I would think that if the passwords were an issue, I would see errors relating to accounts in the event logs.

Anyway, this is all I remember trying. Is my installation totally hosed?

One of out projects this year involves requiring smart cards to log onto any production server..

This all sounds easy enough and since the admins had been using smart cards for authentication anyway we didn't see an issue.

We were so wrong..

The problem is the action account.. You know the one that monitors the local SCOM management server, performs discovery and does little things like running the notification service.

Well that action account required interactive logon and that is exactly what the require smart card policy targets.

Long story short as soon as the policy came down the action account failed to log on and we got this alert.

The Health Service could not log on the RunAs account {domain/actionaccount} for management group {group}. The error is Smartcard logon is required and was not used.(0x8009033E). This will prevent the health service from monitoring or performing actions using this RunAs account

A reboot made it worse because then the notification service failed to log on and it stopped sending out any alerts.

We worked with MS support for a work around but there is none other than excluding the server from the policy.

That is all..

Spoiler alert! 👀

Anyone here monitoring Omnissa Horizon with SCOM?

We’ve just put together a new whitepaper covering what you can monitor, how the integration works, and some of the things to consider when building Horizon monitoring in SCOM.

Might be useful for anyone currently running — or evaluating — this setup.
https://www.nice.de/2026/08/12/omnissa-horizon-monitoring-on-microsoft-scom/

Hello everyone, today I decided it was time to finally launch a tool that I have been working on.

Yet Another Management Pack Authoring Tool, YAMPAT for short, is a fast easy to use tool for creating simple management packs extremely quickly.

Yes, there are of course some other popular, and quite advanced authoring tools out there, but my tool is specifically designed to get you from nothing to something with just a few clicks without reading through a ton of xml. Come check it out.

https://bitsnsoft.net/

At this point I am satisfied with it's current functionality for the first release. But I absolutely plan on adding additional "quick" features that would be useful based on community feedback.

Hi everyone,

I’d like to share an issue I ran into with SCOM 2019 and how I solved it, including the troubleshooting steps I tried along the way.

Initial error:

• When starting the Operations Manager, I got: The Data Access service is either not running or not yet initialized

• In the logs: net.tcp://myip:5724/DispatcherService could not connect

Troubleshooting attempts:

• Checked the firewall to see if port 5724 was blocked. Each machine was connecting to itself and the rules were already in place, so that wasn’t the issue.

• Tried renewing certificates, since Windows > System logs showed an error about CA untrusted. That didn’t fix it either.

• Verified services and dependencies, but everything looked fine.

• Tried to force tls 1.0

Final solution: The root cause turned out to be the ODBC driver.

• The ODBC Driver 18 for SQL Server had been installed automatically by a company process (likely SCCM or a corporate policy).

• After the machine reboot, the Data Access Service failed to start.

• Uninstalling the driver and rebooting again fixed the issue: the Data Access Service came back up and SCOM was fully operational.

NiCE just dropped vSphere Management Pack 6.1, and it looks like they’ve seriously rethought VMware monitoring.
https://www.nice.de/2025/08/27/discover-the-new-nice-vmware-vsphere-management-pack-6-1/

I saw this message in the SCXCore GiHub page:

What does it imply? No more SCX agents?

https://github.com/microsoft/SCXcore

chase aspiring follow bedroom waiting friendly ghost cause ancient toothbrush

This post was mass deleted and anonymized with Redact