You can’t access the UNIX/Linux computers view in the Administration pane in Microsoft System Center 2012 R2 Operations Manager?

You can’t access the UNIX/Linux computers view in the Administration pane in Microsoft System Center 2012 R2 Operations Manager?

If you can’t access the UNIX/Linux computers view in the Administration pane in Microsoft System Center 2012 R2 Operations Manager, then you probably receive the following error message:


Date: 12/30/2017 7:48:49 PM Application: Operations Manager Application Version: 7.1.10226.1360 Severity: Error Message: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.SystemCenter.CrossPlatform.UI.OM.Integration.UnixComputerOperatingSystemHelper.JoinCollections(IEnumerable`1 managementServers, IEnumerable`1 resourcePools, IEnumerable`1 unixcomputers, IEnumerable`1 operatingSystems) at Microsoft.SystemCenter.CrossPlatform.UI.OM.Integration.UnixComputerOperatingSystemHelper.GetUnixComputerOperatingSystemInstances(String criteria) at Microsoft.SystemCenter.CrossPlatform.UI.OM.Integration.Administration.UnixAgentQuery.DoQuery(String criteria) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.DoQuery(String criteria, Nullable`1 lastModified) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.FullUpdateQuery(CacheSession session, IndexTable& indexTable, Boolean forceUpdate, DateTime queryTime) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.InternalSyncQuery(CacheSession session, IndexTable indexTable, UpdateReason reason, UpdateType updateType) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.InternalQuery(CacheSession session, UpdateReason reason) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.TryDoQuery(UpdateReason reason, CacheSession session) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)



The issue occurs if the UNIX/Linux monitoring resource pool is deleted

How to solve it!

To resolve the issue, follow these steps:

  1. Create a resource pool for UNIX/Linux monitoring. Give the new pool a different name than the name of the deleted resource pool.
  2. Add the management servers that perform UNIX/Linux monitoring to the new resource pool.
  3. Configure the UNIX/Linux Run As accounts to be distributed by the new resource pool. To do this, follow these steps:
    • In the Operations console, go to Administration Run As Configuration > UNIX/Linux Accounts.
    • For each account, follow these steps:
      – Right-click the account, and then select Properties.
      –  On the Distribution Security page of the UNIX/Linux Run As Accounts Wizard, select More Secure.
      –  In Selected computers and resource pools, select Add.
      –  Select Search by resource pool name, and then select Search.
      –  Select the new resource pool that is created in step 1, select Add, and then select OK.
  4. Run the following PowerShell cmdlet to retrieve the managed UNIX and Linux computers:
  5. Verify that the agents that are associated with the deleted resource pool still exist and that the relationship remains.
  6. Run the following command to change the managing resource pool to the one that is created in step 1:

    $SCXPool = Get-SCOMResourcePool -DisplayName "<New Resource Pool Name>"
    Get-SCXAgent | Set-SCXResourcePool -ResourcePool $SCXPool

Original article.
All you need to know about the OpsLogix VMware Management Pack

All you need to know about the OpsLogix VMware Management Pack

For most companies virtualization has become the common standard in all facets of IT. Desktop virtualization, emulators, and hypervisors, all contribute to autonomic computing which in turn ultimately aims to develop computer systems capable of self-management.




Base licenses per socket starting from €159
Making sense in price and performance!






OpsLogix VMware Management Pack

The OpsLogix VMware Management Pack provides essential basic monitoring for  VMware environment, presenting data in the System Center Operations Manager console. The OpsLogix Management Pack for VMware takes all the States and Alerts vCenter generates and presents them in System Center Operations Manager 2012 or higher.

Following the common engineering criteria set down by Microsoft’s Dynamic Systems Initiative (DSI) which unifies hardware, software, and services. The OpsLogix VMware Management Pack consolidates VMware data in SCOM for a competitive price!

Two minute VMware Management Pack demonstration by Vincent de Vries

What else does the OpsLogix VMware Management Pack do?


  • The OpsLogix VMware Management Pack fully supports the CI perspective in Service Manager, meaning that the data can be used in an automated workflow such as auto-populating a CMDB or auto-ticketing prompt.
  • We’ve also made sure that our VMware Management Pack seamlessly integrates into OMS. Meaning for companies already using OMS, it’s an easy fit, maximizing both the centralizing of infrastructural data as well as being able to use the tools OMS log analytics provides.

VMware Management Pack demonstration by MVP Tao Yang

Virtualization and why it’s important


Virtualization has been around since the end of the 1990s and has rapidly developed into a standard feature in any enterprise infrastructure. Its immediate benefits are:

  • Reduced administration burden in that, a centralized console allows quicker server access for purposes of provisioning and/or re-provisioning, quickly allocating additional resources such as RAM, power or space
  • Super-fast deployment simply because every server is a file or collection of files on disk. This means that adding additional servers to an infrastructure is literally a matter of cloning or in layman’s terms copy-pasting.
  • Greatly reduced infrastructure cost in hardware. Things like cooling, electricity, network ports, mice and keyboards not to mention physical space. Industry studies have estimated that virtualization increases hardware utilization and operating costs by at least 50% to 70%.




Extending Microsoft Private Cloud OpsLogix VMware Management Pack

VMware Management Pack & OMS Log Analytics

Our VMware Management Pack has been fully integrated into Microsoft’s Operations Management Suite from the get-go.

We also make it possible to collect over 60 performance metrics to analyze the VMware health state. For example, Host / VM memory and CPU usage and datastore space etc. and of course all audit / task / alarm / snmp etc. events. Meaning that you can use it to meet all the requirements of your security auditing (NEN, SOX, ISO & etc.) And what’s really neat about our VMware monitoring solution, is that it doesn’t require a vCenter installation. You can also directly connect to a ESX(i) host without almost losing any monitoring features.


If you are already using our VMware Management Pack, or you are in trial fase, we offer the VMware OMS Log Analytics solution completely for free. Would you like to try it? Send an email to

SCOM xplat Authoring: How to Monitor Oracle Solaris NFS Mount Points

SCOM xplat Authoring: How to Monitor Oracle Solaris NFS Mount Points

Before you start reading the blog below, I just wanted to let you know that I have limited knowledge on the Solaris side. To be honest when I hear Solaris, my memory takes me back 15 years….

Back in the day, (I’m sounding old now) I started working as a second line help-desk employee. I was sharing a desk, which was like 5-6 meters long, with a colleague of mine (it was just a really big room!).

One of the big benefits was that “old” abandoned machines could be bought for a couple of bucks. Most of the time these machines were defect or written off and this is where every IT guy or girl started their addiction of collecting tons of hardware for home usage.

Anyone working in the IT world for a number of years, had (or still has) a room filled with old abandoned hardware which no one wants any more. It is more or less like a computer sanctuary! To you, it’s a gold mine, but to a non IT person it looks like junk.

(To be honest if my wife never forced me to get rid of it all, I would probably still have my hardware sanctuary!)

When we first started working my colleague and I were pretty much on the same side, but soon he started looking at the other side. He started collecting Sun SPARCstations and looking at Solaris.

First with 1:

sparcstation sun pizzabox

but as his addiction grew the entire desk was filled with SPARCstations and most of the time looking like this:


He would endlessly “play” with the hardware, putting on jumpers and changing settings in the OS to try and get thing to work.

He never stopped talking about how much better all this was than my Microsoft crap…

And when he did finally get it to work, I couldn’t resist starting the following conversation:

“So, it is working now?”

“Yes, finally! I needed to mount this and start that and the jumpers were…”  he continued to speak like this for 5 minutes.

And I would always answer “Cool! So you’ve worked on it for a week now just to install the OS so it can recognize the cd player?” The look on his face was priceless.

So when I think of Solaris, I am back at this long desk with my colleague, covered in sun hardware, where we were always hoping we could score some more abandoned hardware! 

This introduction was just to give you an idea of my Solaris knowledge, and even with this knowledge I can write a Management Pack to monitor NFS mount points!

All I need is one shell command to query the file system and some spare time.

Before we start

If you have Oracle running on Solaris in your environment and you want to monitor these components using System Center Operations Manager 2012 R2, there are several steps that need to be taken.

  1. Import the required Management Packs (MP) to monitor Solaris –
  2. Install the open source SCOM agent on the Solaris server –
  3. Install the OpsLogix Oracle MP –

Once you have completed these steps you will be successfully monitoring Oracle running on Solaris.


Now you can see in the diagram above, that Oracle is fully covered by the OpsLogix MP.

But from the Operating Systems Perspective there is still a crucial part missing in the Microsoft Solaris MP: NFS mount points!

These are not discovered by the pack, nor monitored, so using NFS mount points leaves you blind when using the Solaris OS MP provided by Microsoft.

Here, you have a nice overview on logical disks but no mount points.


This can be a bad situation but remember, you are using SCOM and as I have been telling for years:

When you can communicate with the component, you can monitor it with SCOM. No exceptions!

The approach for Unix / Linux is no different:

  • Create a class
  • Create a discovery
  • Create a monitor to check health
  • Create a rule to collect performance
  • (optional) Create a nice view
  • (optional) Create a dashboard

We need to write a Management Pack which extends the default Microsoft Solaris Management Pack and contains these components.

Here, I will describe the entire process for creating the Management Pack.

You can re-use these procedures to monitor or discover any component running Linux / Unix or you can just grab this copy to include NFS mount points for your Solaris monitoring.

Prepare your environment

After installing Visual Studio and the Visual Studio Authoring Extensions, you will need to have references to the cross platform Management Packs.

You can find these Management Packs on the installation media of System Center Operations Manager 2012 (R2 ) in the folder “Management Packs”:


We will need to reference several of these packs in our custom Management Pack.

Create a new Management Pack project and add the required references.

While you could write a module yourself, I strongly recommend looking at the module Management Pack created by Kris Bash –

Download this library – and add it to your project.

How to use the library –

For additional information on monitors and rules –

Your project references should look similar to this:


Then we can create a new class and discovery.

Class and discovery

For the NFS mount point, we need to define a new class. This so we can target specific rules and monitors against this class.

The class is named “Solaris.NFS.Mountpoint.Class” and its base class is Microsoft.Solaris.LogicalDisk which is located in the Microsoft.Solaris.Library pack.

Also, add an extra property called NFSFileSystem.

After creating the class, you need to create a discovery to locate instances of this class. Since I’m not a Solaris guy, I asked a friend of mine for a VM running Solaris, to find out which shell command to use in a SCOM environment.

The shell command is “df -k”. This will show you all NFS mount points (the –k switch shows you the Kbytes):


Now I can read the information from the solaris VM using putty!

The full command will be df -k | awk ‘{print $1 “,” $2 “,” $6}’

The awk command formats the results and ….. this is where the PowerShell came from.

You pipe the results to the formatting where we only want the first, second and sixth column and we are finished.

Next you can create a new discovery rule.

You can use the add new item and choose the discovery rule, which I find rather “annoying” as you have no idea what you are doing in the back, so I am going to add an empty Management Pack fragment and write the XML myself:

In the first part of the XML, we are targeting the discovery against Microsoft.Solaris.Computer so the discovery will run on all Solaris computers.


Next, add the class you want to discover:


Then, select the data source you are going to use and define the components used by the data source:


  • Interval will be the interval for running the discovery. (Don’t set it to low!)
  • Target system, the name of the Solaris computer.
  • Shellcommand, this is the shell command we want to run on the Solaris computer.
  • Timeout, is the timeout of the shell command.
  • Username, password will be the runasaccount used to run the rule. In this case default Unix action account.
  • PsScriptname, this is the PowerShell script we run for creating a property bag and more filtering.
  • PSScriptBody the actual PowerShell script we are going to use:


The script takes parameters from the datasource, which runs the shell script on the Solaris system and retrieves values:

  • Stdout = output from the Shell command.
  • StdErr = error messages, if there are any.
  • Returncode =  0 for success and the rest are considered failed.

After this it divides the output and creates a property bag for each line in the output.

Note: Since this is Unix, we run the workflow on the management server to query WSMan, therefore you can use PowerShell to output the results to the eventlog on the management server. This is helpful for troubleshooting! 

Next, the datasource will filter the results.


The last step is to create a new class instance based on the property bags created in the PowerShell script.


Now you have a class and discovery which will discover the NFS mount points.

Create a Monitor to monitor used space

For the monitor we are going to use the following Monitor Type: Unix.Authoring.ShellCommand.PropertyBag.GreaterThanThreshold.ThreeState.MonitorType

This will let you create the shell command df -k | awk ‘{print $6″:” $5}’

This will collect all NFS mount points and their usage in %:


After running the shell command we can use PowerShell to retrieve the proper values, put them in property bags and filter the correct instance.


When importing the Management Pack a new class will be discovered. It will be monitored for the used space and generate an alert if the used space is above 80 for warning or 90 for error! (this is the default)


Create a performance collection rule

Now you can create a performance collection rule for the used space. By doing this you can create performance views and reports on NFS mount point usage.

You can do this using the following module: “Unix.Authoring.TimedShellCommand.PropertyBag.DataSource”.

This module uses a shell command which passes this output to PowerShell where we can create multiple property bags. Multiple counters are then created in the Operational Database and Data Warehouse.

The shell command used:


You can select the name and the percentage used property.

In the PowerShell script I remove the percentage sign (%) and created a performance counter from the instance and value.


Then the performance data is created:



You can monitor NFS mount points easily with SCOM 2012. All you really need is the Management Pack with all the modules created by Kris Bash and one shell command.

Even with my Solaris Experience, I was able to do this with no trouble.

As long as you have some authoring experience, with the steps provided you should be able to extend this to other components running on Solaris or any Unix or Linux system supported by SCOM.

You can find the VS project in the technet gallery download (link) together with a full version of the Management Pack, including views and dashboards as shown below.

Cheers and happy authoring,

Oskar Landman


SCOM OpsLogix product connector: how to remove & add it

SCOM OpsLogix product connector: how to remove & add it

An easy how to guide for adding and removing the OpsLogix SCOM product connector.

It so happened that I was helping a customer troubleshoot an issue with connectors in an environment that had been upgraded from SCOM 2007 R2 to SCOM 2012 R2. To rule out some of the possibilities we decided to first remove the OpsLogix product connector, and re-add it manually.


ADVICE WARNING: Removing the wrong connector can seriously damage your System Center Operations Manager environment, so use these scripts at your own risk.

To add the OpsLogix product connector manually in SCOM, you can run the following powershell script:

import-module OperationsManager

$Connector = New-Object Microsoft.EnterpriseManagement.ConnectorFramework.ConnectorInfo

$Connector.Name = “OpsLogix”

$Connector.Description = “Connector for OpsLogix Intelligent Management Packs”

$Guid = “{95d30868-704a-4889-bf89-2ee4ec84c7eb}”

$mg = Get-SCOMManagementGroup

$connection = $mg.ConnectorFramework.Setup($Connector,$Guid)


After running these Powershell commands you should be able to see the connector in the SCOM console.


To remove the OpsLogix product connector run the following powershell script:

import-module OperationsManager

$Connector = Get-SCOMConnector -Name “OpsLogix”





Remove-SCOMConnector $Connector

After removing the connector you might have to restart the SDK Service for System Center Operations Manager. I hope this article was useful and if you have any requests or questions feel free to reach out to our OpsLogix team.

Also make sure to follow us on TwitterFacebookLinkedInGoogle+ and Instragram for more blogs, news, updates and other cool stuff we have coming your way.

Thank you for being AWESOME!

KB1509071142: Using licensing or configuration dashboard with 2 SCOM consoles open

KB1509071142: Using licensing or configuration dashboard with 2 SCOM consoles open


If you have 2 SCOM Operations Manager consoles active at the same time on the same machine and you open the licensing / configuration dashboard to add or change a license or subscription it is possible that you will see incorrect information displayed on the dashboard.

Apply to:

All OpsLogix Management Packs with a licensing or configuration dashboard using an external SCOM SDK connection.


The licensing and configuration dashboards uses the last opened SCOM management group that you selected using the SCOM operations Manager Console. If you open 2 SCOM consoles in succession the settings from the last opened console will be used in the licensing / configuration dashboard.


  • Before using the licensing / configuration dashboards start up a new SCOM operations manager console.


  • only use 1 SCOM operations manager console when using the licensing / configuration dashboards
KB: Fixing the “Object reference not set to an instance of an object” error during the Oracle connection TEST

KB: Fixing the “Object reference not set to an instance of an object” error during the Oracle connection TEST

*Update : Rollup 10 for SCOM 2012 SP1 fixes this issue (

*Update : Rollup 7 for SCOM 2012 R2 fixes this issue (


You are deploying the OpsLogix Oracle Management Pack to an environment using a Windows 2008 R2 (or earlier) server as an Oracle Monitoring Node (1). Using the “Oracle IMP Configuration Dashboard” to setup the Oracle Instances monitoring you get an error message (3) “Object reference not set to an instance of an object” when clicking the “Test Connection” button (2).



This problem is related to the Dot Net version loader. This loader is built into the SCOM agent and will decide with wicht Dot Net version to load at runtime. The OpsLogix Oracle Management pack uses a Dot net 4.0 module. The agent still tryies to load it as a Dot Net 2.0 module which will result in an error.


Since this is an internal SCOM agent issue, and not directly OpsLogix related, we have the following workarounds:

  • Microsoft recognised this issue and indicated that the next RU for SCOM 2012/SP1/R2 will include this loading fix.
  • You can manual install a SCOM Gateway instead of a SCOM agent.
    • You don’t have to generate any certificates.
    • Do NOT run the Gateway Approval tool.
    • Use the Pending Management for approving the agent add (be sure the SCOM security setting allow this)
    • A SCOM Gateway will work exactly like a normal SCOM agent except it is tuned for handling higher workloads.

If you have any questions please contact our support team at