mpcatalog / scom-community-catalog Goto Github PK

Hi,

Renaming management packs. Apart from all SCOM enivronments will have to delete and import the "new" MP. is there other potential issues?

In latest release of the Query Ole DB monitor the monitor MP has been removed.
UretzkyZvi/Database-Query-Result-Monitoring-Management-Pack-for-SCOM#2

And when that MP is not installed it wont get detected by the Community Management pack.

Also the version number is incorrect it should be 1.0.0.1 (for QueryOleDbMonitorLibrary) or 2.0.0.5 if you target the QueryOleDbMonitorTemplate

Hi guys,

I think the following is worth to be added:
https://gallery.technet.microsoft.com/SCOM-AD-Directory-Addendum-22d0473a

Thanks :)

Ruben

Is this issue related to a bug in the UI?

If yes, please create a new issue in the UI repo

Have you included the following?

New Packs

• A descriptive title : ABC.Windows.Server.AdminInfo | Duplicate Alert Discovery
• MP SystemName: ABC.Windows.Server.AdminInfo
• MP Display Name: ABC.Windows.Server.AdminInfo | Duplicate Alert Discovery
• MP Current Version: 1.0.0.39
• MP Download URL: https://github.com/MPCatalog/scom-community-catalog/tree/master/ABC.Windows.Server.AdminInfo

Pack Updates

• A descriptive title
• MP SystemName

Management Pack works as it should, however upon every 10 days or when SCOM Health Explorer stats are reset & re-calculated manually, the Alerts are duplicated multiple times and Alert Count multiplies as per the number of entries (even though they are duplicated). As per screenshot, details are listed.

@Juanito99 #100

The Docker managementpack in this catalog points to a url where the pack cannot be found.
https://gallery.technet.microsoft.com/UNIXLinux-Docker-ecc6d024

Is it still available?

Hi,

our SCOM is sitting behind a proxy server. It is maintained in the server configuration:

After clicking on 'Discover Community Packs' an exception window is thrown and the SCOM console crashes.

The text goes as follows:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.AggregateException: One or more errors occurred. ---> System.Exception: Unable to resolve the index location from http://www.mpcatalog.net/CatalogRepo
at Community.ManagementPackCatalog.UI.Models.GitHubRepository.d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Community.ManagementPackCatalog.UI.Models.GitHubRepository.d__9.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at System.Threading.Tasks.Task.Wait()
at Community.ManagementPackCatalog.UI.DiscoverCatalogPacks.PopulateCommunityManagementPackListFromGitHub(GitHubPackDetail[] packsToDisplay)
at Community.ManagementPackCatalog.UI.DiscoverCatalogPacks..ctor()
--- End of inner exception stack trace ---
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.EnterpriseManagement.ConsoleFramework.Wpf.GenericWpfViewConstructor.CreateView(Object parent, Type viewType, IViewParameters viewParameters)
at Microsoft.EnterpriseManagement.ConsoleFramework.ViewConstructor.BeginShow(ShowViewContext showViewContext, AsyncCallback callback, Object state)
at Microsoft.EnterpriseManagement.ConsoleFramework.Wpf.GenericWpfViewConstructor.CreateNonRecyclableView(ShowViewContext showViewContext)
at Microsoft.EnterpriseManagement.ConsoleFramework.Wpf.GenericWpfViewConstructor.CreateAndShowViewCore(ShowViewContext showViewContext)
at Microsoft.EnterpriseManagement.ConsoleFramework.Wpf.GenericWpfViewConstructor.ShowViewOperation.Begin(ShowViewContext showViewContext)
at Microsoft.EnterpriseManagement.ConsoleFramework.Wpf.GenericWpfViewConstructor.BeginShow(ShowViewContext showViewContext, AsyncCallback callback, Object state)
at Microsoft.EnterpriseManagement.ConsoleFramework.Wpf.ConsoleViewDisplayService.OpenViewJob(Object sender, ConsoleJobEventArgs args)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler1 job, Object sender, ConsoleJobEventArgs args) at Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleJobsService.RunJob(ConsoleJobDescription jobDescription) at Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobsService.RunJob(ConsoleJobDescription jobDescription) at Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobsService.RunJob(IComponent jobOwner, EventHandler1 jobMethod, EventHandler1 errorHandler, Object[] arguments) at Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobsService.RunJob(IComponent jobOwner, EventHandler1 jobMethod, Object[] arguments)
at Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobsService.RunJob(EventHandler`1 jobMethod, Object[] arguments)
at Microsoft.EnterpriseManagement.ConsoleFramework.Wpf.ConsoleViewDisplayService.OpenView(String assemblyName, String typeName, String target, String item, String criteria, Object[] arguments)
at Microsoft.EnterpriseManagement.Monitoring.Console.Common.ConsoleDisplayWrapper.OpenView(String assemblyName, String typeName, String target, String item, String criteria, Object[] arguments)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.MomViewsDisplay.OpenMomView(IComponent component, ManagementPackView view, String target, String item)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Administration.AdminTreeView.LaunchView(AdminTreeDataNode viewNode)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Administration.AdminTreeView.HandleNodeSelected(Object sender, TreeViewEventArgs e)
at System.Windows.Forms.TreeView.TvnSelected(NMTREEVIEW* nmtv)
at System.Windows.Forms.TreeView.WmNotify(Message& m)
at System.Windows.Forms.TreeView.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Thanks in advance

Ruben

This management pack was designed with two parts. These parts, contained in a single Rule and one Data Source Method, were broken up to provide System Center Operations Manager with the ability of automatically placing a system into Maintenance Mode using System Center Configuration Manager Service Windows.

https://systemcenter.wiki/?GetCategory=SCCM+Service+Window+to+SCOM+Maintenance+Mode+Automation

Web:
https://rburri.wordpress.com/2014/08/12/scheduled-task-and-ps-scheduled-job-management-pack-1-2-0-500/

Download;
https://onedrive.live.com/redir?resid=8E65D7FF8119FFA6!161&authkey=!AD2usfPtucDzaY4&ithint=file%2czip

Author
Raphael Burri

Comment:
Works great, also for Windows Server 2016 OS !

New Packs

• The SCOM Management pack to add some alert tasks to SCOM console to get information about monitor/rule overidable parameters, its settings and so on.
• SCOM.Alert.Tasks
• SCOM Alert Tasks
• 1.0.0.5
• https://github.com/msalomoun/SCOM.Alert.Tasks

No issue, but both are worth to know:

https://www.progel.it/prodotti/Pagine/Windows-Scheduled-Tasks-Management-Pack.aspx

https://www.scutils.com/products/apcupsmonitoring

With Exchange 2013 Exchange Product Group has chosen a different route and implemented all the monitoring inside Exchange server which is called Exchange Managed Availability. When it comes to monitoring from Operations Manager all we have is a discovery scripts, some perf collection rules and one (yes only one) event monitor which tracks the events created by Exchange Managed Availability Service. I will not be getting into the Managed Availability and its components. As a summary it has different components called health sets and Exchange server performs ~650+ individual checks on these various components.

One of the problems of this component/service based approach is now we don’t have the visibility to individual objects like Mailbox Databases or Transport Queues. These are hidden under specific health sets. After using his management pack in many customers I wanted to do the same for Exchange 2013. I have used his techniques but I had to modify them to work with my own requirements. I have also added some extra monitors rules and added Queue monitoring.

https://systemcenter.wiki/?GetCategory=Exchange+Server+2013+Addendum+Management+Pack

Is this issue related to a bug in the UI?

If yes, please create a new issue in the UI repo

Have you included the following?

https://gallery.technet.microsoft.com/SCOM-Windows-Service-c9fc3f95?ranMID=24542&ranEAID=TnL5HPStwNw&ranSiteID=TnL5HPStwNw-1ye4S1MnAJaeunDQ7lQklg&tduid=(0cc497f76ce5c60d8f7081cd298077bf)(256380)(2459594)(TnL5HPStwNw-1ye4S1MnAJaeunDQ7lQklg)()

https://leibundgutski.wordpress.com/2017/02/19/scom-windows-service-monitor-management-pack/

New Packs

• [ x] A descriptive title: Service Monitoring
• MP SystemName
• MP Display Name
• MP Current Version
• MP Download URL

Pack Updates

• A descriptive title
• MP SystemName

QueryOleDB needs to be adjusted to target the correct file in the management pack.

It would be great if the Wiki could be extended with some contribution guidelines and/or any criteria that must be met for a PR to be accepted.

For example, I hear the index.json file needs to be alphabetically sorted - if this is the case it should probably be stated so moderators don't need to comment on most PRs if the author didn't happen to naturally do this.

Not an issue but a tip.
Here are some tips for management packs that are missing from the database.

ID: Eaton.UPS.Monitoring
Name: Eaton UPS Monitoring
1.0.1.15
https://powerquality.eaton.com/Products-services/Power-Management/Software-Drivers/MS-SCOM-Management-Pack.asp

ID: DataCore.SANsymphonyV.Library
Name: DataCore SANsymphony-V Library
1.3.0.13123
https://www.datacore.com/solutions/by-virtualization-platform/Microsoft/system-center-monitoring-pack.aspx
Need license for the product

HewlettPackard.ProLiant.Monitored.Library
Hewlett-Packard ProLiant Monitored Library Management Pack
3.1.0.0
HewlettPackard.Servers.Library
Hewlett-Packard Servers Core Library
2.3.0.0
https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=HPSCOMMP-P
Product #:
HPSCOMMP-P
Global Trade ID:
Z7550-63218
Version:
1.80
Software specification:
HPE ProLiant Management Pack for System Center Operations Manager (Z7550-01351.exe)
HPE BladeSystem Management Pack for Microsoft System Center Operations Manager (Z7550-01573.exe)

HPEnterpriseStorageLibraryMP
HPE Storage Library Management Pack for System Center
4.5.0.0
https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=System_Center

Hi Daniele ( @brandubh ),

could you help to arrange an update to the current OS versions?

Many thanks in advance

Ruben

The SQL server runas addendum management pack is not detected as installed.

The reason could be that the name of the management pack is the following:
2005->
Microsoft SQL Server 2016 RunAs Addendum Management Pack
Microsoft.SQLServer.RunAs.2016.Addendum
Microsoft SQL Server 2014 RunAs Addendum Management Pack
Microsoft.SQLServer.RunAs.2014.Addendum
Version 6.7.31.0

And the library:
Microsoft.SQLServer.RunAs.Addendum.Library
Microsoft SQL Server RunAs Addendum Library Management Pack
Has version 6.7.7.2

Is this issue related to a bug in the UI?

No

The Appveyor tests are failing because the Pester tests are currently written for V3 (I think) rather than V5 which introduced substantial changes.

v3 to v4
v4 to v5

Whilst all the tests are failing in AppVeyor (e.g. here) the failures are occurring in the discovery phase rather than the test phase, meaning that no tests are run (or fail) causing the tests to 'pass' in Github.

Hi,

found "Agent Management" which helps to add or remove Management Groups.
It sill works in SCOM 1801; just tested 😄

Details here:
URL

Please add. Worth it.

Is this issue related to a bug in the UI?

If yes, please create a new issue in the UI repo

Have you included the following?

New Packs

• A descriptive title : ABC.Windows.Server.AdminInfo | Duplicate Alert Discovery
• MP SystemName: ABC.Windows.Server.AdminInfo
• MP Display Name: ABC.Windows.Server.AdminInfo | Duplicate Alert Discovery
• MP Current Version: 1.0.0.39
• MP Download URL: https://github.com/MPCatalog/scom-community-catalog/tree/master/ABC.Windows.Server.AdminInfo

Pack Updates

• A descriptive title
• MP SystemName

Management Pack works as it should, however upon every 10 days or when SCOM Health Explorer stats are reset & re-calculated manually, the Alerts are duplicated multiple times and Alert Count multiplies as per the number of entries (even though they are duplicated). As per screenshot, details are listed.

Please add to the catalog:
https://gallery.technet.microsoft.com/SCOM-2012-and-2016-2ccc45c0

Author Kevin Holman