Archive

Archive for the ‘Reporting’ Category

Exchange 2010 Management Pack affects Health Service Availability Reports

March 15, 2011 Leave a comment

This came up on the forums a while back – availability reports were showing downtime when run againgst the agent even though there were no errors from the health service. It seems that the Exchange 2010 management pack was the culprit as it was targetting the health service with a monitor – “The required SCOM hot fixes for Exchange MP are not installed”.

These hot fixes are for Operations Manager 2007 Cumulative udpate 1 (seperate updates for SP1 and R2). If you know your agents are above this cumulative update then it is best to disable the monitor (set override, enabled = false and saved to a custom management pack).

Advertisements

Empty Reports

October 27, 2010 Leave a comment

I find that I point so many people to this post from Marnix that I will link to it from here as I usually can’t find it when I need it!

License Report

October 27, 2010 Leave a comment

There is a good discussion here about limitations of the OpsMgr licensing report. In case the thread disappears, I’ll summarise the main points mentioned by Dan Rogers at MSFT here:

1) The licence report really doesn’t track this accurately. It is being removed in the future since monitoring is not the place where license compliance can most efficiently be tracked. The way that the licensing report was trying to track this was flawed – and SCOM is not the solution for enterprise license management. Getting the license report to be correct involves changing every management pack and getting all customers to reload them.

2) Here is a back of napkin (and unofficial aproach) Since standard license only applies to servers that are dedicated FAX, Print, DNS and File servers (did I miss any?) – where dedicated means not shared for any other reason, the enumeration should be pretty simple to do on a napkin. Count agents. Subtract the number of management servers. That gives you the total number of licensed servers. Then split out the dedicated file/print/fax/dns servers. Those are your standard licenses. The rest are your enterprise licenses.

Categories: Licensing, Reporting

Some extra reports for OpsMgr 2007 R2

June 9, 2010 Leave a comment

I’m a bit late catching up on these but there were some “new” reports posted on the MOM Team blog which may be of interest. They do require that the OpsMgr Data Warehouse is running on SQL 2008 as they don’t work on SQL 2005.

http://blogs.technet.com/b/momteam/archive/2010/04/29/reporting-scenarios-more-samples.aspx

http://blogs.technet.com/b/momteam/archive/2010/05/10/reporting-scenarios-more-samples-updated-attachment.aspx

Scheduling Reports

July 10, 2009 Leave a comment

How do you schedule reports in Operations Manager 2007?

Make sure you configure email within SQL Server Reporting Services Configuration Manager
http://technet.microsoft.com/en-us/library/bb381264.aspx
http://cameronfuller.spaces.live.com/blog/cns!A231E4EB0417CB76!1035.entry

Make sure you configure SMTP Relay:
http://blogs.technet.com/jonathanalmquist/archive/2008/04/01/scheduled-reports-email-address-not-valid.aspx

Reporting Services on a separate SQL Server

July 10, 2009 Leave a comment

When splitting the Data Warehouse from Reporting Services, it seems you have only one chance to get this right. If the install fails first time then the roll back doesn’t clean things up correctly and subsequent attempts to install the Reporting Services component are doooooooomed to failure … and ever increasing frustration.

This is due to the fact that failed instances of installation create an invalid row in the Managmentgroup table in the OperationsManagerDW. To check this, login to OperationsManagerDW and expand tables and look for the table called “DBO.MANAGEMENTGROUP”. Right click on that table and open the same and copy the ManagementGroupGuid from the second column and run the below query against OperationsManagerDW

“EXEC ManagementGroupRejectConnect ‘MG GUID’” (Replace the MG GUID with the guid that you copied from the DBO.Managementgroup” table.

Once it is executed, login with the SDK account and try with installing the opsmgr reporting again.