Netapp ONcommand Plug-in for SCOM 2019

This week i had the pleasure to install the OnCommand Plug-In to add the NetApp storage systems to our SCOM 2019 environment. It was a rather interesting installation that took me more time then I expected. I had to work around some issues. The software clearly isn’t ready for SCOM 2019. So I decided to write a post about it to maybe help others that suffer with installation problems as well.

Good thing to know is the environment I’m installing to:

• SCOM 2019 on Windows Server 2016
• Programs will all be installed on D:\
• SQL 2016 on Windows Server 2016
• Two dedicated SCOM servers for non server systems (like netapp, nimble, network devices etc.)
• SCOM Console is installed on the two management servers.

First of all you have to download the software with NetApp from the support site using your NetApp account credentials. Also the installation guide and administrations guide are very useful and should be downloaded from here.

Now, I’m not going to talk about all the prerequisites, these are pretty good mentioned in the setup documentation. I will just show you how I took care of the problems that I came across. I will go through the whole setup and mitigate any problem I find.          

Step 1, start setup. As we use UAC  we must confirm everything. When you open the setup click Run to start  

Click Next

Since we need to change the default location to D:\ we click Change.

Change C:\ to D:\ and leave the rest

Click Next

Ok, i would expect that everything would be selected by default… that’s odd….

Let’s select the Integration Feature…. since we need this to administer the NetApp systems in SCOM.

Ok… what the heck is this????? I got the SCOM 2019 console installed to the system. That definitely is a later version than SCOM Console 2012 SP1 . I tried several thing to work around this problem in the current release… no luck…… So … If you click OK

The feature selection will default back and remove the SCOM Console Integration

Ok.. this is a blocking issue for me… so.. the SCOM 2019 console isn’t recognized, but I need this console to add the storage systems to SCOM. What I did from here on is cancel the install, adjusted the SCOM installation and removed the 2019 Console

After that I installed the SCOM 1801 console beside the SCOM1901 Management Server (Yes this works if you install the plain Console MSI) located in the directory %drive%\setup\AMD64\Console

Now if we rerun the istaller we will see that the SCOM Console Integration is preselected. So now we can install the integration plugin, and the upgrade the SCOM console afterwards.

Now we need a service account for the Plugin. Enter the credentials and than click next.

Shit, forgot to add the service account to the local adminsitrators group. Just do it on the spot and contiunue. After that you can click Next.

Enter the database credentials and click Next. For us, this is a remote SQL server.

If everything is working, we can click Next.

Ok, next problem. Database won’t install. So if you google LaunchResult 4, you will find some things. For the record i will first look at the log files.

First i note the location of the log file, than i will click next and afther that cancel to cancel the installation. A rollback will take place.

So copying the first line of the logfile will bring you to a NetApp article.
https://kb.netapp.com/app/answers/answer_view/a_id/1005355/~/create-failed-for-database-ocpmdb-%28oncommand-plug-in-for-microsoft-data-base%29-

After looking at all the requirements and several installations i decided to just pre-create the database at the SQL server using the following SQL query:

Create DB
USE [master]
GO

CREATE DATABASE [OCPMDB]
CONTAINMENT = NONE
ON  PRIMARY 
( NAME = N'OCPMDBData', FILENAME = N'E:\Data\MSSQL13.SQLAMS\MSSQL\DATA\OCPMDBData.mdf' , SIZE = 1048576KB , MAXSIZE = 21474304KB , FILEGROWTH = 20%)
LOG ON 
( NAME = N'OCPMDBLog', FILENAME = N'F:\Logs\MSSQL12.SQLAMS\MSSQL\Data\OCPMDBLog.ldf' , SIZE = 1048576KB , MAXSIZE = 21474304KB , FILEGROWTH = 10%)
GO

ALTER DATABASE [OCPMDB] SET COMPATIBILITY_LEVEL = 130
GO

IF (1 = FULLTEXTSERVICEPROPERTY('IsFullTextInstalled'))
begin
EXEC [OCPMDB].[dbo].[sp_fulltext_database] @action = 'enable'
end
GO
ALTER DATABASE [OCPMDB] SET ANSI_NULL_DEFAULT OFF 
GO
ALTER DATABASE [OCPMDB] SET ANSI_NULLS OFF 
GO
ALTER DATABASE [OCPMDB] SET ANSI_PADDING OFF 
GO
ALTER DATABASE [OCPMDB] SET ANSI_WARNINGS OFF 
GO
ALTER DATABASE [OCPMDB] SET ARITHABORT OFF 
GO
ALTER DATABASE [OCPMDB] SET AUTO_CLOSE OFF 
GO
ALTER DATABASE [OCPMDB] SET AUTO_SHRINK OFF 
GO
ALTER DATABASE [OCPMDB] SET AUTO_UPDATE_STATISTICS ON 
GO
ALTER DATABASE [OCPMDB] SET CURSOR_CLOSE_ON_COMMIT OFF 
GO
ALTER DATABASE [OCPMDB] SET CURSOR_DEFAULT  GLOBAL 
GO
ALTER DATABASE [OCPMDB] SET CONCAT_NULL_YIELDS_NULL OFF 
GO
ALTER DATABASE [OCPMDB] SET NUMERIC_ROUNDABORT OFF 
GO
ALTER DATABASE [OCPMDB] SET QUOTED_IDENTIFIER OFF 
GO
ALTER DATABASE [OCPMDB] SET RECURSIVE_TRIGGERS OFF 
GO
ALTER DATABASE [OCPMDB] SET  ENABLE_BROKER 
GO
ALTER DATABASE [OCPMDB] SET AUTO_UPDATE_STATISTICS_ASYNC OFF 
GO
ALTER DATABASE [OCPMDB] SET DATE_CORRELATION_OPTIMIZATION OFF 
GO
ALTER DATABASE [OCPMDB] SET TRUSTWORTHY OFF 
GO
ALTER DATABASE [OCPMDB] SET ALLOW_SNAPSHOT_ISOLATION OFF 
GO
ALTER DATABASE [OCPMDB] SET PARAMETERIZATION SIMPLE 
GO
ALTER DATABASE [OCPMDB] SET READ_COMMITTED_SNAPSHOT OFF 
GO
ALTER DATABASE [OCPMDB] SET HONOR_BROKER_PRIORITY OFF 
GO
ALTER DATABASE [OCPMDB] SET RECOVERY SIMPLE 
GO
ALTER DATABASE [OCPMDB] SET  MULTI_USER 
GO
ALTER DATABASE [OCPMDB] SET PAGE_VERIFY CHECKSUM  
GO
ALTER DATABASE [OCPMDB] SET DB_CHAINING OFF 
GO
ALTER DATABASE [OCPMDB] SET FILESTREAM( NON_TRANSACTED_ACCESS = OFF ) 
GO
ALTER DATABASE [OCPMDB] SET TARGET_RECOVERY_TIME = 60 SECONDS 
GO
ALTER DATABASE [OCPMDB] SET DELAYED_DURABILITY = DISABLED 
GO
ALTER DATABASE [OCPMDB] SET QUERY_STORE = OFF
GO
USE [OCPMDB]
GO
ALTER DATABASE SCOPED CONFIGURATION SET LEGACY_CARDINALITY_ESTIMATION = OFF;
GO
ALTER DATABASE SCOPED CONFIGURATION SET MAXDOP = 0;
GO
ALTER DATABASE SCOPED CONFIGURATION SET PARAMETER_SNIFFING = ON;
GO
ALTER DATABASE SCOPED CONFIGURATION SET QUERY_OPTIMIZER_HOTFIXES = OFF;
GO
ALTER DATABASE [OCPMDB] SET  READ_WRITE 
GO

After this the instalation completed succesfully. Don’t forget to upgrade your SCOM console back to 1901 !!!