Tao Yang’s Self-Maintenance management pack for OpsMgr 2012

A really cool Self-Maintenance management Pack from Tao Yang:
http://blog.tyang.org/2013/03/03/opsmgr-self-maintenance-management-pack/
An updated version for SCOM 2012 is also available:
http://blog.tyang.org/2014/02/23/opsmgr-2012-self-maintenance-management-pack-update-version-2-3-0-0/

Advertisements

Unseal Management Packs

MP2XMLPRO is a GUI-tool by Tim McFadden that makes it easy to export/unseal any Management Pack:
http://www.scom2k7.com/mp2xmlpro-management-pack-conversion-tool/

A guy named Steve Bernard has also made a GUI-tool for unsealing Management Packs and his tool can also extract bundled binaries:
http://stevesbog.loungent.com/2014/03/04/a-gui-tool-for-unsealing-management-packs-and-bundles-in-scom/#.Uze7eY2KDIU

Check Database Size

There is a standard SQL report that shows how much space a database is using. In SQL Server Management Studio for SQL Server 2008 R2 and newer, right-click on the database you are interested in and select Reports->Standard Reports->Disk Usage.

There is a good description of this report, including information about how to resize a Operations Manager database in the SCOMfaq.ch blog: http://blog.scomfaq.ch/2012/06/26/scom-check-size-of-databases-sql-standard-reports/

The broken Operations Manager Shell

I have a management server with the Operations Manager Console installed. When I tried to start the Operations Manager Shell it failed with the following errormessage:
Import-Module : The specified module ‘OperationsManager’ was not loaded because
no valid module file was found in any module directory.
At line:1 char:14
+ Import-Module <<<< OperationsManager; .OperationsManagerFunctions.ps1; .O perationsManagerStartup.ps1
     + CategoryInfo : ResourceUnavailable: (OperationsManager:String)
        [Import-Module], FileNotFoundException
       + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Comm
        ands.ImportModuleCommand

The term ‘Start-OperationsManagerClientShell’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:Program FilesSystem Center 2012Operations ManagerPowershellOperationsManagerStartup.ps1:26 char:35
+ Start-OperationsManagerClientShell <<<< -ManagementServerName: “” -PersistConnection: $true -Interactive: $true;
         + CategoryInfo : ObjectNotFound: (Start-OperationsManagerClientShell:String) [], CommandNotFoundException
         + FullyQualifiedErrorId : CommandNotFoundException

The reason for this was that the path to “C:Program FilesSystem Center 2012Operations ManagerPowershell” was missing in the envorinmental variable PSModulePath. Once completed and logged out and back in to the system everything worked as espected.