Tag: Microsoft Monitoring Agent

Manage Custom Fields in Operations Management Suite

Not so while ago I’ve covered a new feature in OMS (MSOMS) called custom fields. When I’ve covered this feature I was missing a way to actually remove an already created custom field. Mistakes happen, you can create field and two months later you may not need that field any more and many other scenarios. It turns out that from today you can remove a custom field that you’ve created. Continue reading “Manage Custom Fields in Operations Management Suite” →

Azure Automation – Hybrid Worker Setup

It is May 4th which marks the start of Microsoft Ignite 2015 and of course new Azure features start to appear. So first Azure Automation is now available in the preview portal: Continue reading “Azure Automation – Hybrid Worker Setup” →

Microsoft Azure Operational Insights Preview Series – Connecting Directly with Microsoft Monitoring Agent (Part 8)

So far we’ve covered this:

At TechEd it was announced that Operational Insights now work with Agent directly without needing SCOM installation. Of course the agent used is Microsoft Monitoring Agent. The agent has some limitations that you can read more here. Continue reading “Microsoft Azure Operational Insights Preview Series – Connecting Directly with Microsoft Monitoring Agent (Part 8)” →

System Center 2012 R2 Operations Manager UR2 Does Not Updated Agents Trough the Console

I’ve noticed recently that after I’ve updated my SCOM 2012 R2 Management Servers to UR2 my SCOM (MMA) agents are not updated. Even though my agents were listed in Pending Management for update and I’ve executed update on all of them trough the console none of them received UR2. Continue reading “System Center 2012 R2 Operations Manager UR2 Does Not Updated Agents Trough the Console” →

Installed MMA 2012 R2 agent on virtual Windows Server 2012 R2 domain controllers gives a lot of health service heartbeat failure alerts

I’ve been dealing with this issues since the release of R2 and now there is a hotfix for that. Seems that was a bug on Windows Server 2012 R2 side. You can read the full details Kevin Holman’s blog (the one and only).