Updated solution for OM12 SP1 UR#2 Web Console Error: System.Reflection.ReflectionTypeLoadException: [ReflectionTypeLoad_LoadFailed]

SCOM, System Center, SCOM 2012 Send feedback »

My friend and fellow MVP and Savision enthusiast Marnix Wolf blogged about this issue and a quick solution provided by Savision last month. However the solution is now updated.

The Issue:

  • You run SCOM 2012 SP1 UR2
  • You run Savision Live Maps for SCOM 2012 version 1.2.0
  • When accessing the SCOM Web Console you get the following error:

    System.Reflection.ReflectionTypeLoadException: [ReflectionTypeLoad_LoadFailed]



The cause:

There was an incompatibility in the Savision Summary Widget with the UR2 update for SCOM.

The previous solution:

Savision quickly released a newer version of their Summary Widget mp (version 1.2.1.0) within a few days and blogged about it here.

The update to this solution:

Savision released version 1.2.1 on the 13th of June 2013. The separate management pack files can not be downloaded anymore from their website. Simply download the full Savision Live Maps for 2012 version 1.2.1 from their website here and run the upgrade to the latest version and make sure that the Summary Widget management pack files are upgraded to 1.2.1.x version.

After you install the Savision Authoring console version 1.2.1 you can find the two management pack files in the following path (if you used a different install path you will be able to find it now I guess): "C:\Program Files\Savision\Live Maps for OpsMgr 2012\Authoring Console\Management Pack" . Current versions today are 1.2.1.22 for these two files.

Savision did fix a few other issues between 1.2.0 and 1.2.1 release. There is a link to the release notes next to the download link on their website.

Conclusion:

Now you can enjoy your monitoring and dashboarding of course! B)B)
And thanks to Savision for the updates.

Bob Cornelissen

SQL File Disk Performance Management Pack for SCOM

SCOM, SQL, System Center, SCOM 2012 Send feedback »

Purpose

This management pack brings together I/O statistics for SQL data files and log files directly from the SQL virtual file stats view into SCOM where you can report on these for any period of time. It can collect data from SQL 2005, 2008 and 2012 data files.

Introduction

Starting SQL 2005 SQL DBA’s have the possibility to use Dynamic Management Views and Functions to monitor the health of a server instance, diagnose problems, and tune performance. This management pack is specifically geared towards the sys.dm_io_virtual_file_stats view, which returns I/O statistics for data and log files. The view is used by DBA’s to view current counter values for each database file (data or log). It is a current point in time and these values are cumulative values since the last restart of the server. This management pack collects these values for use in viewing and reporting. There are no health state changes or alerts connected to these values. There are short time performance views and two reports with double Y axis to display longer term data. The long term data is translated from cumulative data into amongst others IOPS for each point in time.

Files
You can find all management pack files, optional override management packs and the management pack guide explaining it all in the zip file attached in the TechNet Gallery page. The current version of this management pack is 1.0.2.48 and released on the second of June 2013.

General

This Management Pack is provided free of charge by the authors to the System Center and SQL community.

Written by Bob Cornelissen, David Scheltens, and Pavel Dzemyantsau

The Management pack can be found here:
SQL File Disk Performance Management Pack for SCOM.

Enjoy!

New Savision whitepaper by Damian Flynn, Unraveling the Network with SCVMM 2012 SP1

SCOM, SCVMM, System Center Send feedback »

Savision has a tradition of providing free whitepapers to the community about System Center related topics written by industry specialists. A few months ago I was discussing with them about a new free product they were releasing (Cloud Advisor for System Center Virtual Machine Manager), and they asked me who would be a very critical and vocal reviewer of its possibilities. I directly pointed them to my fellow SCCDM MVP Damian Flynn. In the end this resulted in Damian writing a whitepaper for Savision and the community at large about Virtual Networking in SCVMM 2012 SP1. Mind you this whitepaper does not talk about the Savision product, but about SCVMM features and in a practical way.

This is something new in VMM and sometimes hard to figure out on your own, but it is a very important subject which will prepare you for the future of networking within virtual networks. And dont forget that the future is already here with SCVMM 2012 SP1. I have found that Damian Flynn is one of those people who knows what he is talking about and this is certainly one of those subjects he is the absolute authority on.

This free whitepaper can be downloaded from the Savision site from here:
Unravelling the Network with SCVMM 2012

Also Damian will be giving a webinar (on two dates for your convenience) where he explains more about the subject and will be available for questions. See the link above for the registration details for those webinars.

And again also from my side a big thank you to Savision for providing the community with these great resources! And a very warm thank you to Damian Flynn for clearing up the mist around this subject and helping everybody understand what this is about!

Jalasoft released the new Xian SNMP Device Simulator v4

SCOM, SCOM 2012 Send feedback »

Jalasoft released the new Xian SNMP Device Simulator v4.

This is a grrrrreat SNMP network device simulation tool which was and still is free of charge. It is great for instance for playing around with network monitoring in SCOM. I have been playing with previous versions a lot for testing and demo purposes. The great and innovative engineers at Jalasoft have now created a new version of this tool (v4) with some architectural changes and new possibilities and an expanded set of default available devices to simulate. It is now based upon agents which get installed on Windows machines with multiple IP addresses; and one console of this tool in the same network will manage these agents and start the devices you want on the IP addresses you select. It is very easy and quick. I will write more about this soon and provide some examples.

But for now here are the announcements:

The announcement on the Jalasoft blog

Explanations on the architecture and installation and use of the product from the Jalasoft blog

And a press release for the same

This will improve our possibilities to play around with network monitoring and for demo purposes. Thank you very much Jalasoft!

Bob Cornelissen

SCOM 2012 SP1 UR2 now also for Gateways

SCOM, System Center, SCOM 2012 2 feedbacks »

As announced a month ago the UR2 update rollup for SCOM 2012 SP1 was released. One of the known issues of this update was that the gateway servers did not get their agent distribution folders updated. This was because there were no fixes for the bits of the gateway role itself. However of course the gateways do have the agentmanagement folder where the SCOM agents and their latest update can be found. This caused that folder to not be updated with the latest agent fixes. Simple workaround was to copy those newest files from an updated Management Server. Meanwhile Microsoft worked on a fix. A week ago Microsoft released through WSUS the UR2 update package for SCOM Gateway servers.

Good luck!
Bob Cornelissen

Exchange 2013 management pack for SCOM released

SCOM, Exchange, System Center, SCOM 2012 Send feedback »

This was one highly requested MP that we have been waiting for. The Exchange 2013 Management pack for SCOM is now released. It works on SCOM 2007 R2 and SCOM 2012. The released version today of this management pack is 15.00.0620.030

For those who knew the Exchange 2010 management pack and its special correlation engine: the correlation engine is gone now! B) :p :D (Yes, I am happy with that!!).
A Quote from the post:

“If you are familiar with the Exchange 2010 Management Pack, you know that it had a service called the correlation engine that ran on the Root Management Server. It basically correlated health data from all monitored Exchange components. In the Exchange 2013 Management Pack, the correlation engine is no longer used”

This is the TechNet blog post:
http://blogs.technet.com/b/momteam/archive/2013/05/14/exchange-2013-management-pack-released.aspx

The download can be found here:
http://www.microsoft.com/en-us/download/details.aspx?id=39039

The Management pack guide online version can be found here:
Exchange 2013 Management Pack Guide

We will probably write more about this mp later when we had more experience with what it looks like in real life. It looks like they have kept the number of views very low at least.

Bob Cornelissen

Getting more out of your DPM monitoring through SCOM

SCOM, DPM, System Center, SCOM 2012 1 feedback »

If you are monitoring DPM 2012 through SCOM 2012 and you have multiple DPM servers setup you might want to gain more insight into the status of the backup service as a whole and point to the issues at hand from a central location. In that case I would like to bring to your attention a blog post (and more to come) from my good friend and fellow System Center Cloud and Datacenter Management MVP -> Steve Buchanan.

In his post he shows us how we can take advantage of the Distributed Application feature of SCOM, whereby you can link the health status of separate objects together into one Distributed Application. This creates a single location where your application can be viewed and the status of the objects is combined and can be reported on with Service Level Agreement views and availability reports. A good entry for any higher level dashboards where you can see the status of other central services as well.

Go and see Steve's blogpost here:

DPM as a Distributed Application in SCOM.

Enjoy your backups and your monitoring at the same time!

Windows Server Management Pack version 6.0.7026.0 released

Windows 2008, SCOM, System Center, SCOM 2012, Windows 2012 Send feedback »

Yesterday the Windows Server Management Pack got a new update to version 6.0.7026.0 .

Changes in This Update
The April 2013 update (version 6.0.7026.0) of the Windows Server Operating System Management Pack contains the following changes:

  • Fixed a bug in Microsoft.Windows.Server.2008.Monitoring.mp where the performance information for Processor was not getting collected.
  • Made monitoring of Cluster Shared Volume consistent with monitoring of Logical Disks by adding performance collection rules. (“Cluster Shared Volume - Free space / MB”,”Cluster Shared Volume - Total size / MB”,”Cluster Shared Volume - Free space / %”,”Cluster Disk - Total size / MB”,”Cluster Disk - Free space / MB”,”Cluster Disk - Free space / %”)
  • Fixed bug in Microsoft.Windows.Server.ClusterSharedVolumeMonitoring.mp where the Cluster disks running on Windows Server 2008 (non R2) were not discovered.
  • Fixed bug 'Cluster Disk Free Space Percent' and Cluster Disk Free Space MB' monitors generate alerts with bad descriptions when the volume label of a cluster disk is empty.
  • Added feature to raise event when NTLM requests time out and customers are unable to use mailboxes, outlook stops responding, due to the low default value for Max Concurrent API registry Key (HLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters) , which is a ceiling for the maximum NTLM or Kerberos PAC password validations a server can take care of at a time. It uses the “Netlogon” performance counter to check for the issue.

The Windows Server Management Pack can be downloaded here.

SCOM 2012 SP1 command line install lessons learned update 1

SCOM, System Center, SCOM Tricks, SCOM 2012 3 feedbacks »

A few weeks ago I posted an article about some of my lessons learned for SCOM 2012 SP1 command line installations. It contained a very long Lesson 4 talking about creation and placement and naming of mostly the Datawarehouse database. I discussed the difference of SQL 2008 R2 and SQL 2012 in default file paths for databases and log files and its effect on the placement of the datawarehouse files. And of course the remaining effect that the created files have no name. As I explained for the GUI based setup there is a workaround by adding the datawarehouse database name as a folder name in the installation path of the database (basically this is using the bug in the install script B) ). SO lets go for the addendums to the lessons because there is hope:

Lesson 4 addendum 1:

Now I have been informed that there are a few additional install switches, until now not documented on the TechNet pages. This enables us to use the same trick as in the GUI. And of course this also enables us to change the paths for the opsdb and DW db separately, which was what I needed as well. These are listed below together with an example using a shorter path name:

/DatabasePath: "D:\Program Files\SQLstuff\Data"
/DatabaseLogPath: "E:\Program Files\SQLstuff\Data"
/DWDatabasePath: "D:\Program Files\SQLstuff\Data"
/DWDatabaseLogPath: "E:\Program Files\SQLstuff\Data"

Thanks to Byron Ricks for sending me these additional switches.

So what do we do if we want to make use of the trick to get the datawarehouse to be installed in the right directory and also for it to use the name we want? We append the database name we want to both the DW install paths.

/DWDatabasePath: "D:\Program Files\SQLstuff\Data\OperationsManagerDW"
/DWDatabaseLogPath: "E:\Program Files\SQLstuff\Data\OperationsManagerDW"

In my case this now created an empty folder with that name on my SQL box with that name, but the DW database was installed one level higher (where we wanted it) and with the right name (what we wanted). Now I can expand the script to have it clean up that empty directory later in the install process after checking for succesfull installation of the product.

Note: This happened to be a test with a SQL 2008 R2 SP2 backend server.

Lesson 2 addendum 1:

The previous post talked about the correct syntax of the /AcceptEndUserLicenseAgreement installation switch. And it talked about this only being needed for the first management server. However I have heard from a friend of mine that this is true for SCOM 2012 RTM, but that for a clean install of SCOM 2012 SP1 this switch is needed for all management servers. It will take a few more days until I can claim and clean a larger test environment for the clean deployment of a larger number of servers and components and I will write back with an update if I can confirm this story. In any case, if installing without this switch on a second management server gives you an error you can try to add this switch with a value of 1 and see if it works.

Update 10 June 2013: I can confirm this is needed also for other scripted installs. I ran into this requirement as well with the installation of a stand-alone Web Console server. So from now on I always add the /AcceptEndUserLicenseAgreement:1 to any install.

Other items

As soon as I claim and clean that other test environment I will be deploying a lot more components and will see what we run into and blog it back here. Keep in mind that this is just one of the possible setups, as you can have several prerequisite setups. For instance, are you installing on Windows 2008 R2 SP1 and SQL 2008 R2 SP2, or are you installing on Windows 2012 and SQL 2012 SPx? These can have diverse and sometimes unexpected effects as I have shown with the path variable inside SQL in my previous post. But never be discouraged :p

Happy installing!
Bob Cornelissen

Update Rollup 2 for System Center 2012 Service Pack 1

SCOM, DPM, SCVMM, Service Manager, System Center, SCOM 2012 Send feedback »

Released yesterday was the Update Rollup 2 for System Center 2012 SP1. Keep in mind this is not the one for System Center 2012 RTM version (got released yesterday as UR5), Only update rollups for SP1 below!

This release contains updates for: App Controller, SCOM, Service Manager, DPM, Orchestrator.

It is a long list of updates, so here is the link to check out what got fixed and where to dowload the separate components (if you are not using WSUS, where it should appear as well).

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

Hope this helps fix some issues for you and happy manageing of your datacenters!
Bob Cornelissen

Contact / Help. ©2016 by Bob Cornelissen. blog software.
Design & icons by N.Design Studio. Skin by Tender Feelings / Evo Factory.