Multiple Objects in Dynamic Groups

Creating a dynamic group makes life easier for overrides, views and reports (the main uses of groups). When a new object is discovered it automatically joins the group if it matches the criteria. And that means that your overrides, views and reports take that into account without any intervention on your part.

These are usually quite simple to create based on a number of criteria. I was wanting to build a group that matched either wildcard 1 or wildcard 2. It was not initially obvious how to do it so I thought I would document it.

Although this helped http://social.technet.microsoft.com/wiki/contents/articles/7205.operations-manager-dynamic-group-examples.aspx as it showed it was possible (for example a group with C: and D: drives) it did not show how to actually do it.

Start by finding the class and add it. It will show as AND group. If you add your criteria you will get this.

Dynamic group 1

Formula

( Object is Scheduled Tasks 2008 Job AND ( Job Name Matches wildcard User_Feed_Synchronization* ) AND ( Job Name Matches wildcard GoogleUpdateTask* ) )

This will obviously never work. We need an OR not an AND.  Putting the OR between the two expressions does not do what you think it would do. You would expect it to say if it is a Scheduled Task and either of the expressions is true then add the object. But what you need to change is the class expression to an OR group. And the way you do that is by right clicking on that expression.

Dynamic group 2

Now you can switch to an Or Group.

Dynamic group 3

Now the formula is

( Object is Scheduled Tasks 2008 Job AND ( Job Name Matches wildcard User_Feed_Synchronization* ) OR ( Job Name Matches wildcard GoogleUpdateTask* ) )

Which is what is required. If the scheduled task matches either wildcard then it belongs to the group. Easy when you know how.

SQL SPN Alert

This alert seems to come up regularly. If you search for it then this post from 2012 by Marnix Wolf comes up saying just to disable the alert.

http://thoughtsonopsmgr.blogspot.co.uk/2012/04/scom-r2-alert-sql-server-cannot.html

I would have thought it would have been fixed by now. I am using version 6.4.1.0 of the SQL MP. I tried to do it from the alert help and it seemed to work so when I pushed some more agents out and a couple of new alerts appeared from 2 more SQL Servers. I tried the setspn command again but this time it did not work with the following error:-

Unknown parameter MSSQLSvc/ServerFQDN:1433.  Please check your usage.

After some searching I came across this page on Technet. “How to Configure an SPN for SQL Server Site Database Servers” http://technet.microsoft.com/en-gb/library/bb735885.aspx

It was not so much the article but a comment from Asif Shafi that provided the answer – “Do not copy and paste syntax from this article as it has invalid characters”.

He provided a couple of examples and I copied those and inserted my server and account details in and this time it work straight away.

That was weird as I copied the original details to notepad first and then copied them into a command line. From my Notepad file I copied and pasted another server and got the same error. But when I typed it exactly as it was in Notepad it worked. I am perplexed how strange characters or formatting can get into Notepad. And I tried copying the faulty line into Notepad++ as well with the same results.

I did some further investigation and it turned out to be the dash in front of the A. So if you get this error try the command again but delete the dash and type the dash in again. That sorted it on the copy and paste I tried. In a few minutes the alerts disappeared. But at least I now know a way that works and clears the alert.

Note that if you run the command (with the right characters) again you will get the following error “Duplicate SPN found, aborting operation!” and your SPN will be left as is.

You may also see information on using ADSIEdit as per http://support.microsoft.com/kb/319723. I did not try this method but I have used this method before on the SCOM service as proposed by Kevin Holman.

http://blogs.technet.com/b/kevinholman/archive/2007/12/13/system-center-operations-manager-sdk-service-failed-to-register-an-spn.aspx

MP Author SP1

I received an email that the free MP authoring tool from Silect is now at SP1. But there is very little information about what is contained in this upgrade. There is still just the single exe file and the PDFs for installation and getting started. I run the exe and it upgraded my existing installation without any problems.

This is the about screen for RTM.

Image

And for SP1

Image

As well as the version increase there is a Feature added – Maximum users = 100.

The only thing that the web site seems to say is integration with MP Studio. Their web page has a video of the integration with MP Studio but it also walks through creating a basic management pack (very quickly). But it is a great little video to get an idea of how much better MP Author is compared to the old Microsoft Authoring Console for 2007.

From http://www.silect.com/mp-author

New MP Author SP1 is now fully integrated with MP Studio v5.2 – check out the new video demo here.

Review of Infront’s Orchestrator Runbook MP

I was working on a project where Orchestrator 2012 SP1 plays a big part in linking and automating the various parts of the solution which includes Service Manager, Operations Manager, BMC and Orion as well as custom databases. Therefore it was essential that Orchestrator is properly monitored. While Microsoft produce a MP for Orchestrator it is a bit of a disappointing MP (version 7.0. Version 7.2.12.0 has been released since I did this work but still does not monitor Runbooks) which basically monitors the services and a few bits and pieces but not Runbooks. The trouble with the Common Engineering Criteria is that, while it is a good thing that the Product Groups have to create an MP for their product, there is no definition of what it should contain and no quality bar. While some Product Groups are very good at creating a good MP some just go for the simplest tick in the box they can get away with. It is very disappointing when one of the System Center products falls into that category.

Fortunately there is an answer and that is the Infront Consulting System Center Orchestrator Management Pack. http://infrontconsulting.com/services/infront-software/.

This is a free MP that works on SCOM 2007 R2 and 2012. You do need to register to be able to download it and you need to provide the name of the Management Group. They use the MG name as part of the install process. I am not sure why they do that. Maybe at one stage they were going to sell it or they are just testing that technology to see how it works.  It does mean that installation is a bit different from importing an MP but is quite quick and painless. Once I tested it in the test environment a quick e-mail with the names of the other management groups got us the files for use with each Management Group. The version that I am reviewing is 2.1.2.7 and this was run on SCOM 2012 SP1.

This MP is about monitoring the Orchestrator Runbooks. As these are the key parts of what makes Orchestrator work it is a great solution for monitoring your Orchestrator Runbook servers. Initially when installed it does nothing, which I like. The first thing is to create an override to discover the servers the Runbooks are running on. There is only one monitor that is enabled by default and that checks if there has been a failure with the Runbook. The next time the Runbook succeeds then the monitor will clear. And to be honest if that was all the MP did it would be a good enough reason to install it.

Monitors

  • Last Runbook execution succeeded.
  • Runbook is executing
  • Runbook is checked in.

Runbook Health State

There are other monitors and rules that are switched off by default. One of them is if a Runbook is checked out for a length of time (15 minutes by default). This is handy as Runbooks should not be checked out unless they are being updated. As the MP discovers the Runbooks they are listed as objects so individual Runbooks can be put into maintenance mode while work is being done on them.

Another monitor is checking that a Runbook that is supposed to be continuously running actually is. For this one you need to create a group using the attribute “Manually Triggered”. This means you can target the monitor at Runbooks which need to be constantly running rather than those that get called by another Runbook when needed.

As well as the rule and monitors there are a number of performance collection rules which makes it easy to see how frequently Runbooks are getting called and how long they take to run. This was an interesting one as some Runbooks were taking a long time and so need investigating.

Rules

  • SC Orchestrator Runbook Instance Failed (With Suppression)
  • SC Orchestrator Runbook Instance Failed (Without Suppression)

Active alerts

Rules – Performance Collection

  • SCO Runbook Average Execution Time Collection Rule
  • SCO Runbook Failed Instances Collection Rule
  • SCO Runbook In Progress Instances Collection Rule
  • SCO Runbook Success Instances Collection Rule
  • SCO Runbook Total Finished Instances Collection Rule
  • SCO Runbook Warning Instances Collection Rule

Performance - Completed success

Performance - Completed Instances

There are no built in reports but the fact that the counters are collected means that you can use the generic performance report to create your own.

Once running you soon realise that a naming standard is critical for your Runbooks. If you start getting more and more Runbooks being used, then when the alert comes up about a particular Runbook you will want to quickly find it. The same is true to see the Runbooks in Service Manager. You will see a list of Runbooks without the hierarchy so a good naming convention really helps. The sessions done by Pete Zerger and Anders Bengtsson at MMS 2013 are essential viewing for anyone involved in Orchestrator in my opinion.

Best Practices For Runbook Authoring and Managing Orchestrator

http://channel9.msdn.com/Events/MMS/2013/SD-B317

Tasks

  • Start Runbook
  • Start Runbook with Parameters

A couple of handy tasks to save you having to logon to an Orchestrator server.

Issues

The one issue I have seen is with the alert that a Runbook is checked out. In the alert description it says the person that checked it out and the Runbook but the date and time is blank. The information is in the alert context. Looking at the alert context the date is in US format whereas the servers I was working on are in UK format. I have passed this information on to Infront.

Not an issue but it would be nice to have the group already created that discovers Runbooks that are set to continuously run.

The monitor “Last Runbook execution succeeded” resolves when the Runbook succeeds. This means that it creates and alert and quickly clears it if you have a busy Runbook. Therefore be sure to check the closed alerts to see if this is happening. Also the most common alerts report also highlighted this as an issue. It enabled us to find a problem with a particular Runbook. Most of the time it succeeded but occasionally it would fail. Checking the failures we found there was an issue with the way the alert description was formed occasionally that meant the Runbook picked up the wrong information and failed when creating an incident as the name was too long in those instances.

Summary

This is an essential MP if you are using Orchestrator and would like it to be properly monitored. The ability to get alerted on errors and on when Runbooks are not running or have been checked out is very useful as it is difficult to see that information in the Runbook console. The documentation is clear and easy to follow. Thanks to Infront Consulting for taking the time and effort to create this MP and release it for free. And shame on Microsoft for not doing something similar in the Orchestrator MP.

Highly recommended.

MP Author from Silect (Bridgeways)

Simon Skinner Tweeted about this in December and Daniel Savage, Program Manager – System Center, has just blogged about it – http://blogs.technet.com/b/momteam/archive/2014/01/13/mp-blog-the-right-tool-for-the-right-job.aspx.
This has been released as a free tool and the download is 23.5 MB.

Daniel says “MP Author allows users to develop management packs without needing XML skills. Utilizing a wizard-driven designer and a simple, intuitive browse and select interface, MP Author guides users through pre-populated and pre-configured steps to design new and/or customize existing management packs to specifically meet their unique business needs.

This tool fills a much needed gap in the portfolio for providing an IT Pro orientated tool for MP Authoring.”

This is excellent news as the old Authoring Tool for 2007, while it could create MPs and be used in 2012 was clunky and VSAE is a hard curve for non-developers. Plus you have to purchase a copy of Visual Studio to use it. The Visio Management Pack Designer (http://technet.microsoft.com/en-us/library/hh457569.aspx) is quite neat but it is still in its infancy. But according to Stefan Stranger this tool will no longer be developed or supported.  For IT Pros to create MPs outside of the SCOM console it was not easy. I have downloaded the tool and will be having a look at it to see how it stands up.

Be aware that when you go the download page at http://bridgeways.com/mp-author-landing-page  and fill in your details and click Download Now you are given a pop up allowing you to purchase Premium Support.

MP Author Premium Support

Then it takes you to a page when you can compare MP Author and MP Studio (and get quite a big discount on MP Studio).

Silect MP Author v MP Studio

MP Studio Discounted Price Jan 2014

When you click Download it takes you back to the first page and it looks like you cannot download the program but in fact you have been sent an e-mail with a link to download the program.

The downloaded zip file comes with an exe and 2 PDFs – the installation guide and the user guide. This creates 2012 MPs so you will not be able to create MPs for use in 2007. Stefan has a blog post showing a step by step installation and a quick first look.

http://blogs.technet.com/b/stefan_stranger/archive/2014/01/13/new-tool-for-mp-authoring.aspx

I look forward to seeing how it stands up to the other authoring tools.

SQL Server 2012 DB Engine Group Problem

I was checking out some reports on the SQL Server MP as I had installed the new 6.4.0.0 version in a test system but still had 6.3.173.1 in production. When looking at group membership I noticed that there were a few SQL servers missing from the SQL Server 2012 DB Engine Group but that they were all shown as members of the group SQL Server 2012 Computers. But this was consistent for both versions of the MP.

The SQL 2012 DB Engine Group dynamic membership rule is

( Object is SQL Server 2012 DB Engine AND ( Version Matches wildcard 11.0.* ) AND True )

But all the SQL 2012 SP1 Servers were 11.1.3000. So this would never work. Initially I thought it was a bug in the MP but looking at version numbers according to Microsoft the SP1 version is 11.0.3000.00 which would mean that the group membership would work.

http://www.microsoft.com/en-gb/download/details.aspx?id=35575#

Versions shown on http://social.technet.microsoft.com/wiki/contents/articles/783.sql-server-versions.aspx

Even CU5 for SP1 is 11.0.3373.0.

http://support.microsoft.com/kb/2861107

This was puzzling as this did not match the version numbers of the customer. Searching on the web I saw a few more mentions of 11.1.3000.

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/78268cc9-5a3a-440c-b950-e2e7edf817d2/msiexecexe-processes-keep-running-after-installation-of-sql-server-2012-sp1

But nothing to say why there were these two version numbers for the same product. The customer had Enterprise, Standard and Developer and all versions were 11.1.3000.0 if SP1 was installed.

 

On the SQL Server when I do

select @@version

Microsoft SQL Server 2012 (SP1) – 11.0.3000.0 (X64)

                Oct 19 2012 13:38:57

                Copyright (c) Microsoft Corporation

                Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

Then I get 11.0.3000.0

But from SCOM Discovered Inventory

Display Name SCOMOPERATIONS

Full Path Name server.local\SCOMOPERATIONS

Instance Name SCOMOPERATIONS

Version 11.1.3000.0

Edition Standard Edition

I get 11.1.3000.0

 

In Registry

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\SQLServer2012\CurrentVersion

It shows 11.1.3000.0

I tried looking at the SCOM discovery script for SQL Server 2012 DB engine but it goes on for pages and pages and pages and uses WMI. I am presuming if I found this registry key wrong then the script will find the wrong registry key wherever it is looking which it must do as it returns that value. So it looks like it is a SQL problem putting the wrong value into the registry and the MP developers were going by the documentation.

A search for 11.1.3000 finds that it is in these registry keys (and a lot more for SQL)

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\Tools\Setup
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\Tools\Setup\Client_Components_Full
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\Tools\Setup\Client_Components_Full\1033
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\Tools\Setup\SQL_SSMS_Adv
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\Tools\Setup\SQL_SSMS_Adv\1033
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS11.SCSM\Setup
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS11.SCSM\Setup\Analysis_Server_Full
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSRS11.SCOMOPERATIONS\Setup
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSRS11.SCOMOPERATIONS\Setup\RS_Server_Adv
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSRS11.SCSM\Setup
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSRS11.SCSM\Setup\RS_Server_Adv
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.SCOMDW\Setup\SQL_Engine_Core_Inst
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.SCOMDW\Setup\SQL_Engine_Core_Inst\1033
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.SCOMDW\Setup\SQL_FullText_Adv
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.SCOMOPERATIONS\Setup
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.SCOMOPERATIONS\Setup\SQL_Engine_Core_Inst
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SqlDom\CurrentVersion
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\sqlls\CurrentVersion
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLNCLI11\CurrentVersion
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SqlWriter\CurrentVersion
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SQLNCLI11
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products22C2487A9E6A5D4EA07E03128178F38\InstallProperties
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB2674319
  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server 2012 Redist\SQL Server System CLR Types\1033\CurrentVersion_64

A search for 11.0.3000 only finds a number of names under this one key
HKEY_CLASSES_ROOT\Installer\Assemblies\Global
Name = Microsoft.AnalysisServices,fileVersion=”11.0.3000.0″,version=”11.0.0.0000″,culture=”neutral”,publicKeyToken=”89845DCD8080CC91″,processorArchitecture=”MSIL”

 

All very confusing but if you have SQL 2012 SP1 then be aware that the group SQL 2012 DB Engine Group will not pick up any 2012 SP1 SQL DB engines.

If you need to have a group targeted at all SQL 2012 DB Engines then either use the SQL 2012 Computer group or create your own group with the formula:

( Object is SQL Server 2012 DB Engine AND ( Version Matches wildcard 11.* ) AND True )

The SQL team need to get their installation or documentation fixed and/or the MP team need to update the SQL MP.

System Center 2012 SP1 Update Rollups

Update Rollup 3 has arrived but not all products are updated. I have created this matrix to show what product has been updated with each rollup.

Rollup UR1 UR2 UR3
Article 2785682 2802159 2836751
App Controller KB2790935 KB2815569 KB2853227
App Controller Setup Update N/A N/A KB2823452
Configuraturtion Manager * * *
Data Protection Manager KB2802095 KB2822782 KB2853210
Operations Manager KB2784734 KB2826664 KB2852565
Operations Manager – UNIX/Linux KB2784734 KB2828653 KB2852565
Orchestrator N/A KB2828193 N/A
Service Manager N/A KB2828618 N/A
Service Provider Foundation KB2785476 N/A N/A
VMM Administration Console KB2792925 KB2826392 KB2858509
VMM Server KB2792926 KB2826405 KB2858510
VMMr Guest Agent N/A N/A KB2858511

 

Description of Update Rollup 1 for System Center 2012 Service Pack 1 http://support.microsoft.com/kb/2785682
Description of Update Rollup 2 for System Center 2012 Service Pack 1 http://support.microsoft.com/kb/2802159
Description of Update Rollup 3 for System Center 2012 Service Pack 1 http://support.microsoft.com/kb/2836751

* Configuration Manager has seprate updates and calls them Cumulative Updates
Description of Cumulative Update 1 for System Center 2012 Configuration Manager Service Pack 1 http://support.microsoft.com/kb/2817245
Description of Cumulative Update 2 for System Center 2012 Configuration Manager Service Pack 1 https://support.microsoft.com/kb/2854009

I am not sure why some products just have one KB per UR while others have multiple. And OpsMgr switches between both methods.

System Center is supposed to be heading to be a product with the old products SCOM, SCVMM etc just being elements of that product the way that Office went. But you can only license System Center as a suite. This presentation from MMS by Carmen Summers, Senior Program Manager, Microsoft is interesting and shows the way they are heading and the challenges that they face with this approach. Anyone who has tried to work out what SQL Collation is required for all the System Center components to co-exist on one SQL Server will know what I mean.

System Center 2012 SP1 Simplifications and Upgrades, MMS 2013 – http://channel9.msdn.com/Events/MMS/2013/SD-B203

 

 

SCOM to SCSM Connector Stops

I had a situation that the SCOM to SCSM (both 2012 SP1) had stopped several days ago yet the CI Connector showed that it was still working. There was no obvious reason why this connector was still working when the alert connector was not.Looking at the SCOM side and showing the column Forwarding Status then I could see that all the alerts that met the criteria were showing as Forwarding Pending. This showed that the SCOM side was putting the alerts up for SCSM to pick up but SCSM was not picking them up. When I clicked the Synchronise Now button on the connector in SCSM the following event was generated.

Warning event 34070
Source – Operations Manager Connector

Error of type System.Xml.XmlException while reading configuration. The following information may help take corrective action:
Message: An error occurred while parsing EntityName. Line 1, position 958.
Subsequent error messages in the event log will indicate the affected connector. In order to correct this error, export the  ServiceManager.LinkingFramework.Configuration management pack, correct the connector configuration, and then reimport the management pack.

The named MP (ServiceManager.LinkingFramework.Configuration) was exported and I looked at it in an editor. Line 1 was the normal MP start line and certainly did not have 958 characters. But down in the XML there was this section:- 

<ComputerCriteriaRule>

                      <Name>Customer A &amp; B Incidents</Name>

                      <TemplateId>8f5bfff8-2e46-a477-58a0-8e60d4b3b59d</TemplateId>

                      <AlertSeverity>Error</AlertSeverity>

                      <CriteriaType>Computer</CriteriaType>

                      <ComputerCriteria computerGroup=”Customer A &amp; B” />

            </ComputerCriteriaRule>

While the line number and character number in the event was no help it did point me to the correct MP to look in. I was wary as soon as I saw the ampersand which is a reserved character in XML and even though it was encased properly as &amp; I decided to try that first.

There were a number of Alert Routing Rules that had been created. These used groups to determine which template a particular alert should use when it comes in. One of these groups and the template had an ampersand (&) in the name. This Alert Routing Rule was deleted and the connector sprung back into life. The group and template were renamed without the ampersand and put back into the Alert Routing Rule table and all is fine now. 

 

PowerShell Get-Member

In the past when I have wanted to find out the names of the fields used by get-scomalert, get-scommanagementpack, get-scomagent etc I have piped the command to a csv file and opened it up in Excel. Just recently I have found out about get-member. This is great for getting a list of the properties or a command so you can find out what the fields are.

Examples
get-scomalert | Get-Member
get-scommanagementpack | Get-Member
get-scomagent | Get-Member

As well as finding out the name of the property it tells you whether you can change it. For example in get-scomalert:

NetbiosComputerName Property string NetbiosComputerName {get;}
Owner Property string Owner {get;set;}

NetbiosComputerName cannot be changed but Owner can as you can see a set as well as a get.

SCSM 2012 – SCOM CI Connector Warnings

When you setup the CI (Configuration Items) connector from SCOM to SCSM it expects that the classes that are in SCOM are in SCSM as well. This is achieved by importing the SCOM MPs that have all the classes defined. This is usually the Library MPs but other MPs may have classes in as well and some MPs may reference others and so cannot be imported without the MP that it references. It is usually easier to import all the MPs imported into SCOM rather than work out the tangled relationships!

As this is important you would expect that the SCSM MP would warn you if there are problems with this. The latest MP, Service Manager 2012 MP v 7.5.1561.0, does not do this. The MP does check that the SCSM server key areas are working but there does not seem to be any rules or monitors for the connector. But there are warning events in the OperationsManager log though. These three were the ones seen but there may be others.

Event – 34093

Connector Name=SCOM to SCSM CI Connector, Id=143ebfac-999c-1e31-2736-469f0b850b8b Class Microsoft.Windows.DNSServer.Library.Server was not found in Service Manager. The management pack Microsoft.Windows.DNSServer.Library in which the class was defined may have been removed from Service Manager since synchronization  was setup.  Ensure that the management pack is present in Service Manager or edit the connector configuration to remove it from the list of synchronized management packs.

Event – 39094

Connector Name= SCOM to SCSM CI Connector, Id=143ebfac-999c-1e31-2736-469f0b850b8b Cannot create part of service map [Active Directory Topology Root]. Skipped component: Microsoft.SystemCenter.Apm.CsmAgent. Class of skipped component: Client-Side Monitoring Agent.  The component Microsoft.SystemCenter.Apm.CsmAgent is defined in management pack Operations Manager APM Infrastructure. Check for prior errors that indicate if importing a missing management pack can help resolve this issue.

Event – 34096 

Connector Name=SCOM CI Connector, Id=069e77c4-42e5-9e24-8488-e72fb160e1a6
Skipping import of instances of class Microsoft.Windows.Server.6.2.NetworkAdapter. The management pack Microsoft.Windows.Server.Library that defines this class has version 6.0.7026.0 in Operations Manager that is higher than its version 6.0.6989.0 in Service Manager.
The following steps will resume import of instances of this class:
1) Import management pack Microsoft.Windows.Server.Library with version 6.0.7026.0 into Service Manager.
2) Edit the connector configuration and ensure that this management pack is selected for synchronization.

In one case the Windows Server OS had been updated in SCOM but was not imported into SCSM so the versions were not in synch. This creates an event for each class in the MP.  In the other cases the MPs were in SCOM but not in SCSM.

In order to pick these events up I created a custom MP with three rules. I recommend that if you are you are using the SCOM CI Connector to SCSM that you create a custom MP with these three rules. You can anme them something else if you don’t like the names I have used. Hopefully in the next release of the MP that these will be added.

The three rules to create.
The rules all use the same, source, Log and target and create warning alerts.
• Source – Operations Manager Connector
• Log – Operations Manager
• Target – SCSM 2012 Management Server

Event – 34093
Name – SCOM CI Connector for SCSM – SCOM Class was not found in Service Manager – missing MP

Event – 34094
Name – SCOM CI Connector for SCSM – Cannot create part of service map

Event – 34096
Name – SCOM CI Connector for SCSM – Skipping import of instances of class

Follow

Get every new post delivered to your Inbox.