Installing Audit Collection Reports

Create:

• Create a folder on the server hosting Audit Reporting - C:\TOOLS\AUDIT REPORTS\ACS on the Operations Server (or the server that will be hosting the Audit Reporting)

Copy:

• Uploadauditreports.cmd, Models Folder and Reports folders from the System Center Operations Manager 2007 CD (located at ReportModels\ACS\) copy them into the folder that was just created.
• Copy the reportingconfig.exe from the SCOM 2007 CD\ Support Tools
• Place that file in the folder that was created - C:\TOOLS\AUDIT REPORTS\ACS.
• Command prompt -  Change directories to C:\TOOLS\AUDIT REPORTS\ACS.

Run the following command:

UploadAuditReports "OperationManagerServerName"
“http://<OperationManagerServerName>/reportserver" “c:\tools\audit reports\acs"

• Click OK on any dialog you receive.
• This creates a new data source called Db Audit
• Uploads the reporting models Audit.smdl and Audit5.smdl and uploads all reports into the ACS\REPORTS directory.
• The Audit Reports folder will appear in the SCOM Reporting console shortly
  • This process can take up to 30 minutes before the folder will appear in the console depending on server spec's and network topology.

>edwalt

You may experience this error when installing the SCOM database to a SQL 2005 cluster.

**Run the installation on the SQL node that hosts the Virtual Node** 

This error is caused when SQL 2005 is missing disk dependencies within the SQL 2005 Group. 

The Fix:

1.  Within the cluster administrator take the SQL group offline.

**If the disks are missing you MUST take the SQL group offline in order for any "new" disks to be recognized.  You will not be prompted to take it offline either.... :(

2.  Properties of SQL server - Dependencies tab -> make sure that all disks are listed.

You should have a SQL Network name dependency, and the Physical disk should be listed here as well.

3.  If the disks are not there - add them - bring the cluster back on-line

4.  Re-run the SCOM installation

*** For additional Information Please refer to:

http://technet.microsoft.com/en-us/library/bb381402.aspx

>edwalt

Operations Manager 2007 Data Warehouse Library Management Pack.

Overview

The Data Warehouse Library Management Pack contains the definitions and workflows required to support the forwarding of data to the Operations Manager Data Warehouse as well as the subsequent maintenance of the data. It also contains rules and monitors to track the ongoing health of the Data Warehouse data flows and processes. This Management Pack ships with the Operations Manager product and is periodically updated with fixes and new functionality.

Feature Bullet Summary:
• Manages the flow of data to the Data Warehouse
• Manages credentials used for the operation and management of the Data Warehouse
• Supports the deployment of reports to the Data Warehouse
• Manages the aggregation of performance data in the Data Warehouse
• Synchronizes alert data in the Data Warehouse with recent alert changes made in the operational database
• Manages the health of Data Warehouse workflows

Release History:
4/4/2007 - Original version released with the Operations Manager 2007 product
7/10/2007 - Updated MP to provide better support for adjustments to Data Warehouse grooming settings.

http://www.microsoft.com/downloads/details.aspx?FamilyID=09f74984-7e9d-42ef-8b38-ad770b084363&displaylang=en

>edwalt

The updated file list includes
• Microsoft.SystemCenter.2007.mp (6.0.5000.28)
• Microsoft.SystemCenter.Internal.mp (6.0.5000.28)
• Microsoft.SystemCenter.Library.mp (6.0.5000.28)
• Microsoft.SystemCenter.OperationsManager.200.mp (6.0.5000.28)
• Microsoft.SystemCenter.ServiceDesigner.Library.mp (6.0.5000.28)
• Microsoft.SystemCenter.WebApplication.Library.mp (6.0.5000.28)
• System.Health.Library.mp (6.0.5000.28)

http://www.microsoft.com/downloads/details.aspx?FamilyID=0d7fc438-4eb9-496e-a664-54d43a577576&DisplayLang=en

CTRL-C and/or the copy function are not available in SCOM 2007.

>edwalt

Management Packs are often upgraded or modified without us knowing it.  In this case the MOM Backwards Compatibility pack v.6.5000.00 and the Dell Management pack v1.0 were the packs currently installed on the SCOM server.

After removing the Dell management Pack the CPU spikes disappeared. 

Resolution

1. Installed the OpsMgr 2007 MOM 2005 Backward Compatibility Update v.6.0.5000.12 which included the System Center Internal Library v.6.5000.16  http://www.microsoft.com/technet/prodtechnol/mom/catalog/catalog.aspx?vs=2005 
2. Reviewing the Dell website - Installed the Dell Management Pack v.3.0 - http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R158716&formatcnt=1&libid=0&fileid=212055

Please remember :  With step one, once you download and run the .MSI, this will only extract the new MP's to a folder on the servers hard drive.  You must then import the new MP's to make them available.

If you are not sure whether the Management Packs imported correctly or not:

1. Open the SCOM Console
2. Select Administration - if the option is not available it is also the yellow "gear" icon on the bottom left-hand side
3. Double click Administration
4. Double click Management Packs
5. The Management Packs currently installed with their installed version numbers will appear on the right-hand side.

How do I import newer Mangement Packs?

1. Open Administration in the Adminstration console
2. Rt-click Mangement Packs
3. Browse to the folder the new management packs were extracted to.
4. Select all of the new MP's listed in the folder - select open
5. The Import Management Packs window will appear.
6. Select the "import" button at the bottom of the Import Management Pack window
7. The import process will begin.
8. If it was successful you will see a green check appear next to the Management Pack name.
9. Select close
10. Refresh the SCOM Console.
11. Check the Management Pack version once again.

If an MP has already been installed you will see a message returned stating that fact. 

>edwalt

SMS Service Pack 3 brings along a new  "advanced" client that must be installed on each monitored client as well.  If the "new" SP3 advanced client has not been installed/or fails to install, processor information is reported incorrectly.  The correct Advanced Client version for SMS SP3 should be 2.50.4253.3000.

How do I verify the Advanced Client Version?

From the client = Open Control Panel\Systems Management Properties\General Tab\SMS Client Version.

From the server:

1. Open a collection that a client in question is a member of
2. Properties of the Client\Hardware\SMS Advanced Client State

 >edwalt