Archive

Archive for December, 2013

Path is empty in Web Console for SCOM 2012

December 19, 2013 Leave a comment

If you use the SCOM 2012 web console, or maybe even publish dashboards to SharePoint, you might notice that the PATH of the monitored objects is missing in some views.  This is not good.

12-19-2013 12-59-20 PM

We would like to see path displayed in this dashboard, so how can we make it happen?  It’s a simple fix.  Go to the install directory of your SCOM Console (Installdir\System Center 2012\Operations Manager\Console) and copy the file “Microsoft.EnterpriseManagement.Monitoring.DataProviders.dll”:

12-19-2013 1-20-14 PM

 

Paste that file into the web console directory (Installdir\System Center 2012\Operations Manager\WebConsole\WebHost\bin).  This will over write the existing one, which is fine, but if you are a cautious person, simply rename it.  The current file may look like this:

12-19-2013 1-03-59 PM

 

Notice the difference in the version.  Once you copy and replace the web console dll with the dll from the console folder, you will see the path of the objects in the web console and also on your dashboards published to SharePoint:

12-19-2013 1-22-03 PM

Mission accomplished!

Advertisements
Categories: Operations Manager

Exchange 2013 Management Pack

December 18, 2013 Leave a comment

We have recently deployed a few Exchange 2013 servers in a few of our labs.  We are planning on putting some production users on the servers in the new year.  Our Exchange engineering group has requested the servers to be managed by SCOM, so I took a look at the new management pack, especially given the history of the management packs for Exchange 2010.

If you are worried, based on your experience with 2010, then don’t be.  This management pack, as it is now, is very lightweight.  There are a few classes, a few monitors, and I think one rule.  This is very different from the last version.  Of course, gone is the correlation engine as well.

Instead of re-hashing what has already been said I will just post this link to the MSFT blog which talks about this MP:

http://blogs.technet.com/b/momteam/archive/2013/05/14/exchange-2013-management-pack-released.aspx

Get a list of monitored URLs out of SCOM via PowerShell

December 18, 2013 4 comments

Our URL monitors, imported using the BulkURL utility for SCOM have display names that contain the text URL.  The names of the monitors containing URL are unique and contain a list of SEVERAL urls being watched.  For example we have one monitor for SharePoint, which contains several URL’s of sharepoint sites, and another called SharePoint2 that contains several more URL’s.  The point is, you are going to query for the name of your parent monitor, then you can get all the URL’s that are contained in that parent monitor.

Find URL monitors if URL is in the monitor display name:

get-monitoringclass | where {$_.DisplayName -like “*URL*”} | FT Name

This will return only GUIDS, if created in console.  To get the display name you need to execute this:

get-monitoringclass | where {$_.DisplayName -like “*URL*”} | FT Name, DisplayName

Now from the list find the GUID and the display name of the actual monitor, not watcher node:

WebApplication_f1cea1da6eab40e4a7c27d0f6141cdfe

WebApplication_e6a8be62bd1d448ea4787284d0df5a8c

WebApplication_dce99aee7c924d24a01d9df7532162f7

WebApplication_a34f8e5f51ac45558146e7a53ba1797b

From those guids, you can now run the following command and dump a list of URLS:

get-monitoringobject -monitoringclass (get-monitoringclass -Name WebApplication_a34f8e5f51ac45558146e7a53ba1797b) | Select-object DisplayName | export-csv “My Location”

From what I could tell there are many ways to get urls into SCOM, but nothing out of the box to dump the monitors out of SCOM.  Powershell, of course is probably one of the best and fastest ways to achieve this.  Hat tip to Charles Champion for working with me on this.