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

Service Manager 2012 SP1 SMCMDB Subscription Data Source Module errors

This was a brand new installation of SCSM 2012 SP1 on a Windows 2008 R2 SP1 server. After finishing the install and before configuring anything else I looked at the even log and saw a lot of warnings and errors. All in the Operations Manger event log.

This was quite common

Eventid 33610

Source: SMCMDB Subscription Data Source Module.

The database subscription query is longer than expected. Check the database or simplify the database subscription criteria.

The following errors were encountered:

Exception message: Subscription query is taking long.

Subscription id: 0915b911-5657-a1f3-9b75-7038486ca85f

Time spent in new state: 00:00:10.0159455

Time spent in querying state: 00:00:10.0159455

One or more subscriptions were affected by this.

Subscription name: ServiceManager.ActivityManagement.ActivitySkippedRule

Instance name: 活动工作流目标

Instance ID: {2ED5ABBB-C0B8-7622-DAB6-7D792C212F54}

Also getting warning event 33611

Source – SMCMDB Subscription Data Source Module

The database subscription notification acknowledgement is taking longer than expected.

The following errors were encountered:

Exception message: Subscription acknowledgement is taking long.

Subscription id: 482551f9-ba19-051a-0001-6ec22e8f6f3e

Time spent in new state: 00:00:10.0003840

Time spent in querying state: 00:00:09.1878528

Time spent waiting for acknowledgement: 00:00:00.8125312

One or more subscriptions were affected by this.

Subscription name: ServiceManager.ReleaseManagement.ActivityStatusChangedRule

Instance name: 版本记录工作流目标

Instance ID: {1DBC28E4-0734-4CD0-8429-B53C7B0E6B82}

Warning 33333

Source – DataAccessLayer

Data Access Layer rejected retry on SqlError:

Request: SqlConnection.Open

Class: 20

Number: 5

Message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)

Error 33651

Source – SM Implicit UserRole Admin

Implicit user role administrator is unable to configure the implied user role because of database errors.

The following errors were encountered:

Exception message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)

Implicit user role administrator name: Microsoft.EnterpriseManagement.SystemCenter.ImplicitUserRoleAdministrator

Instance name: 订阅工作流目标

Instance ID: {3FDD292D-04CF-E893-9AE2-76740BA4E017}

Error 33602

Source – SMCMDB Subscription Data Source Module

The database subscription is unable to find instances that match its criteria because of database errors.

The following errors were encountered:

Exception message: Error occured in the subscription runtime. Cannot send notifications.

Subscription id: 6f9b1c01-d925-00c9-9444-bcc8f32a0547

Exception: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)

One or more subscriptions were affected by this.

Subscription name: ServiceManager.ActivityManagement.ActivityAddedRule

Instance name: 活动工作流目标

Instance ID: {2ED5ABBB-C0B8-7622-DAB6-7D792C212F54}

Event 2800

Source – OpsMgr Root Connector

The Root connector received an exception from the SDK Service while submitting task status:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)

Event 26308 Error

Source – DataAccessLayer

Query notification processing failed due to a sql exception.

System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)

at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)

at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)

at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)

at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)

at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)

at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)

at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)

at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)

at System.Data.SqlClient.SqlConnection.Open()

at Microsoft.EnterpriseManagement.DataAccessLayer.SqlConnectionHandler.Open(SqlConnection sqlConnection, RetryPolicy retryPolicy, DatabaseConnection databaseConnection)

at Microsoft.EnterpriseManagement.DataAccessLayer.DatabaseConnection.Open()

at Microsoft.EnterpriseManagement.DataAccessLayer.QueryNotificationManager.HandleNotifications(Object state)

Event 29205 Warning

Source  – OpsMgr Config Service

OpsMgr Config Service failed to apply incremental update to the in-memory state and will make an attempt to generate state using snapshot.

Reason:

System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)

at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)

at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)

at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)

at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)

at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)

at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)

at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)

at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)

at System.Data.SqlClient.SqlConnection.Open()

at Microsoft.EnterpriseManagement.DataAccessLayer.SqlConnectionHandler.Open(SqlConnection sqlConnection, RetryPolicy retryPolicy, DatabaseConnection databaseConnection)

at Microsoft.EnterpriseManagement.DataAccessLayer.DatabaseConnection.Open()

at Microsoft.EnterpriseManagement.DataAccessLayer.QueryRequest.Execute(SqlNotificationRequest sqlNotificationRequest)

at Microsoft.Mom.ConfigService.SvcMgrDataAccess.ConfigurationChangeSetProvider.GetConfigurationDelta(IQueryEngine queryEngine, DateTime timeStamp)

at Microsoft.Mom.ConfigService.DataAccess.DatabaseAccessor.NotifyOnChanges()

at Microsoft.Mom.ConfigService.DataAccess.DatabaseAccessor.DoNotification(Boolean isInitial, Boolean isIncremental)

at Microsoft.Mom.ConfigService.DataAccess.DatabaseAccessor.PollingThreadMethod()

Also event 3324 error

Source – Lfx Service

Just contained the name of the management group and nothing else!

Initially due to the Chinese/Japanese characters in some of the events I wondered if it might be a SQL Collation problem. After some search I found that the intial warnings (which were the main ones) could be

  • A bug in SQL when running the database on a very large server which the poster had solved by changing the degree of parallelism. Not here as there were only 2 cores.
  • The SCOM agent but that had not been configured yet
  • Badly written XML but this was a new install and no additions made
  • And some said unless the UI was slow to just ignore them!

As a number of the events mentioned SQL Named Pipes I decided to look on the SQL Server.

While Named Pipes were enabled in most of the sections in SQL Server Configuration Manager it was not enabled in SQL Server Network Configuration, Protocols for MSSQLSERVER.

SQL Configuration

Once Named Pipes was enable the events stopped and have not come back.

Copy SCOM View Data to Excel

 I come across this post regarding SCSM and thought it worth pointing out that it works in SCOM as well.
http://blogs.technet.com/b/servicemanager/archive/2010/03/03/hidden-feature-export-data-to-excel-from-a-view.aspx

Go to a view (State or Alerts) and do Ctrl-A to select all the rows. Ctrl-C to copy and then paste the results into Excel. Instant spread sheet of the data in the view.  A lot easier than using PowerShell to export the data to CSV and then bring it into Excel. And it also brings in the column names as well.
This works best when not using the Group Items By feature. If the group by is closed then only the titles get copied and you cannot expand them in Excel. If they are expanded in SCOM then all the data will be copied but the Group Items By will just be another row in the spread sheet.
This does not work on performance views or any of the views in the Authoring area.

Word is 30

Microsoft Word v1.0 (for DOS) was released in 1983 which makes it 30 years old. Quite a milestone for a software program.

How to Create a New Override MP

 This is something that an OpsMgr admin does on a regular basis but I have added some additional bits to the process.

When a new override management pack is needed then the following steps are required.

If there is a specific alert that needs to be overridden then click on that alert and in Alert Details click on the Alert Rule/Alert Monitor.  This will show which Management Pack the alert was generated by.

 For example – the SQL Server 2008 (Monitoring) management pack.

It is best practice to create an override Management Pack for the sealed MP and put the overrides for the sealed MP into that MP. I prefer to create a new MP in the Administration tab so I can control the process rather than create the MP on the fly when overriding an alert.

Note that unsealed MPs do not need a separate MP as the override will be written directly into the MP.

Go to the Administration  tab and click on Management packs.

 In this case I have filtered the MPs to the SQL 2008 ones. 

 sql server 2008 mps

 Double click on the SQL Server 2008 (Monitoring) MP.

The 2 important fields are ID and Name. The ID must match the filename of the MP and the Name will be the name that shows up in the list of MPs.

Highlight the Name and copy (Ctrl C).

 SQL 2008 MP properties

This will give you the name of the MP – SQL Server 2008 (Monitoring).

Close the dialogue box.

Right click in the Management Pack area and chose Create Management Pack.

 Create MP Wizard

This will start the Create a Management Pack Wizard

 MP Wizard 1

 Paste the name that was copied into the Name field and add Overrides.

Some organizations put Overrides at the beginning of the name so that they show up in the MP list together. It is easy to find all MPs with overrides in the name using the Find search box on the tool bar. Therefore I do not think that  it is necessary to put the word overrides at the beginning. Putting it at the end means that the override MP shows up in the MP list next to the sealed MP so that you know that there are overrides for that MP.

 MP Wizard 2

 Note that it creates the ID name for you. But importantly does not include numbers. When the MP is created it is checked in the console to make sure it is unique. If the 2012 one was done next it would create an MP with ID of SQL.Server.Monitoring.Overrides0. This can be fixed later to match the version with the name.

The version can be any number but leave it at 1.0.0.0 for now.

 MP Wizard 3

 If you click Edit to add knowledge you will get this error message.

 VSTfO Error

In order to edit Knowledge you must have Visual Studio Tools for Office runtime installed along with Word on the computer that is running the console.

 Once it is created it can be seen in the console. It can now be used for overrides but the following steps are recommended before you create overrides. If you go to the Monitoring pane you will see a new View folder with the name of the MP.

 Empty view

 All new MPs created in the console create a top level folder so that views can be created underneath. As this will only be used for overrides the empty view is not necessary and clutters the console.

Highlight the folder and press Delete.

 Delete Empty view

Click yes.

 As noted earlier the MP created does not have 2008 in the file name. When the 2012 MP is made it will have a very similar name. I have found it is better to rename the filename to have 2008 in the name to make it easier to distinguish files outside of the console.

Go back to the Administration pane and click Management Packs.

Click on the new management pack and right click to Export Management Pack.

 export MP

 Once exported open the MP in a text editor.

 The contents will now look like this.

 SQL 2008 Override MP 1

 The key fields are ID and Name.

The ID has to be a unique name for the Management Group and MUST match the name of the file. If these two do not match you will not be able to import it back into the Management Group.

The Name is the friendly name that is seen in views and can be left.

Change the contents of the ID field from SQL.Server.Monitoring.Overrides to SQL.Server.2008.Monitoring.Overrides.

You must also change the Display String Element to match otherwise you will get a message like this.

 SQL 2008 Override MP 2

The highlighted text shows that it is the Display String Element in the Language section that is wrong as it still refers to the original name.

 Change the version number to 1.0.0.1 to show that the view has been removed, that the file name has changed.

 SQL 2008 Override MP 3

 Do a File Save As and ensure that the file name is the same as the ID.

  Import the new MP into the Management group.

 As this has a unique name (ID) it does not overwrite the original MP.

 Multiple MPs

The 1.0.0.0 MP can now be deleted and the new MP is ready for overrides.

 Rather than going through the whole process again for the SQL Server 2012 overrides the existing XML file can be edited by changing 2008 to 2012 in the 4 lines highlighted.

 SQL 2008 Override MP 5a

Do a file save as SQL.Server.2012.Monitoring.Overrides.xml and the new MP can be imported in.

 new sql 2008 override MP

 This template can now be used for any new override MP.

 Override MP Template

 When a new MP is need replace FILENAME with the name of the file which reflects the MP name and must be unique with no spaces and in the 2 Name fields replace MPNAME with a friendly name.

 Here is the text file to use as a template.  

<?xml version=”1.0″ encoding=”UTF-8″?>
<ManagementPack ContentReadable=”true” SchemaVersion=”2.0″ OriginalSchemaVersion=”1.1″ xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsl=”http://www.w3.org/1999/XSL/Transform” >
   <Manifest>
      <Identity>
         <ID>FILENAME.Overrides</ID>
         <Version>1.0.0.1</Version>
      </Identity>
      <Name>MPNAME Overrides</Name>
      <References>
         <Reference Alias=”SystemCenter”>
            <ID>Microsoft.SystemCenter.Library</ID>
            <Version>7.0.8432.0</Version>
            <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
         </Reference>
      </References>
   </Manifest>
   <LanguagePacks>
      <LanguagePack ID=”ENU” IsDefault=”false”>
         <DisplayStrings>
            <DisplayString ElementID=”FILENAME.Overrides”>
               <Name>MPNAME Overrides</Name>
            </DisplayString>
         </DisplayStrings>
      </LanguagePack>
   </LanguagePacks>
</ManagementPack> 

NOTE – when copying this text ensure that the quotation marks are the straight ones (“”) and not the curly ones(“ “). This can happen when copying and pasting from certain programs and web pages.

 

MMS 2013 Videos

In the old days you had to attend MMS to see the sessions and a few months later they would send a DVD (or 2) with all the sessions so you could catch up on the ones that you missed. If you were lucky you could get some extra DVDs to hand out or if you were not there pick up one from a friend. These days the videos are all online and in fact most of them were up 1 to 2 days after they were recorded. Absolutely brilliant. They can be watched online at http://channel9.msdn.com/Events/MMS/2013.

You can also download the videos to watch offline from the same source. You have a choice of formats to download these files. It is handy as I am working at a site where I need to go by train and the hour journey is enough to watch a video – especially when you change the speed to do 1.4x.

If you want to down load all of them it is a bit tedious but a few people have presented PowerShell scripts to help.

Stefan Stranger (ex MVP and now at Microsoft) has a couple.

Videos

http://blogs.technet.com/b/stefan_stranger/archive/2013/04/14/download-mms-2013-videos-from-channel-9.aspx

List of sessions as an Excel spreadsheet

http://blogs.technet.com/b/stefan_stranger/archive/2013/04/03/retrieving-mms-2013-content-sessions-using-powershell.aspx

I used this one below to download the files and Stefan’s above to get the sessions as an Excel file.

http://blog.scomfaq.ch/2013/04/10/mms-2013-download-sessions-offline-viewing/

Note that these scripts  all need PowerShell v3.

This downloads the media files as WMV files. Before I used the script I had downloaded a few as MP4 which was handy for my tablet.

An interesting one was this one which gave you a menu of what format you wanted to download the files in.

http://infoworks.tv/2013/04/09/mms-2013-session-video-download-script-2-0-rtw/

But from comments it does not work and it did not work for me. The author is aware of it and has said he will fix it when he gets time. There was another comment that posted some PowerShell that was supposed to fix the problem. I never got around to trying it as I had already started with the other script.

This is a big help to those of us who did not manage to get across to Las Vegas for the MMS. A big thanks to Channel  9 for making these available.

OpsMgr 2012 Beta First Looks

The public beta has now been released for those of you who want to test it.

Download – http://www.microsoft.com/download/en/details.aspx?id=26804 (About 1 GB and 3 MB for the zipped docs)

Microsoft site for beta – http://www.microsoft.com/systemcenter/en/us/om-vnext-beta.aspx

Technet Site -  http://technet.microsoft.com/en-us/library/hh205987.aspx

 

There are already three posts showing a simple (all components on one server) screenshot install. The big thing I am seeing from these is that there are new prerequisites which need to be checked and installed.

Christopher Keyaert

http://scug.be/blogs/christopher/archive/2011/07/20/system-center-operations-manager-2012-beta-installation-step-by-step.aspx

Dual – Polish – English by Łukasz Rutkowski

http://oopsmgr.wordpress.com/2011/07/20/instalacja-operations-manager-2012/

Bob Cornelissen
http://www.bictt.com/blogs/bictt.php/2011/07/20/scom-2012-beta-first-install

There is a bunch of useful information as usual from Kevin Holman

http://blogs.technet.com/b/kevinholman/archive/2011/07/21/operations-manager-2012-public-beta-has-launched.aspx

And Graham Davies (MVP) has setup a new blog to deal with OpsMgr 2012 posts – http://www.systemcentersolutions.com/2011/07/whats-new-in-scom-2012/

Some nice snippets of information.

There is a lot if useful information in the docs from the download.

  • Quick Start Guide – 62 pages
  • Deployment Guide – 104 pages
  • Operations Guide – 305 pages
  • Supported Configurations – 19 pages
  • Release notes

Plenty to read and it is needed as the requirements for SQL and Windows to install 2012 on is much higher.

SCOM 2007 Versions

I thought that I would do an update list as it is quite useful to look this up when visiting customer sites.

SCOM 2007 RTM = 6.0.5000 23 Mar 2007
SCOM SP1 RC1 = 6.0.6246 5 Nov 2007

SCOM 2007 SP1 = 6.0.6278 22 Feb 2008

SCOM 2007 SP1 Update Rollup = 6.0.6278.100 (KB 971541) 13 Nov 2009

SCOM 2007 SP1 CU1 = 6.0.6278.112 (KB 2028594) 30 Jul 2010
SCOM 2007 R2 Beta = 6.1.6407 20 Nov 2008

SCOM 2007 R2 RC = 6.1.7043 25 Mar 2009

SCOM 2007 R2 RTM = 6.1.7221 23 May 2009

SCOM 2007 R2 CU1 = 6.1.7221.13 (KB 974144) 30 Jan 2010

SCOM 2007 R2 CU2 = 6.1.7221.15 (KB 979257) 29 Jun 2010

SCOM 2007 R2 CU3 = 6.1.7221.49 (KB 2251525) 1 Oct 2010

SCOM 2007 R2 CU4 = 6.1.7221.61 (KB 2449679) 31 Jan 2011

SCOM 2012 Public Beta = 7.0.8289.0 – July 2011

v.Next = 2012

I attended the event “War on Cost” run by Inframon on Friday 5th. There was a whole bunch of Microsofties from Redmond there on their way to TechEd. It was great hearing some of the stuff that will be coming out. As soon as they said that the new products are going to be called 2012 (SCOM, SCCM and SCVMM) I knew that there was going to be a delay. Microsoft name the products based on their financial year which is July to June and not the calendar year. That means anything that has 2012 in the title will not be released until at least July 2011.

OpsMgr will have a public beta in Q2 2011, RC in Q3 and RTM in Q4 (probably about Oct/Nov) – this is calendar year and not Microsoft financial year. Key points are that OpsMgr now has the networking technology from EMC Smarts that they announced a few years ago at a previous MMS, that you can do an in place upgrade from 2007 and at the moment the console looks very similar to 2007. With it being a year away from RTM a lot can change.

They were also very keen to keep a cadence going with the Cumulative Updates being released every quarter and they mentioned that new features could be added as part of the CU. I asked about certificates and DMZ scenarios in 2012 but it seems there will be little change in that area. Which is doubly annoying. Not only is it one of the trickiest areas for organisations to get right but as DMZ agents are often manually installed a quarterly CU means a lot of work to keep them up to date.

ConfigMgr 2012 takes on the System Center style console which is supposed to improve console performance. Flattening the hierarchy and better performance seem to be key areas. Having not looked at it for a while 2012 looks good.

Later this month Opalis 6.3 gets released with connectors for all the System Center products and a new improved one for OpsMgr. Microsoft is working their way through this product to make it more of a Microsoft product. The demos looked pretty good and it looks like another great buy for Microsoft and provides a glue that can link all the System Center products and provide Run Book style automation or even link into other systems. Definitely one to keep an eye on.

I have seen the AViCode stuff before but it was nice to see it demoed now that Microsoft have purchased it. A great tool for monitoring and analysing code and performance problems with web sites – especially .Net.

I am sure these will all be covered at TechEd in more depth so expect more announcements. The main thing that I took away from the day is that I will not be going to the MMS in March as it is too soon to get up to speed on the new version of OpsMgr. A shame as I have gone every second year to coincide with the major releases of the product.

Management Pack Catalog Revamp

After Microsoft moved the MP Catalogue to PinPoint (or PainPoint as I called it) it was incredibly difficult to find MPs. The site has been revamped allowing you to filter by product (OpsMgr, ConfigMgr etc) instead of all lumped together. Then you can filter by company that made the MP and also sort by release date or name. Brilliant. We are back where we started.

The link is here http://pinpoint.microsoft.com/en-US/systemcenter.