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!

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 Leave a comment

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.

Pre SP2 Exchange 2010 Management Pack

July 24, 2012 Leave a comment

MSFT pulled their most recent update to the Exchange 2010 MP. No one can get the updated version or previous versions. I have had several emails sent to me asking for the previous MP and have sent the file to those who requested it. Since so many people are looking for it and MSFT has not provided it, I have decided to put it up on my spaces page. If you want the pre sp2 Exchange 2010 MP, then go here and get it.

Categories: Operations Manager

Frustrated on How to Configure SQL Server Analysis Services for VMM?

July 3, 2012 3 comments

So I am trying to get VMM 2012 really integrated into SCOM 2012.  There are a few reports that will not work without SQL Analysis Services and integration from VMM.  Well to get VMM to work with this you have to install Analysis Management Objects on your VMM Management Server.  So I do this.   So I try to connect, but I get the same issue (AMO not installed).   I bounce the VMM management server, and when it comes up I try to connect and integrate SSAS and it works.

Categories: Operations Manager Tags: , , ,

Exchange 2010 Most Recent MP (14.3.38.2) Release (for Exchange 2010 SP2) and the Issue

June 28, 2012 Leave a comment

I am very happy to see that the Exchange team made this issue public and are working on a fix.  I am also happy I did not deploy it as soon as it came out.  This just goes to show that you really need to test management packs when they first come out.  This doesn’t mean just looking at the console, but the application that the management pack touches, as I don’t think people who deployed this had any indication of problems until end users started to complain about mailbox access.

Anyway, let’s hope they release a fix soon, but in the meanwhile if you have deployed it then they post a work around.  Here is the link to their blog with a detailed description of the issue and the work around.

http://blogs.technet.com/b/exchange/archive/2012/06/28/mailboxes-on-a-database-are-quarantined-in-an-environment-with-system-center-operations-manager.aspx

Categories: Operations Manager Tags: , ,

SCOM CU5 patch and my experience

August 5, 2011 Leave a comment

Patched our lab this afternoon.  All seemed well until I ran the SQL scripts on the OpsDB and DW.  When I went back to my RMS to open the console and import the new MP’s, I got an error saying the SDK service had not initialized and could not connect.

I saw a lot of 2115 warnings and 26319 errors.  I reached out to my buddy Almquist  and he recommended bouncing the SQL service.  He said this was an issue that was supposed to be fixed in CU4.  Apparently we ran into it during our upgrade from CU3 to CU5.

So if you have this issue, then you know the easy fix, bounce SQL and you will be good to go.  Other than that I had no issues in my lab.  I hope this continues in our pre-prod environment and then production.

Happy SCOMing!

Categories: Operations Manager
Follow

Get every new post delivered to your Inbox.