sariaya

I recently got a new job and it is my first exposure to MOM 2005. I have a
task of figuring out why the Microsoft Availability Reporting Report is not
working. Here is what I have done so far.

First, I downloaded the latest Microsoft Availability Reporting Management
Pack - dated August 28, 2006.

Second, I installed the Availability Reporting Management Pack according to
the guide. I cut and paste the procedure that I followed - see below:

--------------------------------
Upgrading the Availability Reporting SQL Server components on the SQL
Reporting Services database server.
To re-install the Availability Reporting SQL Server component on the MOM
Reporting database server logon as an administrator:

1. Select Add/Remove Programs from Control Panel.

2. From the list of currently installed programs select Reliability
****ysis Reporting and click Remove. (Note: Availability Reporting database
tables, views, functions, stored procedures and reported are not removed as
part of this removal).

3. Once the Availability Reporting SQL Reporting Server msi has
completed removal, locate the updated MOM-MRAS.MSI and follow the
installation instructions within the Availability Reporting Management Pack
Guide. (Note: Existing Availability data is preserved during the
installation. Only necessary stored procedures and underlying configuration
tables are updated.)


Upgrading the Availability Reporting MMC snap-in
To re-install the Availability Reporting MMC snap-in on computers where it
is already installed:

1. Select Add/Remove Programs from Control Panel.

2. From the list of currently installed programs select Microsoft
Operations Manager 2005 Availability Reporting Console and click Remove.

3. Once the Microsoft Operations Manager 2005 Availability Reporting
Console msi has completed removal, locate the updated MRAS_MP_UI.MSI and
follow the installation instructions within the Availability Reporting
Management Pack Guide.


Upgrading the Availability Reporting Management Pack (Availability
Reporting.akm)
To import the Availability Reporting Management Pack by using the MOM
Administration Console:

1. In the MOM Administrator console, click Management Packs.

2. In the details pane, click Import/Export Management Packs.

3. On the Import or Export Management Packs page, click Import
Management Packs and/or Reports.

4. On the Select a Folder and Choose Import Type page, click Browse.

5. Navigate to the folder where the Availability Reporting.akm
accompanying this release resides, and then click OK.

6. On the Select Management Packs page, select the Management Packs
that you want to import, select the import option Import Management Packs
only, and then click Next.

7. From the list of management packs select Availability Reporting.akm
and the Import Options Replace existing Management Pack.

8. To complete and close the wizard, click Finish.

------------------------------------------------------------------------------------------------

Third, on the MOM 2005 Administrator Console, under the Rule Groups node, I
added Windows 2003 Servers on the Computer Groups tab on the Microsoft
Availability Reporting Managing Pack for Microsoft Operations Manager 2005
group. I also added Windows 2003 Servers on Application Events group. This
procedure is shown on page 9 of the Microsoft Availability Reporting
Management Pack Guide.

Fourth, in the Availability Reporting snap-in console, I created a new
report and schedule this report to run at a specific time.

Fifth, I checked the Microsoft Availability Reporting Report console to see
if the report I created was generated in the drop down list box called Report
Name. It is not showing.

Is there a log that I can check to determine what's happening so I can fix
the problem? How does the Microsoft Reliability and ****ysis Service work?
Also, how is the Microsoft Availability Reporting Report generated?

Thanks for your help.

Sariaya

twan van beers

Hi ya,

before the report generates...

- you have to associate the appropriate computer groups with the
availability rule group as per the guide
- the Availability discovery script has to run on the target computers (by
default this is 00:32 or so each morning
- after the discovery script has run, the target servers need to be rebooted
- after the reboot the DTS job to transfer info has to be run
- after the transfer of data the Reliability****ysisReporting task needs to
run (NOTE this must run the following day, since the end time hard coded in
the job is yesteray at 23:59)
- after all of this, the report you want to schedule needs to pass its
scheduled time, and then the Reliability****ysisReporting task needs to run
again

Cheers
Twan

sariaya

Hi Twan,

Thanks for your quick reply and suggestions to my post.

The good news is that our MOM Availability Reporting is now working. It
seems to work after I added "Windows 2003 Servers" on the Computer Groups
tab of the "Microsoft Availability Reporting Management Pack" node and the
"Application Events" node.

I have another question - when importing the Availability Reporting
Management Pack, and the "Import Management Packs only" is chosen; would the
rules on the "Microsoft Availability Reporting Management Pack for Microsoft
Operations 2005" node be retained. Or do I have to reconfigure the rules
each time I updated the Availability Reporting Management Pack.

Thanks,

Sariaya

twan van beers

DHi Sariaya,

Great that its now working. You should only have to associate the computer
group with the Microsoft Availability Reporting Management Pack node. The
relevant servers should then flow down and grab all the rules below that

When importing a management pack most things have to be reapplied. I think
that the only exception is enable/disable of rules and company knowledge will
be retained if you use the merge option, and everything is replaced if you
use the replace option. This will include any computer group assignments

It pays to keep a good change log...

Cheers
Twan

thomas olsen

Hi All


Now you can import the new version of the MP and your "rule copies" will not
be touched.
/Thomas O
"Twan van Beers" <TwanvanBeers@discussions.microsoft.com> wrote in message news:E2AF223A-532C-44F4-BA9F-68A257ED5FF5@microsoft.com...

anders bengtsson

You can also choose not to overwrite any changes when you import a new
version of a MP.


"Thomas Olsen" <thomas_olsen44@hotmail.com> wrote in message news:ObGC5ZB7GHA.1252@TK2MSFTNGP04.phx.gbl...

huttonhenry@gmailcom

Hi,

I have been running availability reporting for a month and a half,
using the fixed version 05.0.5000.0001. I have a task set-up for all
five types of reports and data is being generated.

The DC reports is only reporting on 2 of my 8 domain controllers.
Under the availability reporting MMC I have the report linked to the
"Windows Server 2003 Domain Controller" group. Under the ruleset
"Microsoft Availability Reporting Management Pack..."\"Directory
Services" I have the "Timezone" and "Windows Servers 2003 Domain
Controller" groups associated to it.


Domain Controller" computer group it shows all eight domain
controllers.

There is nothing in the report that indicates why six servers have not
been reported against (i.e.nothing "user defined under exclusions" or
"exclusions due to missing or bad events"). The two servers that are
being reported are no different from the other two (i.e. they are in
different locations, same software levels as the others).

Has anyone seen this before? Any suggestions would be appreciated.
Thanks in advance,
Hutton.

anders bengtsson

Hi Hutton

Have you associated Directory service rule group with your domain controller
computer group?
You can find more info about it here
http://www.microsoft.com/technet/prodtechnol/mom/mom2005/Library/3e1dfa65-84a5-4e3e-9403-3ef9b47c6b68.mspx?mfr=true

--
Regards, Anders Bengtsson (mcse, mcp, mcsa:messaging) | anders AT contoso.se
| Website and blog: http://www.contoso.se

pete zerger

Hello HuttonHenry@gmail.com,

Remember, it takes some reboots and the related events before computers will
show up in the reports. Have these 6 machines been rebooted since deployment
of the AvailRpting Pack?

And just for sake of being thorough, I captured Clive's specific instructions
on rule group / computer group associations and known issues with that MP
here.
http://www.it-jedi.net/2006/09/availability-reporting-mp-4th-times.html

Regards,

Pete Zerger, MCSE(Messaging), MVP - MOM
URL:http://www.momresources.org
BLOG: http://www.it-jedi.net/

huttonhenry@gmailcom

Hi Anders, yes I have associated the DC rule group with the domain
controllers group. Thank you.