Tag: OpsMgr


I’ve been meaning to write this blog post for a long time. The reason for that is because since the first preview of OMS (Operational Insights back in the day) I’ve received question like “I’ve removed the Microsoft Monitoring Agent from my server but why I still see the server in OMS?” trough various channels. And btw if you wonder how long I’ve been using OMS today is exactly 2 years and 3 months since it was announced at TechEd North America 2014. I probably should be getting some honorable badge for this achievement Smile . Back to the topic. While there are scenarios in which you can think of OMS like it is SCOM in many ways you should not and there is reason for that. I will try with this blog post to explain why and answer the above question. We can summarize the differences between Operations Management Suite and SCOM in the following statements: Continue reading “#MSOMS Is Not #SCOM”


Version 3.0.1 of THE MVP Script to Download All SCOM Management Packs with PowerShell

So after the release of 3.0 at the beginning of week there were some comments of desired features and bugs reported. I’ve sent those to Damian and as he is working on fast release cadence a new version is now ready to address those comment. Additionally we are including another friend and fellow MVP Cameron Fuller to the authors. We are now on version 3.0.1 with the following changes: Continue reading “Version 3.0.1 of THE MVP Script to Download All SCOM Management Packs with PowerShell”

Fixing Event ID 31553 On SCOM Management Server

On a SCOM management server I’ve noticed event ID 31553 logged a lot constantly and in detail the error looked like this: Continue reading “Fixing Event ID 31553 On SCOM Management Server”

Quick Look at Multi-Tenant RRAS Management Pack

If you are using Network Virtualization from Microsoft you probably also using Multi-Tenant Gateways. In such scenario the gateways become critical part of your infrastructure and would be best if you can monitor them. Continue reading “Quick Look at Multi-Tenant RRAS Management Pack”

Updated MP: SQL Server

The SQL MP which had new version just last month now is updated again. The previous release had some bugs which were addressed and fixed quickly:

  • Fixed CPU Utilization Monitor
  • Fixed SQL Server seed discovery for WoW64 environments
  • Alert severity of Average Wait Time Monitor was changed to Warning, added consecutive sampling to reduce noise, threshold was changed to 250
  • Alert severity of SQL Re-Compilation monitor was changed to Warning, threshold was changed to 25. The monitor was disabled by default.
  • Minor fixes

Great job by the team behind the MP for fixing those bugs quickly. The new version you can find here.

Updated MPs: SharePoint Server 2013 and SharePoint Foundation 2013

Two SharePoint 2013 MPs are updated and as both have common code the fix is same for both:

  • Fix report not working issue, version 15.0.4557.1000

Download SharePoint Server 2013 MP from here and SharePoint Foundation 2013 from here.

First Look at OpsLogix’s VMware Management Pack (beta)–Part II

After taking a first look at OpsLogix’s VMware Management Pack I’ve released I’ve missed something that I usually test with such core MPs like this one. That test is to bring the discovered objects from SCOM to SCSM as Configuration Items. It is not something hard to do and I’ve described the process before here but nevertheless I think it will good to see it visually in this blog post.

First you need to import OpsLogix IMP –Base Library MP and OpsLogix IMP – VMWare MP in Service Manager.


But before actually importing these two you need to import also their dependencies:



In my case I’ve needed to import Operations Manager Internal Library, System Center Visualization Library and System Center Image Library. All management packs can be found in the SCOM installation in the Management Packs folder. Keep in mind that for the System Center Visualization Library the MPB file have to be imported:


After successful import you need to configure your Operations Manager CI connector in SCOM to sync the VMWare MP:


Next we need to put some classes in the SCSM allow list in order to sync the instances for that classes. The classes we will find in SCOM Discovered Inventory View:


Now that we know the display names of the classes we can easily find their internal names with PowerShell.


You need to start Operations Manager cmdlet and execute the following commands:

  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Cluster"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Datacenter"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Datastore"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware ESX Server"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Network"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Resource Pool"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware vCenter"}
  • Get-SCClass | Where-object {$_.DisplayName -match "Vmware Virtual Machine"}

Basically we need the following classes:

  • OpsLogix.IMP.VMWare.Cluster
  • OpsLogix.IMP.VMWare.Datacenter
  • OpsLogix.IMP.VMWare.Datastore
  • OpsLogix.IMP.VMWare.ESXServer
  • OpsLogix.IMP.VMWare.Network
  • OpsLogix.IMP.VMWare.ResourcePool
  • OpsLogix.IMP.VMWare.vCenter
  • OpsLogix.IMP.VMWare.VirtualMachine

Now that we have the internal names of the classes we can easily put them in SCSM allow list again with PowerShell:


I am using the built-in SCSM PowerShell cmdlets and executing these commands:

  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.Cluster
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.Datacenter
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.Datastore
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.ESXServer
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.Network
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.ResourcePool
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.vCenter
  • Add-SCSMAllowListClass -ClassName OpsLogix.IMP.VMWare.VirtualMachine

To verify that the classes are added to the allowed sync list you can use: Get-SCSMAllowList

Next you need to force sync on your Operations Manager CI connector. After the connector syncs successful you can create several views to check if the instances of these classes are synced:








The beta of the MP does not discover a lot of properties for the objects but I am hoping this will be changed in the final version or some of the next ones as proper and rich CMDB is important.