Posts tagged "scom-2"

Remove SCOM Management packs with PowerShell

After importing a newer version of SQL Management pack, in our case ( The older SQL Management packs are no longer needed, because the new one is version-agnostic.

As described in the release notes:
This management pack is version-agnostic, which means that you need only it to monitor SQL Server from 2012 to 2017 and higher. The previous management packs for SQL Server 20082012, 2014, and 2016 have reached the end of support. After importing, this management pack behaves differently depending on whether there are already the previous management packs installed or not. If those are not installed, the management pack will discover and monitor SQL Server 2012, 2014, 2016, 2017 and higher right out of the box, as the previous management packs do that. In the case when there is one or several of the previous management pack for SQL Server 2012, 2014, and 2016, the version-agnostic management pack will disable the discovery and monitoring for those versions of SQL Server that are already monitored by the previous management packs. It is to avoid double monitoring.

Now, it’s time to delete all older SQL Management packs.
Open your Operations Manager PowerShell window. If you cannot find the shortcut on your management server, you can also do a “import-module operationsmanager”

Unattended SCOM Agent installation Windows

Command line is your friend when the SCOM Agent auto deploy functionality does not work for some reason. Because some firewall rules are disabled or something like that.
Or if you need to create a SCCM Package.

Unattended installation with system account:

Unattended installation with SCOM Action account:


IBM Storage management pack SCOM

With the SCOM management pack for IBM you can monitor the following systems:

  • DS8000
  • Flex Systems
  • SAN Volume Controller (SVC)
  • Storwize V3500
  • Storwize V3700
  • Storwize V5000
  • Storwize V7000 & Unified
  • XIV Systems

Logon to your storage system. Add a user for monitoring purpose in the monitoring user group.
Be sure that port 22 is open from the SCOM landscape to the IBM Management Addresses.

Download the newest IBM_Storage_MP_for_SCOM_#.#_Windows setup from the IBM site.
Install the IBM Storage SCOM-control utility.

Import the SCOM management packs, the setup placed them on:
C:\Program Files\IBM\Storage\Host\IBMStorageSCOM\mps

Open the configuration utility command line.

Link IBM Storage SCOM-Control utility with SCOM:
scomu.cmd --sc-set --servername scomsrv01 --domain domain01 --username usr --password pass


  • Password authentication mode:
    scomu.cmd --add -t storwize --ip #### --authmode password --username ### --password ###
  • Public key authentication mode:
    scomu.cmd --add -t storwize --ip #### --authmode publickey --username ### --certpath c:\storwize.cert --passphrase xxxxx

List the added storage systems:
scomu.cmd --list

Delete a connection:
scomu.cmd --del -t storwize.v7000 --ip